Sorting by last introduced date

[foolip]

A column with the most recent date that a browser shipped a feature would be useful to understand recent changes on the platform for features that aren't yet Baseline. web-features burndowns has a lastIntroducedDate which shows the concept. It's a bit like a "last modified" date and is the same as the Baseline low date for Baseline features.

If this date was published with web-features, could it be added as a column to webstatus.dev?

[jcscottiii]

This is definitely doable! (see next comment) But I need some more context around the purpose of the date.

I looked at the spreadsheet. I saw some rows where there is a value present for lastIntroducedDate, but not for computedBaselineLowDate. Is that correct? Or are those rows incomplete and there should be a value present for computedBaselineLowDate too?

I ask because of this statement:

is the same as the Baseline low date

The existing baseline column is already sorted by baseline low date. So I want to see if there's a need for it if they use the same date.

If there are rows where lastIntroducedDate can have a value but not computedBaselineLowDate, could you write a small caption that can show up when users hover over it? That will be helpful for users to understand the difference.

[jcscottiii]

Ignore my questions in my previous comment. I read the full e-mail thread.

lastIntroducedDate, which is the last time any browser shipped support. After all browsers support a feature, it's the same as the Baseline date

This clears everything up. Do you have an ETA of when this would land in web-features? That will help us plan when to adopt it.

[foolip]

I don't have an ETA no, I just filed web-platform-dx/web-features#1311 and haven't discussed it with @ddbeck previously. We'll discuss and I'll report back here with what to expect.

[foolip]

web-platform-dx/web-features#1514 would also make it much easier to compute this date from only web-features. (Currently you would also need BCD to get the dates.)