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

Google proposed Find in Page API under review by the TAG #165

Closed
BigBlueHat opened this issue Mar 14, 2018 · 2 comments
Closed

Google proposed Find in Page API under review by the TAG #165

BigBlueHat opened this issue Mar 14, 2018 · 2 comments
Labels
topic:affordances topic:APIs topic:user Interaction

Comments

@BigBlueHat
Copy link
Member

Review has been requested of the TAG for an API to allow Web apps to provide custom UX in place of the browsers text finding functionality: w3ctag/design-reviews#236

It proposes some events as well as an "extended" set of possible features including loading additional custom results and/or pre-loading not-yet-displayed data so that it can be found by the browsers text finding code.

This differs from the FindText API Working Group Note which focuses on enabling JavaScript-based text searching and Range finding.
@BigBlueHat
Copy link
Member Author

WICG discussion that turned into this proposal:
https://discourse.wicg.io/t/allowing-browser-find-in-page-to-find-non-dom-text/1205

@iherman iherman mentioned this issue Mar 15, 2018
Closed
@iherman
Copy link
Member

iherman commented Mar 15, 2018

Moved this issue to the general WG issues' list: w3c/publ-wg#27

@iherman iherman closed this as completed Mar 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic:affordances topic:APIs topic:user Interaction
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BigBlueHat @iherman