Browser-compat-data: Is "version_removed" inclusive?

[FranklinYu]

For example, support for Public Key Pins header is removed in Chrome since 72, which means that 71 is the last Chrome with this feature. However, from the rendered compatibility table, it seems like 72 is the last version. Which one is true?

[vinyldarkscratch]

We've defined version_removed as exclusive, or in translation, "Browser X version Y no longer supports this feature". However, looking at the compatibility data, you do strike a good point -- it makes it seem like that version still supported it, but future versions didn't.

@Elchi3, I'd love to get your input on this one!

[Elchi3]

The MDN rendering is wrong here. It is tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1417902. The good news is that I think we're unblocked on this one now.

[FranklinYu]

I’m not sure I understand that bug. Are we going to re-design the UI, or update the data schema?

And how is #591 related to this issue?

[vinyldarkscratch]

The schema will remain the same, but the renderer within Kumascript will be updated, from what I can tell in that tracking bug. That other issue is relevant because for us to show the prior browser version, we’d need to know what that version is!

[FranklinYu]

Cool. In the current version, I think the affected part is

https://github.com/mdn/kumascript/blob/c4ff934bcce1dc3ce873ffda7d8ee1170e56d023/macros/Compat.ejs#L196-L215

Right? In addition, should I close this issue and track the Bugzilla bug instead?

[Elchi3]

That is the affected part, correct. I think we can track here as well, so we don't forget about this issue. Implementation needs to be fixed in kumascript, though.