api.Document.parseHTMLUnsafe_static - Incorrect Firefox support version about browser-compat-data HOT 3 CLOSED

The data comes from https://mdn-bcd-collector.gooborg.com/tests/api/Document/parseHTMLUnsafe_static , which matches what the BCD currently says.

My understanding is that

• this tool tracks the WebIDL - i.e. the presence properties/methods on the corresponding object.
• BCD doesn't track bugs as such - so even if a feature doesn't work correctly due to a bug we don't indicate the sub versions where that is true. This is a pragmatic decision.

@Elchi3 @queengooborg Is that correct? ^^^ - should we update to the fixed version for Firefox since the BCD data is "deceptive".

from browser-compat-data.

• this tool tracks the WebIDL - i.e. the presence properties/methods on the corresponding object.

By default, the collector determines if a feature is supported by its presence in WebIDL or otherwise, as that is the safest bet for 99% of features -- so for most features, yes, this is correct. However, not all features can be checked this way, so the collector supports custom tests, which is useful in cases like this one where support is not directly associated with the presence of the method/property.

• BCD doesn't track bugs as such - so even if a feature doesn't work correctly due to a bug we don't indicate the sub versions where that is true. This is a pragmatic decision.

This is incorrect. These cases are exactly why we have a partial_implementation property.

from browser-compat-data.

"Somewhat incorrect" - I've only seen partial implementation added at the beginning of an API introduction - not in the middle due to a late-breaking bug.
But thanks, I get your point.

from browser-compat-data.