Feature removals in BCD use a misleading version range

[foolip]

I was sure I'd already filed an issue for this, but maybe it was for the old MDN site...

Take a look at this table:
https://developer.mozilla.org/en-US/docs/Web/API/FetchEvent/replacesClientId#browser_compatibility

The data for Edge being rendered here is:

"edge": {
  "version_added": "18",
  "version_removed": "79"
},

This is rendered as "18 — 79" on a red background. I think the natural interpretation of this that the feature was in versions 18-79, but the correct interpretation is that it was in Edge 18 only.

I think the logic here should be:

• The displayed end range is the version before version_removed in BCD.
• If that is the same as the start range, show just a single number on red, "18" in this case.

cc @Elchi3 @ddbeck

[foolip]

While in the area, I'll also the the chance to complain about the use of the wide em dashes (—) here. The narrow en dash (–) is more commonly used to represent ranges.

Edit: #3972

[teoli2003]

@foolip Is 79 a typo, and you meant 19 ?

[foolip]

@teoli2003 no, this is a case of something that was in Edge 18 and then removed in Edge 79, which is the case where the problem is the most obvious.

[teoli2003]

Oh yes, my bad, I understand now. Makes sense!

[caugner]

Duplicate of #6667.