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

<iframe seamless> can be removed #2232

Closed
annevk opened this issue Jan 22, 2016 · 7 comments
Closed

<iframe seamless> can be removed #2232

annevk opened this issue Jan 22, 2016 · 7 comments

Comments

@annevk
Copy link
Contributor

annevk commented Jan 22, 2016

See whatwg/html@1490eba.

@Fyrd
Copy link
Owner

Fyrd commented Jan 23, 2016

Features generally aren't removed from caniuse, but I can mark it as "unofficial". Do you have a link to an explanation somewhere on why it was removed?

@annevk
Copy link
Contributor Author

annevk commented Jan 24, 2016

It'll be a little self-referential whatwg/html#331. 😊

The main problem for us is that caniuse.com is pointing to the HTML Standard for this feature at the moment, which ends up generating an warning/error in our build script since we removed it.

@Fyrd
Copy link
Owner

Fyrd commented Jan 25, 2016

Ha, okay. Have updated the feature and changed the link to an older (w3c) version of the spec, which I assume will solve your issue?

@zcorpan
Copy link
Contributor

zcorpan commented Jan 25, 2016

Heh, nope, our build script still picks it up I believe. But we should get rid of that and make sure that caniuse consistently links to whatwg for not-dropped features... Filed whatwg/wattsi#14

@ZoeBijl
Copy link

ZoeBijl commented Jan 25, 2016

Related W3C HTML issue: w3c/html#35

@AndySky21
Copy link

changed the link to an older (w3c) version of the spec

I'm sorry, but the version of W3C spec referenced by that is really old.
Besides, <iframe seamless> was still present in the last W3.org-"hosted" version of the draft, and still is in the version maintained on GitHub (and as I asked in the related W3C HTML bug I don't know what's the destiny for the latter).

@Fyrd
Copy link
Owner

Fyrd commented Jan 27, 2016

Yeah, I guess that spec was due to some lazy googling on my part. Have updated it now with the last one.

Closing this issue now since it seems to have been resolved.

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

No branches or pull requests

5 participants