-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use FrozenArray<double> for IntersectionObserver's thresholds attribute #114
Comments
This is important. Please do not ship |
Right, I got here from Intent to Ship: Intersection Observer on blink-dev. |
It's unclear why a new array each time is problematic in this case. Is the concern allocation or some other semantic issue (e.g. side-channels)? |
Semantic. It's important to preserve |
Why is it important? (honest question) |
Ping? Blink's IDL file already uses |
Ping again. |
@szager-chromium looks like the spec here needs updating. |
https://bugs.webkit.org/show_bug.cgi?id=260129 Reviewed by Ryosuke Niwa. This patch is to align WebKit with Web-Spec [1] and Blink / Chromium. [1] https://www.w3.org/TR/intersection-observer/#intersection-observer-interface GitHub Issue: w3c/IntersectionObserver#114 * Source/WebCore/page/IntersectionObserver.idl: Update * LayoutTests/imported/w3c/web-platform-tests/intersection-observer/idlharness.window-expected.txt: Rebaselined Canonical link: https://commits.webkit.org/266857@main
https://wicg.github.io/IntersectionObserver/#intersection-observer-interface
This is very similar to
Notification
'svibrate
andaction
attributes:https://notifications.spec.whatwg.org/#api
As it is, this would return a new array every time.
@annevk @bzbarsky @domenic
The text was updated successfully, but these errors were encountered: