Skip to content
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

HTML: autofocus="" overhaul #195

Closed
domenic opened this issue Jul 29, 2019 · 2 comments · Fixed by #343
Closed

HTML: autofocus="" overhaul #195

domenic opened this issue Jul 29, 2019 · 2 comments · Fixed by #343
Labels
position: positive venue: WHATWG Specifications in a WHATWG Workstream

Comments

@domenic
Copy link
Contributor

domenic commented Jul 29, 2019

Request for Mozilla Position on an Emerging Web Specification

  • Specification Title: Update to autofocus="" processing algorithm
  • Specification or proposal URL: Update autofocus processing algorithm whatwg/html#4763
  • Mozillians who can provide input (optional): @bzbarsky has commented on autofocus work in the past; @annevk has asked that we improve the foundations of autofocus before working on custom element focus features.

Other information

@tkent-google has been working on overhauling the autofocus processing model to better match browser behavior, while also making sense with the specification ecosystem, and avoiding surprising results for users. See some motivating issues in whatwg/html#3551 (raised by @bzbarsky) and whatwg/html#4563 (comment) (by @annevk).

Kent has a pull request at the above URL. However, we've had trouble getting other browsers to vet the proposal. As such it is hard for us to judge whether merging the spec PR, and implementing it in Chrome, would move us closer toward interop, or just create a new divergent behavior.

I am hoping that raising an issue on this repository will be a good way to get Mozilla input as to the proposed changes.

@bzbarsky
Copy link
Contributor

The proposal looks generally reasonable to me, fwiw. There are some parts of it that are not trivial to implement in Gecko, largely due to differences between the spec's model for some things nd Gecko's internal model, but I don't think will be too much of a problem in practice. @smaug----

@adamroach adamroach added the venue: WHATWG Specifications in a WHATWG Workstream label Nov 16, 2019
@dbaron
Copy link
Contributor

dbaron commented May 22, 2020

I think a bunch of the feedback actually happened in whatwg/html#4763, but we should have remembered to come back after that happened and make a conclusion here; I think this should probably be marked as worth prototyping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
position: positive venue: WHATWG Specifications in a WHATWG Workstream
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants