Domenic Denicola
Domenic Denicola
Yes, I think that was the intended behavior. If you are able to fix that back to how it was previously, that would be much appreciated!
@whatwg/sg gentle ping on this issue :). I am willing to prepare PRs if I can get a directional OK on this.
I'm unsure why one would be easier than the other, but... anything helps.
Bleh, it requires even more contortions to deal with nested workers: https://wicg.github.io/page-lifecycle/#dedicatedworkerglobalscope-owning-document I'll at least try to upstream that from HTML...
We discussed this topic a bit in this morning's WHATNOT. I was asked to give a bit of a historical perspective. I think the overall goal of enabling custom elements...
(In the future, please consider responding once, instead of four times, as each response sends an email to 700+ people. If this means waiting until you're at a computer, so...
It's not a cache key, for sure, since it's not used as such. The cache keys one might use would be as discussed in https://httpwg.org/http-extensions/draft-ietf-httpbis-no-vary-search.html#section-7, including all three of: the...
I think https://fetch.spec.whatwg.org/#concept-request-destination might be better than the enum? Anyway let's remember to use https://speced.github.io/bikeshed/#metadata-required-ids to enforce this.
I think we should update the specification to match reality, and if someone wants to propose changes to browsers, it can go through our normal working mode.
Yeah, to invoke [[GetOwnProperty]] you'd need to use `Object.getOwnPropertyDescriptor(window, "foo")` or similar.