Using gwtquery, how can we select elements with attributes having values containing more than one word?

Question

Say I want to select an element such as

<div class="my class">InnerHTML</div>

While this may be done easily using CSS selectors with [class="my class"], gwtquery has a difference in the sense that it doesn't take the quotation marks in the input. It only accepts values like [attribute=attributevalue].

When I applied the same selector in GQuery with the space in between, it returned no matches. I have a feeling that this might be because of some incorrect parsing in the library for such cases. Is this so?

If so, is there any other way I might select these elements using GQuery?

score 2 · Accepted Answer · answered May 23 '12 at 21:17

2

It works for me (at least with gwtquery-1.1.0 and gwt 2.4.0)

GQuery myClassDivs = $("div[class=\"my class\"]");

returns a match for <div class="my class"/>.

However, with the class attribute, it's generally better to use the ~= selector instead, because <div class="my class"/> and <div class="class my"/> should usually be treated as equivalent.

So I would suggest using

GQuery myClassDivs = $("div[class~=my][class~=class]");

This will also select something like <div class="my class special"/>, which is usually desirable.

answered May 23 '12 at 21:17

Chris Lercher

37,264
20
99
131

Thanks! Using multiple attribute selectors did work. I do agree with the \" usage style. I had tried that before. Somehow it didn't work. Of course, the problem might be independent of gquery and may instead be of some coding error elsewhere in my code. – Saurabh Agarwal May 25 '12 at 15:18

score 1 · Answer 2 · edited May 23 '17 at 12:20

Generally, to select attributes with space-separated words, you'll use the [att~=val] selector as mentioned by Chris Lercher.

Or, you know, since you're selecting by the class attribute anyway, you could just use class selectors instead:

GQuery myClassDivs = $("div.my.class");

Regarding this:

When I applied the same selector in GQuery with the space in between, it returned no matches. I have a feeling that this might be because of some incorrect parsing in the library for such cases. Is this so?

If you're referring to adding the space in your unquoted attribute value, it's not a parsing error in the library. The selector itself is invalid because spaces in unquoted attribute values are explicitly invalid.

If quoted attribute values aren't recognized, then that is a parsing error in the library.

Using gwtquery, how can we select elements with attributes having values containing more than one word?

2 Answers2