jQuery Forum

after 1.4 jQuery got more rigid on using quotes when using attribute selectors

$('[name=value]') used to work fine but newer seems to require:
$('[name="value"]')

in your case :  tr[data-domain=' + sld + '_' + tld + ']

 try : tr[data-domain="' + sld + '_' + tld + '" ]

Hi,

Hi again guys,

Not sure if the following suggestions might help but:

Just before the append you could produce an alert for the element's html to check that it is correct.

You could use Chrome's debugging tools (Butterfly ?!)  to inspect the DOM before you append - Chrome
may have added an extra element or text node that interferes with the append. And, of course, check it
afterwards to see if the element is there but not visible.

Andy.

Hi again,

One thing I see that may be causing issues is use of meta characters like " . " and " [ " in your ID's. jQuery docs show these should be double escaped in selectors. It could be that use of these is not being handled consistently in all browsers
http://api.jquery.com/category/selectors/

In chrome the select always seems to get appended so a workaround for the options , and a more efficient method of appending elements , that you could try is to create the whole select as one string, including all the options and make one append instead of trying to append each option.

Append is the most costly part of the operation anyway, so this would cut down a lot of the indiviudal appends you are making anyway

You would need to modify your data() calls on the new options and add them with inline html5 type data attributes. Fortunately jQuery now reads those from html anyway when you look for the values with data() method.

My theory is that if the empty select makes it to the TD Ok, so should the whole html string with options included

After writing this i tried some double escaping in chrome of "[" and "]" in your options appendTo and it worked fine with exisiting code

EDIT: but part I double escaped is legitimate use of these brackets....   wierd. I would go with the full html string concept

Hi,

Hi,

the better solution is the first one I proposed....create one html string for complete select and make one append

var selHtml='<select class="......." >'

loop over json for options
selHtml +='<option >foo</option>
end loop

selHtml+= '</select>';


$(selector).html( selHtml)

bug? or improper escaping issues with meta characters....... not sure.

I don't understand still...

by the way - thanks for your replies still - your help is still much appreciated ;)

---
http://www.flexin.be

I was just going through this again, but even though I really appreciate the feedback regarding the escaping, I just rethought this over, and there is no escaping to be done really...

ok  looking closer I agree....I think I was off base about the escaping now that I look closer at your replace()'s

Changing the td:nth-child(3) to td:last makes your 2 row version work in chrome also and only fills first row select. Maybe a bug with nth-child. I never use that in selectors since it's easier to use eq()

Simply removing the :nth-child(3) declaration magically made it work for me. You might want to try and minimise your selectors a bit. Don't use redundant information (test.com/test_com is set into way too many elements), and use jQuery methods while you can.