browser-compat-data
browser-compat-data copied to clipboard
mdn
Mark the item* microdata attributes as not supported by browsers
The API reflecting these attributes was removed already: https://github.com/mdn/browser-compat-data/pull/16226
The attributes have never had any effect beyond the API for accessing them, so it's fair to say these attributes are not supported.
A search for "itemscope" in the source of Chromium, Gecko and WebKit finds only old tests and similar, no code handling the attribute.
@Elchi3 they are documented on MDN and I think that makes sense since they're used by https://schema.org/docs/gs.html and probably other things. Should content be updated to just not have a BCD key then?
Should content be updated to just not have a BCD key then?
hm, I guess I would remove the compat tables on MDN and leave a note there saying that browsers do not necessarily need to support this. I mean so that absent a compat table readers are not wondering about the compat story.
I mean an all-false table also leaves the wrong impression that this is unusable, right?
Just removing the compat tables sounds good to me. Do you want me to do that before we move forward with this PR then?
I've sent https://github.com/mdn/content/pull/32926 to drop the compat tables. Should I just remove these entries from BCD then?
Yes, please remove them in this PR.
And as Will says in https://github.com/mdn/content/pull/32926#pullrequestreview-1975208128 use mdn/content's front-matter yaml to provide the spec url for these features in content directly then.
https://github.com/mdn/content/pull/32926 is merged now, so this should be good to go too.