Contact emails
Explainer
The spec says that iframe and frame elements have a "scrolling" attribute that can be set to "no", "off", or "noscroll" to disable scrollbars. Until now, Chromium has only supported the "no" value. This I2S ships support for the other two values.
This I2S was suggested by the reviewers for my CL implementing this change.
Spec
https://html.spec.whatwg.org/multipage/rendering.html#the-page
The interesting part:
If a Document's browsing context is a child browsing context, the container of that browsing context is a frame or iframe element, that element has a scrolling attribute, and that attribute's value is an ASCII case-insensitive match for the string "off", "noscroll", or "no", then the user agent is expected to prevent any scrollbars from being shown for the viewport of the Document's browsing context, regardless of the 'overflow' property that applies to that viewport.
Because this change is already specified and is very small, I don't believe a TAG review is required.
Summary
See Explainer above.
Link to “Intent to Prototype” blink-dev discussion
Since this is already specified behavior, and Firefox already implements the spec, I did not go through the full I2P process for this change.
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Demo link
Debuggability
Devtools will show the state of the "scrolling" attribute.
Risks
Interoperability and Compatibility
There is a very small risk here, in that a page might currently set scrolling="no" or scrolling="noscroll", and expect the scrollbars to still show up. That seems unlikely to happen (and quite likely a site bug), especially since on Firefox, that would already result in no scrollbars. But it is a possibility.
Edge: No signals
Firefox: Shipped
Safari: No signals, but a bug has been filed and work started.
Web / Framework developers: No signals
Ergonomics
Pretty clean, I think.
Activation
No issues.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
Tests have been added, here. (At the time of this email, another more complete test is stuck in the WPT PR queue, here. Hopefully that also lands soon.)
Entry on the feature dashboard
This is a very small change, and I don't think it warrants a chromestatus entry.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDg2W9xWTGfQ7RGjiNT%2BX%3Da80MmxpGcfd27UGm7hFfVn6Q%40mail.gmail.com.
LGTM1
(I would probably not have minded if this had been a PSA but I
also don't mind the time it takes to determine that it's a simple
change and write LGTM)
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B-LeH_z%3D67tLc8rtHVBO555qZsyS-RwpEy0T1pgcfhspZQyGA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDhqBVb2T2%2BnmqapePwfEtX7GQRJYBG5zQacyW407yA6bA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEh56WxiDWzR4WwQhe6%2B5r80t-eGQfu8CqVE9cyxvOcW9g%40mail.gmail.com.