Spec Metadata Lists Incorrect Values for Chrome

[jpmedley]

The Browser Support heading in the spec manifest shows support in Chrome as 89. If I hover over the label it expands to show Chrome support in 86 through 89. (I'm not sure why I thought to hover. There's no affordance suggesting that I should do that.)

Chrome has actually supported web app manifest since 39. There is a similar problem with the Chrome Android label.

Also Chrome 89 does not even exist yet. The current dev channel is Chrome 88.

[christianliebel]

Hi Joe! From my understanding, the browser support section shows data from caniuse.com, where the Chrome support data appears to be correct: https://caniuse.com/web-app-manifest

The caniuse integration in ReSpec retrieves the four latest versions of a browser (https://github.com/w3c/respec/blob/develop/src/core/caniuse.js#L108), showing the latest one on the label, and hiding the previous three in the submenu. This includes prerelease versions. My installation of Chrome Canary is on version 89 already, so it seems as if M89 is already in preview.

It may make sense to show the latest released version of the browser on the label and all supported versions in the hover menu. That however would be a feature request for ReSpec.

.cc @sidvishnoi @marcoscaceres

[jpmedley]

I'll open a ticket on respec. In the meantime, I'd suggest removing it completely because it's showing incorrect data.

[sidvishnoi]

It may make sense to show the latest released version of the browser on the label and all supported versions in the hover menu.

The default number of browsers can be adjusted in respecConfig (https://respec.org/docs/#caniuse):

var respecConfig = {
  caniuse: {
    feature: "web-app-manifest",
    versions: 10,
  },
};

Though, showing too many versions might become too clumsy. I'll try to see if we can group versions like caniuse.com does.

[sidvishnoi]

Also, I'm not sure if it'll add much value as we do not intend to copy the caniuse table into ReSpec/spec. This is what the "More info" link is for.

[jpmedley]

I'm less concerned with how you get there than I am about the fact that it looks like its presenting incorrect information. Joe Medley | Technical Writer, Chrome DevRel | jmedley@google.com | 816-678-7195 *If an API's not documented it doesn't exist.*

…

On Tue, Nov 17, 2020 at 9:21 AM Sid Vishnoi ***@***.***> wrote: Also, I'm not sure if it'll add much value as we do not intend to copy the caniuse table into ReSpec/spec. This is what the "More info" link is for. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#939 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6S7C373I45X62YB24P7JDSQKWJXANCNFSM4TYZUBIQ> .

[marcoscaceres]

I agree that what it shows is not great. sidvishnoi/respec-caniuse-route#8 would solve the problem via the grouping.

I guess the best thing to do here right now would be to just set "versions" to 1. That disables the hover behavior and just shows the latest supported version.

@jpmedley, would that be suitable?

[christianliebel]

I am closing this as the browser support section now links to caniuse.com.