16:24
<Domenic>
annevk: I sent out an internal call for someone on the implementation side to take point and coordinate on cleaning up embed/object/plugins. We already have a thread on general Flash cleanup so I hope someone is interested in carrying it further and actually making changes to embed/object to achieve interop.
16:25
<annevk>
Domenic: sounds good, happy to work with whoever volunteers; I have some ideas 🙂
16:27
<annevk>
I wish it was part of disabling Flash as getting people to take initiative now is undoubtedly harder, but alas
16:40
<Domenic>
I want to update https://developer.mozilla.org/en-US/docs/Web/API/Window/isSecureContext to point to HTML but the edit button has disappeared on MDN I guess
16:47
<gsnedders>
Domenic: the "Found a problem with this page?
16:47
<gsnedders>
Domenic: " section links to the source on GitHub?
16:47
<Domenic>
Oh, I see, I was able to find that after Ctrl+Fing... but it was not in my line of sight
16:49
<gsnedders>
I mean I'd argue that's a sensible thing to file a bug for :)
16:49
<Domenic>
Filed https://github.com/mdn/content/issues/1192 instead of doing a PR... seems easier.
18:42
<Domenic>
annevk: https://bugs.chromium.org/p/chromium/issues/detail?id=1163588 for PDF + click events... you may want to subscribe, or maybe we should open a spec-side issue. I guess it's a UI events issue technically?
18:47
<annevk>
Domenic: yeah I guess, though HTML should prolly define PDF documents
18:47
<Domenic>
Yeah
18:48
<annevk>
I think we need to accept that PDF is a thing that’ll stick around and define the observable aspects. Prolly don’t wanna go into the format though
18:58
<Domenic>
I wonder how much we will gain from making it PDF-specific vs. defining some much smaller version of "plugins" with more rules. (E.g.: content type must match, <param> does nothing, clearly-defined interaction with sandbox, etc.)
18:58
<Domenic>
PDF-specific seems like the right place to start though
19:02
<andreubotella>
is there any difference, though, between a PDF in an object and, say, a network error in an iframe?
19:02
<andreubotella>
both are presumably resources "without a Document"
19:03
<Domenic>
Well, object and iframe are needlessly different in lots of ways
19:03
<Domenic>
But indeed in terms of what comes out of the navigation algorithm I think they're very similar
19:04
<Domenic>
Some discussion of observability at https://github.com/web-platform-tests/wpt/pull/27129
19:04
<Domenic>
Also I don't remember what the latest is on error events on network errors
19:04
<Domenic>
Oh right fallback content, as Anne mentioned in that thread, is probably the biggest answer to your question, andreubotella
19:05
<andreubotella>
I'll take a look
19:06
<andreubotella>
annevk: on another note, how big of a faux pas would it be to open a new PR to tackle the same issue as https://github.com/whatwg/html/pull/3276?
19:07
<andreubotella>
since the OP seems to be AWOL for years and the PR needs updating other than the merge conflicts
19:49
<annevk>
andreubotella: totally fine
19:50
<andreubotella>
ok
19:51
<andreubotella>
I figured it'd be better to raise one single Firefox issue for both that PR and https://github.com/whatwg/html/issues/6247
20:31
<smaug____>
Is there a spec term for the about:blank which is created synchronously?
20:34
<Domenic>
"initial about:blank"
20:45
<smaug____>
aha, thanks