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

Double click in an XML attribute only selects one character #132

Closed
rhdunn opened this Issue Oct 30, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@rhdunn

rhdunn commented Oct 30, 2015

If I have an XML fragment such as:

<basic:json type="object"></basic:json>

Double clicking on basic, json and type select the word as expected, but double clicking on object (i.e. the string content within the attribute) only selects a single character, where it should select the word.

NOTE: Given something like:

let $msg := "Hello World";

Double clicking inside that string selects the word as expected (i.e. Hello or World in this example).

@rhdunn

This comment has been minimized.

Show comment
Hide comment
@rhdunn

rhdunn Oct 30, 2015

The same thing happens for text nodes. For example:

<p>Hello</p>

Double clicking Hello only selects a single character.

rhdunn commented Oct 30, 2015

The same thing happens for text nodes. For example:

<p>Hello</p>

Double clicking Hello only selects a single character.

@ligasgr

This comment has been minimized.

Show comment
Hide comment
@ligasgr

ligasgr Nov 15, 2015

Owner

Double clicking as well as using ctrl-w (select word) relies on the elements in internal AST being represented as separate tokens. Currently all of the elements that you mentioned are all having each character treated as a separate token.
I'll consider changing the lexical analysis change to see if it's possible to merge/group them.

Owner

ligasgr commented Nov 15, 2015

Double clicking as well as using ctrl-w (select word) relies on the elements in internal AST being represented as separate tokens. Currently all of the elements that you mentioned are all having each character treated as a separate token.
I'll consider changing the lexical analysis change to see if it's possible to merge/group them.

@ligasgr ligasgr added the feature label Nov 15, 2015

@ligasgr ligasgr closed this in 15f14fb Nov 17, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment