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

Implement proposed Focus Traversal API #4784

Open
arei opened this issue Jul 17, 2019 · 6 comments
Open

Implement proposed Focus Traversal API #4784

arei opened this issue Jul 17, 2019 · 6 comments
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: focus

Comments

@arei
Copy link

arei commented Jul 17, 2019

Implement the proposed Focus Traversal API as explained here: https://github.com/awesomeeng/FocusTraversalAPI/blob/master/EXPLAINER.md

and discussed here: https://discourse.wicg.io/t/proposal-focus-traversal-api/3427

additional details and a sample polyfill can be found here: https://github.com/awesomeeng/FocusTraversalAPI

@domenic
Copy link
Member

domenic commented Jul 17, 2019

It's a bit unclear what this issue is about. Are you hoping to merge your spec into the HTML Standard? Or did you mean to file this on the implementer bug trackers instead, asking them to implement your spec?

@arei
Copy link
Author

arei commented Jul 17, 2019

@domenic I am proposing adding this to the spec with the end result getting it implemented across browsers. I am happy to undertake whatever steps are necessary to make this happen, but am completely at a loss as to what they are. As you can see, it was proposed to the WICG but I largely think that is ignored.

@arei
Copy link
Author

arei commented Jul 17, 2019

I am also very open to suggestions, discussion, changes, comments, etc.

@domenic
Copy link
Member

domenic commented Jul 17, 2019

Ah, OK. Well, the thing is, the working mode for the HTML Standard is kind of the opposite of that. Putting things in the spec doesn't somehow force browsers to implement them. Instead, we work together to gain browser interest and implementations, and then formalize them in the spec. You can learn more at https://whatwg.org/working-mode, in particular https://whatwg.org/working-mode#additions. https://whatwg.org/faq#adding-new-features may also be helpful.

In general, large features like this work best if incubated in a venue like the WICG, then implemented in at least one browser and gathering 2+ browser interest in implementing, and then we merge them in to the HTML Standard. So I think most of the work is still on you engaging browser vendors to see if they are interested in implementing your proposal.

Hope this helps!

@arei
Copy link
Author

arei commented Jul 18, 2019

#4607

@arei
Copy link
Author

arei commented Aug 6, 2019

I'll be speaking about the Focus Traversal API Proposal at JSCONF US 2019 next week (August 12 2019 @2:15pm, Track B). Hope to see some of you out there and talk more about making focus better!

https://2019.jsconf.us/speakers/glen-goodwin

@domenic domenic added addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: focus labels Sep 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: focus
Development

No branches or pull requests

2 participants