-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Remove microdata API #208
Comments
So this is basically https://www.w3.org/Bugs/Public/show_bug.cgi?id=23080, right? The Gecko discussion for this is https://bugzilla.mozilla.org/show_bug.cgi?id=909633 |
@bzbarsky yeah it is, though that was filed against a W3C component so we were not aware of it. 😟 Sounds like we should remove the API then. Thank you. |
This removes the Microdata API and examples that depend on it due to lack of interest from implementations. It does not remove the Microdata attributes and model (which have seen adoption) or the application/microdata+json drag-and-drop functionality (of which the status is unclear).
Despite doing part of the implementation of this API for Presto, I'd be happy to merge this, but is there anything we should wait for before going ahead? If nobody shouts within 24 hours I'll make it so. |
Looks like people didn't remove this stuff from web platform tests. :( |
@zcorpan did file web-platform-tests/wpt#2521. I guess wpt is understaffed. |
The microdata API is "not currently planned" for Edge, "no longer pursuing" for Chrome, and "removed" for WebKit. Firefox remains the only implementer.
It also is not a very pretty API, with the custom HTMLPropertiesCollection craziness.
I think we should remove the API. Any Firefox developers want to comment?
(NOTE: this is not about removing the feature, i.e. removing the spec's advice on how to use certain attributes to mark up microdata information. You can still do that. Just use standard DOM APIs to access the resulting info.)
The text was updated successfully, but these errors were encountered: