Side navigation
#12387 closed bug (invalid)
Opened August 24, 2012 09:17AM UTC
Closed August 24, 2012 12:55PM UTC
Last modified August 24, 2012 12:57PM UTC
Regression document ready
| Reported by: | nicolas.penin@dragon-angel.fr | Owned by: | nicolas.penin@dragon-angel.fr |
|---|---|---|---|
| Priority: | high | Milestone: | None |
| Component: | core | Version: | 1.8.0 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
I believe there is an issue document ready raised to early (in google chrome 21) :
you can compare on this fiddle : http://jsfiddle.net/neonp/KCsub/
Attachments (0)
Change History (4)
Changed August 24, 2012 12:42PM UTC by comment:1
| owner: | → nicolas.penin@dragon-angel.fr |
|---|---|
| status: | new → pending |
Changed August 24, 2012 12:48PM UTC by comment:2
Indeed however, I just find out that the issue is written clearly in the chrome console :
Uncaught Error: Syntax error, unrecognized expression: :not(:input))
Changed August 24, 2012 12:55PM UTC by comment:3
| component: | unfiled → core |
|---|---|
| priority: | undecided → high |
| resolution: | → invalid |
| status: | pending → closed |
Great, thanks for getting back. I believe it may be a duplicate of http://bugs.jquery.com/ticket/11355 . If not, please file a new bug with a further reduced test case. Thanks again!
Changed August 24, 2012 12:57PM UTC by comment:4
Actually, it is really a syntax error in where the previous version was maybe too permissive. Here is a reduced test case : http://jsfiddle.net/neonp/HLjtJ/
Hi Nicolas,
Thanks for the test case. It's a bit too complex to accurate debug what's happening here, although I don't believe it's an issue with document readiness. Could you perhaps reduce the jsfiddle example down further so we can easily see the bug?