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.

Sign up for GitHub

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

Jump to bottom

Is this still active? #37

Open
marcoscaceres opened this issue Dec 10, 2019 · 3 comments
Open

Is this still active? #37

marcoscaceres opened this issue Dec 10, 2019 · 3 comments

Comments

@marcoscaceres
Copy link
Contributor

This spec hasn't moved in a few years.... should we consider incubation complete and archive this repo? @RByers?
@marcoscaceres
Copy link
Contributor Author

marcoscaceres commented Feb 16, 2023 •
edited
Loading

Just checking in again for status.

Wonder if we should archive this repo or consider moving any tangible ideas to a W3C Working Group?

@RByers
Copy link
Member

RByers commented Feb 16, 2023

Sorry I missed your first ping. We ship this API in chromium and it has significant usage but AFAIK no other engine has expressed interested in implementing it. That may be because mouse+touchscreen scenarios are somewhat niche and largely confined to Windows and Chromebooks. So we must continue to ship this API in chromium and will want to ensure IP protection for it somehow, but I can understand why it's unlikely to be a priority for WebKit, but unsure about Gecko. Any thoughts on how to best approach such a situation?

@RByers
Copy link
Member

RByers commented Feb 23, 2023

See request to migrate to UI Events here: w3c/uievents#108

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@marcoscaceres @RByers