Firefox vs. Chrome incompatibilities?

google-code-export / game-golem

Automatically exported from code.google.com/p/game-golem

0 stars 0 forks source link

Firefox vs. Chrome incompatibilities? #303

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Use  $children.eq(1).find('div[style*="graphics"]') in Firefox
2. Watch it fail to find anything.
3. Remove "[style*="graphics"]" and watch it work, at least if  the div is not 
nested.

Any cool replacements for .find in jQuery?

Original issue reported on code.google.com by 0Artifi...@gmail.com on 19 Apr 2011 at 3:46

GoogleCodeExporter commented 9 years ago

I've had success with .filter() before in cases where I couldn't make other 
things work well. You can access the parent, children, etc. without spoiling 
the context of the point at which the call is made.

Original comment by lur...@hotmail.com on 19 Apr 2011 at 9:00

GoogleCodeExporter commented 9 years ago

In reference to filter, I meant by passing a function to it that allows more 
complex testing than pure jQuery inline syntax allows.

Original comment by lur...@hotmail.com on 19 Apr 2011 at 9:02

GoogleCodeExporter commented 9 years ago

A lot of this stuff is purely because of the FF/GM sandbox - if we could get 
Golem to be a FF4 non-reloading extension (ie, can be updated without 
restarting FF) then it might let us update the FF version to the latest jQuery 
too.

Original comment by RycochetTM on 5 May 2011 at 4:17