-
Notifications
You must be signed in to change notification settings - Fork 43
Issues: WICG/scroll-to-text-fragment
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Scroll to the start node of the first text directive instead of its common ancestor
#259
opened Jul 9, 2024 by
jnjaeschke
Remove the mention of force-load-at-top from "Invoking Text Directives"
#258
opened May 24, 2024 by
amccreight
Please consider an alternative mitigation mechanism to word segmention
#251
opened Dec 15, 2023 by
hsivonen
Add informative note about the use of Unicode White_Space
i18n-tracker
Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
#249
opened Dec 14, 2023 by
hsivonen
Remove / Rephrase "4.3 Determine if Fragment Id is needed"
spec issue
#244
opened Nov 29, 2023 by
jnjaeschke
How should force-load-at-top interact with the new Navigation API
spec issue
#242
opened Nov 22, 2023 by
bokand
Ensure restrictions on text directive scrolling match reality
spec issue
#240
opened Nov 21, 2023 by
bokand
Please reconsider the use of collator-based search
i18n-needs-resolution
Issue the Internationalization Group has raised and looks for a response on.
spec issue
#233
opened Sep 28, 2023 by
hsivonen
It's unclear whether scroll to text fragment works with flat tree or not.
spec issue
#190
opened Aug 6, 2022 by
rniwa
[Spec] Incorrectly searches node data rather than rendered text
spec issue
#98
opened Mar 13, 2020 by
bokand
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.