Make all plugin-related APIs no-ops

[domenic]

Part of #6003. /cc @mfreed7 @annevk

• At least two implementers are interested (and none opposed):
  • Chrome: https://groups.google.com/a/chromium.org/g/blink-dev/c/bbxAGu90LgM/m/aKNlwPAMAQAJ
  • Firefox already does this
• Tests are written and can be reviewed and commented upon at:
  • Move navigator layout test to WPT web-platform-tests/wpt#27534
• Implementation bugs are filed:
  • Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=1164635
  • Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1691513 (suggesting simplification to the code; no behavior changes necessary)
  • Safari: https://bugs.webkit.org/show_bug.cgi?id=220495

(See WHATWG Working Mode: Changes for more details.)

---

/index.html ( diff )
/obsolete.html ( diff )
/system-state.html ( diff )

[annevk]

This looks nice. I hope we can remove some of these interfaces down the line, but this is a great start.

[annevk]

Yeah, a cleanup bug against Firefox would be nice. Will you also file a follow-up issue on Plugin and MimeType?

[annevk]

It might be worth waiting with landing this until Chrome is a bit further along, just to be sure.

[domenic]

@mfreed7 did your change to Chrome come with web platform tests?

[mfreed7]

@mfreed7 did your change to Chrome come with web platform tests?

@domenic no, sorry, I didn't include any WPTs for this. I did make a layout test that could easily be converted to a WPT. Should I do that? I'm still in "monitoring" mode for this change, with some anticipation of PDF-related problems, due to this comment. But I'm happy to move that test over to WPT if you think it would be valuable now.

[domenic]

Yeah, converting that test would be ideal!

[domenic]

@mfreed7 ping on converting that layout test to a WPT?

[mfreed7]

@mfreed7 ping on converting that layout test to a WPT?

Yep, thanks for the ping. I was waiting to see how back the fallout was for the original change, but it seems (??) like it might be ok. I'll convert this test to WPT today.

[saschanaz]

This removes indexed property getters and thus removes @@iterator. As it could cause webcompat issue, probably need to revive the getters?

Or maybe okay when we want to completely remove the interfaces. #6317

[domenic]

How could it cause web compat issues?

[saschanaz]

for (const plugin of navigator.plugins) {} may fail if anyone is doing it.

[domenic]

I'm not sure how worried we should be about that...

[saschanaz]

@annevk said we probably want to keep it for now, but yeah, no data to prove whether it will be a real issue.

[annevk]

If Chrome is removing them I'd be happy for Firefox to follow, to be clear. But it does mean behavior changes for us, contrary to OP.