-
Notifications
You must be signed in to change notification settings - Fork 44
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
Behavior or ZeroWidthSpace #253
Comments
Thanks for filing. I don't think we've explicitly covered it and this results on some edge-cases... From what I can tell a The intent is that it should be treated as whitespace in both contexts so this is a bug. (Note: see also #250 - I'll try to address these together) |
Appreciate the confirmation! Just to clarify - after you make any necessary changes, browsers will still need to update their versions of this in order for it to be supported right? |
Yes, that's right. I haven't tried to see what Safari does yet, does it behave similarly? |
Just confirmed that Safari (similar to Chrome) does not ignore the |
The documentation for scrolling to text fragment mentions that whitespace is ignored and I see explicit mention of how   characters are handled. However, I do not see any mention of how &ZeroWidthSpace is handled nor can I seem to link a text fragment that has &ZeroWidthSpace as a prefix.
Below is what I am trying to match with (what I think) is the relevant information extracted. I want to match the 2,806 (appears multiple times with the same suffix so requires a prefix).
What I've Tried:
Is there something I am missing here? What is the expected behavior of ZeroWidthSpace?
The text was updated successfully, but these errors were encountered: