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

Selecting across wbr element Bug 584141 #113

Open
nos111 opened this issue Oct 5, 2019 · 5 comments
Open

Selecting across wbr element Bug 584141 #113

nos111 opened this issue Oct 5, 2019 · 5 comments

Comments

@nos111
Copy link

nos111 commented Oct 5, 2019

Currently selecting text that contains a wbr element will not cross the wbr element.

The new behavior will select cross the wbr element.

https://bugzilla.mozilla.org/show_bug.cgi?id=584141

@annevk
Copy link
Member

annevk commented Oct 6, 2019

In particular, if we ever define the overall model of selection better, this is likely the behavior we want to describe for wbr.

@rniwa
Copy link
Contributor

rniwa commented Dec 10, 2019

Sorry, could you clarify how this will affect the selection API? Because the current doesn't specify precisely how user interaction would end up selecting content, this seems like UA dependent behavior. Or is your commentary about "define the overall model of selection" about defining precisely which nodes will be selected & when?

@annevk
Copy link
Member

annevk commented Dec 10, 2019

Given that there are interoperability issues because of this, I think it makes sense for the specification to define high-level selection operations (e.g., "select word", "select all") and their implications. Given how we organize other standards it seemed most natural to me that the model would be defined alongside the API.

@rniwa
Copy link
Contributor

rniwa commented Dec 10, 2019

Given that there are interoperability issues because of this, I think it makes sense for the specification to define high-level selection operations (e.g., "select word", "select all") and their implications. Given how we organize other standards it seemed most natural to me that the model would be defined alongside the API.

Could you elaborate more on what exactly you mean by "the model"? Like which nodes will be selected when extending selection?

@annevk
Copy link
Member

annevk commented Dec 10, 2019

Yeah, and which nodes are to be ignored and such for the purposes of determining boundaries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants