Open bkardell opened 1 month ago
othermaciej
commented
2 weeks ago @bkardell the Mozilla standards-positions URL field is meant to be for a link to an issue in Mozilla’s standards-positions repo, not an interop issue that indirectly claims a positive position. We want to see Mozilla’s reasoning, not just their final answer, ideally.
othermaciej
commented
2 weeks ago Ok this was a bit confusing but it seems the changes in the fork are actually merged to the W3C Intersection Objeserver spec, which is owned by the W3C Web Applications Working Group.
PR: https://github.com/w3c/IntersectionObserver/pull/523 Diff: https://pr-preview.s3.amazonaws.com/w3c/IntersectionObserver/523/ef83cd2...szager-chromium:885a800.html
WebKittens
@hober @annevk @marcoscaceres
Title of the proposal
Intersection Observer v2
URL to the spec
https://w3c.github.io/IntersectionObserver/
URL to the spec's repository
https://github.com/W3C/IntersectionObserver
Issue Tracker URL
https://github.com/W3C/IntersectionObserver/issues/
Explainer URL
https://github.com/szager-chromium/IntersectionObserver/blob/master/explainer.md
TAG Design Review URL
No response
Mozilla standards-positions issue URL
https://github.com/mozilla/standards-positions/issues/109
WebKit Bugzilla URL
No response
Radar URL
No response
Description
This was added as a potential area to Interop 2025 and it lists a positive Mozilla position, but no position from WebKit.