Intent to Implement and Ship: prevent scrolling in HTMLElement.focus()
91 views
Skip to first unread message
Ella Ge
Nov 3, 2017, 4:38:30 PM11/3/17
to blink-dev
Contact emails
Spec
https://html.spec.whatwg.org/multipage/interaction.html#focus-management-apis
Summary
This adds an optional focusOptions argument to Element.focus() API. The additional argument allows to disable scrolling triggered by focus().
Motivation
Currently, there’s no way to request the scrolling to no scrolling when calling Element.focus(). Disable scrolling have use cases such as: JS is focusing an element based on pointer hover(for TV). See discussion here.
Web developers want to be able to prevent scrolling when focus, so they can use focus with scrollIntoView to achieve focus with scrolling behavior.
Link to “Intent to Implement” blink-dev discussion
Here is an intent to implement. But spec proposal changed after I sent that.Interoperability and Compatibility Risk
Edge: In development Link
Firefox:In development Link
Safari: In development Link
Web developers: Positive Link
Ongoing technical constraints
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Is this feature fully tested by web-platform-tests?
Yes
https://github.com/w3c/web-platform-tests/pull/7915
https://github.com/w3c/web-platform-tests/pull/7917
OWP launch tracking bug
Link to entry on the feature dashboard
https://www.chromestatus.com/feature/5745122025144320
Requesting approval to ship?
Yes
Ella
Brian Birtles
Nov 5, 2017, 6:05:22 PM11/5/17
to blink-dev
2017年11月4日土曜日 5時38分30秒 UTC+9 Ella Ge:
Thanks for doing this. When you update the feature dashboard it might be better to say, "bugs filed" as opposed to "in development" since there doesn't seem to be any evidence of actual development in other browsers yet? For Firefox you could go a step further and say Mozilla is supportive based on Olli's comment.[1]
(Also, regarding Web developers, perhaps it should link to the discourse issue. In the currently linked-to thread there seems to be only one comment from a non-browser vendor / spec editor and it just links to the discourse issue.)
eir...@chromium.org
Nov 6, 2017, 11:22:28 AM11/6/17
to blink-dev
Thanks for the comment. I didn't find "bugs filed" in the feature dashboard, so I changed Safari and Edge 's status there to "No public signal" and changed Firefox's link. Should I delete this "intent" and resend another one?
Chris Harrelson
Nov 6, 2017, 3:02:40 PM11/6/17
to eir...@chromium.org, blink-dev
LGTM1
--
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+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d4a89529-603f-47d3-893a-84e6e5cc8c76%40chromium.org.
Rick Byers
Nov 7, 2017, 12:26:21 AM11/7/17
to Chris Harrelson, Ella Ge, blink-dev
LGTM2
On Mon, Nov 6, 2017 at 3:02 PM, Chris Harrelson <chri...@chromium.org> wrote:
LGTM1On Mon, Nov 6, 2017 at 8:22 AM, <eir...@chromium.org> wrote:Thanks for the comment. I didn't find "bugs filed" in the feature dashboard, so I changed Safari and Edge 's status there to "No public signal" and changed Firefox's link. Should I delete this "intent" and resend another one?
No no, this thread is totally fine :-). There's definitely a grey area here and these values tend to change over time.
On Sunday, November 5, 2017 at 6:05:22 PM UTC-5, Brian Birtles wrote:2017年11月4日土曜日 5時38分30秒 UTC+9 Ella Ge:Thanks for doing this. When you update the feature dashboard it might be better to say, "bugs filed" as opposed to "in development" since there doesn't seem to be any evidence of actual development in other browsers yet? For Firefox you could go a step further and say Mozilla is supportive based on Olli's comment.[1]
Yeah I'd say this counts as "public support". I updated the entry.
----(Also, regarding Web developers, perhaps it should link to the discourse issue. In the currently linked-to thread there seems to be only one comment from a non-browser vendor / spec editor and it just links to the discourse issue.)
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+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d4a89529-603f-47d3-893a-84e6e5cc8c76%40chromium.org.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-p8_QH7%2B6NroK9%3DxxaYYKdT2iFmSCwwb17zTfzUzWzhg%40mail.gmail.com.
Daniel Bratell
Nov 8, 2017, 12:39:59 PM11/8/17
to Chris Harrelson, Rick Byers, Ella Ge, blink-dev
LGTM3
(Though the "Edge: in development" is not something I can read from the link but it doesn't change what I think)
/Daniel - using new powers for good in the world!
LGTM2
On Mon, Nov 6, 2017 at 3:02 PM, Chris Harrelson <chri...@chromium.org> wrote:LGTM1On Mon, Nov 6, 2017 at 8:22 AM, <eir...@chromium.org> wrote:Thanks for the comment. I didn't find "bugs filed" in the feature dashboard, so I changed Safari and Edge 's status there to "No public signal" and changed Firefox's link. Should I delete this "intent" and resend another one?No no, this thread is totally fine :-). There's definitely a grey area here and these values tend to change over time.On Sunday, November 5, 2017 at 6:05:22 PM UTC-5, Brian Birtles wrote:2017年11月4日土曜日 5時38分30秒 UTC+9 Ella Ge:Thanks for doing this. When you update the feature dashboard it might be better to say, "bugs filed" as opposed to "in development" since there doesn't seem to be any evidence of actual development in other browsers yet? For Firefox you could go a step further and say Mozilla is supportive based on Olli's comment.[1]Yeah I'd say this counts as "public support". I updated the entry.
(Also, regarding Web developers, perhaps it should link to the discourse issue. In the currently linked-to thread there seems to be only one comment from a non-browser vendor / spec editor and it just links to the discourse issue.)
--
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/d4a89529-603f-47d3-893a-84e6e5cc8c76%40chromium.org.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-p8_QH7%2B6NroK9%3DxxaYYKdT2iFmSCwwb17zTfzUzWzhg%40mail.gmail.com.
--
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/CAFUtAY-rqh8975d0AuwerMpYGPZQpEbDK3KgUFUyTgFO523ZGQ%40mail.gmail.com.
--
/* Opera Software, Linköping, Sweden: CET (UTC+1) */
eir...@chromium.org
Nov 8, 2017, 1:52:46 PM11/8/17
to blink-dev, chri...@chromium.org, rby...@chromium.org, eir...@chromium.org, bra...@opera.com
On Wednesday, November 8, 2017 at 12:39:59 PM UTC-5, Daniel Bratell wrote:
LGTM3(Though the "Edge: in development" is not something I can read from the link but it doesn't change what I think)
Sorry for the confusion, it should be:
Firefox: Public support
Edge: No public signals
Safari: No public signals
/Daniel - using new powers for good in the world!On Tue, 07 Nov 2017 06:25:52 +0100, Rick Byers <rby...@chromium.org> wrote:LGTM2On Mon, Nov 6, 2017 at 3:02 PM, Chris Harrelson <chri...@chromium.org> wrote:LGTM1On Mon, Nov 6, 2017 at 8:22 AM, <eir...@chromium.org> wrote:Thanks for the comment. I didn't find "bugs filed" in the feature dashboard, so I changed Safari and Edge 's status there to "No public signal" and changed Firefox's link. Should I delete this "intent" and resend another one?No no, this thread is totally fine :-). There's definitely a grey area here and these values tend to change over time.On Sunday, November 5, 2017 at 6:05:22 PM UTC-5, Brian Birtles wrote:2017年11月4日土曜日 5時38分30秒 UTC+9 Ella Ge:Thanks for doing this. When you update the feature dashboard it might be better to say, "bugs filed" as opposed to "in development" since there doesn't seem to be any evidence of actual development in other browsers yet? For Firefox you could go a step further and say Mozilla is supportive based on Olli's comment.[1]Yeah I'd say this counts as "public support". I updated the entry.
Thanks Rick!
(Also, regarding Web developers, perhaps it should link to the discourse issue. In the currently linked-to thread there seems to be only one comment from a non-browser vendor / spec editor and it just links to the discourse issue.)
--
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+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d4a89529-603f-47d3-893a-84e6e5cc8c76%40chromium.org.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-p8_QH7%2B6NroK9%3DxxaYYKdT2iFmSCwwb17zTfzUzWzhg%40mail.gmail.com.
--
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+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY-rqh8975d0AuwerMpYGPZQpEbDK3KgUFUyTgFO523ZGQ%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages