[Webkit-unassigned] [Bug 178515] New: How to reach full interoperability on default scrolling behavior for HTMLElement focus()
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Oct 19 07:54:08 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=178515
Bug ID: 178515
Summary: How to reach full interoperability on default
scrolling behavior for HTMLElement focus()
Product: WebKit
Version: Safari Technology Preview
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: HTML DOM
Assignee: webkit-unassigned at lists.webkit.org
Reporter: zcorpan at gmail.com
CC: cdumez at apple.com
Context is: https://github.com/w3c/csswg-drafts/pull/1805#issuecomment-337801758
> Ask browser vendors to consider if they want to get full interoperability on default scrolling behavior for focus(), and if so what the behavior should be. I can file issues.
The current situation is summarized in https://github.com/w3c/csswg-drafts/pull/1805#issuecomment-331383688 and repeated below.
Chrome, Opera, Safari behave as follows.
Entirely in view: No scrolling
Partially in view: Scrolling (block: nearest, inline: nearest)
Entirely out of view: Scrolling (block: center, inline: center)
Firefox, Edge behave as follows.
Entirely in view: No scrolling
Partially in view: No scrolling
Entirely out of view: Scrolling (block: nearest, inline: nearest)
Getting agreement between browsers here would give us a stable foundation to extend the focus() API with scrollOptions (or something) that can explain the default scrolling behavior and allow customizing alignment etc. It also makes the web platform more predictable for developers.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171019/d141f8c7/attachment-0001.html>
More information about the webkit-unassigned
mailing list