Philip Jägenstedt

Results 336 issues of Philip Jägenstedt

Notes are originally from https://github.com/mdn/browser-compat-data/pull/21937.

data:css :art:

### What type of issue is this? Incorrect support data (example: BrowserX says "86" but support was added in "40") ### What information was incorrect, unhelpful, or incomplete? https://github.com/mdn/browser-compat-data/pull/21621 added...

data:css
p3

There's CSS data with these ranges for CSS property values based on https://github.com/openwebdocs/mdn-bcd-collector where data going back to the original support of the property wasn't available. We can't use this...

data:css :art:

### What type of issue is this? Incorrect support data (example: BrowserX says "86" but support was added in "40") ### What information was incorrect, unhelpful, or incomplete? https://developer.mozilla.org/en-US/docs/Web/API/IntersectionObserverEntry doesn't...

data:api :rabbit2:

@stephenmcgruer has let me know: > Was going through handover tasks and realized we have a bit of a tricky issue with DockerHub (which we use to host wpt.fyi and...

infra
priority:backlog

@andreban asked if there's a way to know what the score of the next stable Chrome release is going to be before it happens. The answer is no, because we...

The problem is that first we do this to populate the most recent runs: https://github.com/web-platform-tests/results-analysis/blob/e16852115077721b680c5a3e1a9a99b7ac66fb4f/build.sh#L17 The in various scoring scripts, we use the wpt.fyi API to enumerate runs: https://github.com/web-platform-tests/results-analysis/blob/e16852115077721b680c5a3e1a9a99b7ac66fb4f/interop-scoring/main.js#L405-L406 And...