Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<applet> is hardly a thing now #6684

Merged
merged 2 commits into from Sep 5, 2017
Merged

<applet> is hardly a thing now #6684

merged 2 commits into from Sep 5, 2017

Conversation

annevk
Copy link
Member

@annevk annevk commented Aug 2, 2017

document.applets (which always return an empty collection) and a mention in the HTML parser, but that's it.

This is for whatwg/html#1399 and https://bugzilla.mozilla.org/show_bug.cgi?id=1386008.

document.applets (which always return an empty collection) and a mention in the HTML parser, but that's it.
@w3c-bots
Copy link

w3c-bots commented Aug 2, 2017

Build PASSED

Started: 2017-08-21 15:10:27
Finished: 2017-08-21 15:21:00

View more information about this build on:

@w3c-bots
Copy link

w3c-bots commented Aug 2, 2017

View the complete job log.

Sauce (safari)

@w3c-bots
Copy link

w3c-bots commented Aug 2, 2017

View the complete job log.

Chrome (unstable)

@w3c-bots
Copy link

w3c-bots commented Aug 2, 2017

View the complete job log.

Sauce (MicrosoftEdge)

Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like there could be some useful negative tests created here. E.g. that there is no CSP violation generated; that applet doesn't show up in the window named properties (by name or ID); that they don't have priority over divs in the document.* properties.

I think we should also introduce a -historical.html test for everything in the OP of whatwg/html#1399, perhaps consolidated into one file. Including user agent stylesheet stuff.

I know this is more work, but I do think especially given all the extra places we removed it from, having a nice set of tests for implementers will help.

Copy link
Member

@zcorpan zcorpan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes LGTM but I agree with @domenic that we should have more negative tests

@annevk
Copy link
Member Author

annevk commented Aug 21, 2017

Good call, found a bug in Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=757434.

annevk pushed a commit to whatwg/html that referenced this pull request Aug 21, 2017
This removes support for the applet element from:

* document.all[name]
* document[name]
* window[name]

Furthermore:

* document.applets now returns an empty array
* Removed handling for applet elements in <iframe sandbox>
* Removed rendering rules for applet elements
* Removed the element itself and HTMLAppletElement
* Applet elements now use HTMLUnknownElement

The HTML parser is intentionally not changed.

Tests: web-platform-tests/wpt#6684.

Fixes #454.
Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, although ideally we'd also have negative tests for the CSP violation stuff too... might be worth filing a tracking issue for that, at least.

}, "window cannot find applet")

test(() => {
assert_equals(self.getComputedStyle(document.getElementsByTagName("applet")[0], "").cssFloat, "none");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be nice to test vertical-align too.

@gsnedders
Copy link
Member

Is there any reason this isn't merged?

@annevk annevk merged commit 208fa49 into master Sep 5, 2017
@w3c-bots
Copy link

w3c-bots commented Sep 5, 2017

Build PASSED

Started: 2017-08-21 15:10:27
Finished: 2017-08-21 15:21:00

View more information about this build on:

@annevk annevk deleted the annevk/applet branch September 5, 2017 07:09
@annevk
Copy link
Member Author

annevk commented Sep 5, 2017

I'm not sure.

@domenic
Copy link
Member

domenic commented Sep 5, 2017

I mean, there's still some outstanding missing coverage per my last review. I guess I'll file an issue.

@annevk
Copy link
Member Author

annevk commented Sep 5, 2017

Ah yeah, that's probably why. But it seems better to have this checked in.

alice pushed a commit to alice/html that referenced this pull request Jan 8, 2019
This removes support for the applet element from:

* document.all[name]
* document[name]
* window[name]

Furthermore:

* document.applets now returns an empty array
* Removed handling for applet elements in <iframe sandbox>
* Removed rendering rules for applet elements
* Removed the element itself and HTMLAppletElement
* Applet elements now use HTMLUnknownElement

The HTML parser is intentionally not changed.

Tests: web-platform-tests/wpt#6684.

Fixes whatwg#454.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants