06:08
<MikeSmith>
botie, inform mkwst about the Origin Policy bug, added comment at https://bugs.chromium.org/p/chromium/issues/detail?id=901477#c14 with NetLog dump attached
06:08
<botie>
will do
12:18
<FND>
Domenic: your comment at https://github.com/whatwg/html/issues/3035#issuecomment-329003087 last year resulted in some controversial discussions on my end...
12:18
<FND>
.. until we realized we weren't actually sure what you _actually_ meant here: "custom elements are not meant to be arbitrarily powerful; they're meant to give you the same power as the platform has" - is it worth asking for clarification?
12:20
<FND>
in particular, someone argued that strict interpretation would mean Polymer, for example, is non-idiomatic as per your statement
15:00
<bradleymeck>
is there a simple way to "tee" a Response Object
15:06
<bradleymeck>
nm.... missed the .clone()
15:25
<Domenic>
FND: my comment is about the standard.
16:35
<annevk>
Domenic: I could prolly be persuaded that it's still early enough to break early adopters btw, but we can't keep doing that
16:36
<Domenic>
annevk: I just don't think it counts as "break"
16:36
<annevk>
Domenic: so at some point we do have to consider them and work with them in mind
16:36
<annevk>
I see, I guess we disagree then
16:36
<Domenic>
What code is broken?
16:37
<Domenic>
A page author decides to do something a component author didn't expect. Now, their page behaves as desired.
16:37
<Domenic>
Nothing is broken, just weird.
16:37
<Domenic>
I think there are plenty of custom elements out there that don't proactively do `attachShadow({ mode: 'closed' })` to "protect" themselves against breakage
16:37
<Domenic>
They just accept the consequences if page authors want to do something unexpected
16:38
<Domenic>
We've certainly never recommended that every custom element attach a closed shadow root to protect itself. Should we start doing so?
16:48
<annevk>
Domenic: I guess it depends
16:49
<FND>
Domenic: thanks, I'm not sure that'll suffice to quell concerns here, but that's not your issue :)
16:49
<annevk>
Domenic: I’m still not sure attach makes sense btw due to subclassable built-ins
16:50
<Domenic>
annevk: yes, basically no solution works with subclassing.
16:50
<annevk>
Domenic: those have internals already
16:50
<Domenic>
Oh, are you just talking about the name?
16:50
<annevk>
Those have internals already*, so get* makes more sense
16:51
<annevk>
Ugh IRCCloud
16:51
<Domenic>
I don't care about the name. Although I think it's still up in the air whether we want the ElementInternals class to be more like computed style (reading back all internals including ones you set) or more like the style attribute (an overlay on top of any existing internals)
16:51
<annevk>
Yup
16:52
<annevk>
Hmm yeah, less cascade seems nice, but who knows
16:57
<jgraham>
hsivonen: foolip & co pointed out https://staging.wpt.fyi/results/encoding?product=firefox%4076c0092916&product=firefox%407f56040b8f&diff which I assume you are aware of, but I wonder what the reason is
17:04
<annevk>
jgraham: I think AutomatedTester should have a link to a bug
17:05
<AutomatedTester>
one sec please caller
17:05
<annevk>
jgraham: I think it’s also fixed in Nightly?
17:07
<jgraham>
annevk: Oh is this that bug
17:07
<jgraham>
foolip claimed that the regression was still there
17:07
<annevk>
jgraham: it was discussed a while back when this was first announced
17:08
<jgraham>
annevk: Oh you're right https://staging.wpt.fyi/results/encoding?product=firefox%4076c0092916&product=firefox[master]&diff
17:08
<annevk>
jgraham: it was meant to “regress” in a way we thought would be acceptable for release, so could be
17:08
<jgraham>
hsivonen: Sorry to bother you
17:10
<AutomatedTester>
oh I can't find it
17:11
<AutomatedTester>
jgraham: iirc, we were falsely passing those tests
17:11
<AutomatedTester>
and then with the encoding.rs work we started failing properly
17:11
<jgraham>
AutomatedTester: Doesn't matter :)
17:13
<AutomatedTester>
ok
17:13
<AutomatedTester>
it's https://bugzilla.mozilla.org/show_bug.cgi?id=1423877
17:14
<AutomatedTester>
if that is the issue
17:18
<annevk>
Ta!
17:18
<annevk>
Think so