- From: hyojin via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Oct 2020 03:14:20 +0000
- To: public-css-archive@w3.org
> Has there been any movement on the default scrolling behavior for focus()?
Yep! It has been merged via [a commit](https://github.com/whatwg/html/commit/7a579c1cf3fddc68a634e74c12c457af258e6a80.) in Oct 2017.
You can quickly understand how `element.focus({preventScroll: true});` work on [this](https://developer.mozilla.org/en-US/docs/Web/API/HTMLOrForeignElement/focus).
I believe that the valuable changes in this thread would be needed for many developers.
Its [polyfill](https://github.com/stipsan/scroll-into-view-if-needed) has been widely used for several use cases such as custom scroller, arrow keys based navigation.
In my side(LG webOS), there are requirements about the following functionalities.
A: `element.focus({block: start});`
(It can be used for both aligning it in a customized way and mediating the different default behaviors between Chrome and Firefox.)
B: `element.scrollIntoView({scroll: if-needed});` or `element.scrollIntoView({preventScroll: true});`.
(The latter could be used with IntersectionObserver for selecting the 'already inside view' case.)
All the cases are mostly covered with the already proposed changes in this thread.
How could we drive this item? What should we discuss with more?
--
GitHub Notification of comment by anawhj
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/1805#issuecomment-716278718 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 October 2020 03:14:22 UTC