Ticket #8468 (closed bug: wontfix)
Find by multiple selector return different value in Opera
| Reported by: | anonymous | Owned by: | anonymous |
|---|---|---|---|
| Priority: | low | Milestone: | 1.7 |
| Component: | selector | Version: | 1.5.1 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description (last modified by ajpiano) (diff)
Requirements in html:
- element input with class 'vdata' doesn't exists in html
- element select with class 'vdata' exists in html
Query: jQuery(this).find("input.vdata,select.vdata :selected").val();
query return 'undefined' in Opera in IE 8, Chrome 9.0.597.107 and Firefox 3.6.13 return selected value in element 'select'
Change History
comment:2 Changed 2 years ago by anonymous
- Status changed from pending to new
I simplify test case...
comment:3 Changed 2 years ago by dmethvin
- Status changed from new to open
Confirmed in Opera 11.01 on Windows; I simplified the test case a bit and tried a few permutations:
comment:4 Changed 2 years ago by dmethvin
- Priority changed from undecided to high
- Component changed from unfiled to selector
- Milestone changed from 1.next to 1.6
comment:7 Changed 2 years ago by john
- Status changed from open to pending
I think this may have been fixed in Opera 11.1. Can you confirm?
comment:8 Changed 2 years ago by timmywil
- Status changed from pending to open
Confirmed http://jsfiddle.net/timmywil/PKCG7/4/
comment:10 Changed 2 years ago by scott.gonzalez
Why is this not higher priority? Having simple selectors fail seems like a blocker.
comment:11 Changed 2 years ago by scott.gonzalez
This is the cause for http://bugs.jqueryui.com/ticket/7094
comment:13 Changed 2 years ago by john
- Keywords browser-opera,1.7-discuss added; browser-opera removed
Nominating ticket for 1.7 discussion.
comment:14 Changed 2 years ago by rwaldron
- Description modified (diff)
+1, Seems like a bug, should be fixed
comment:15 Changed 2 years ago by jaubourg
+1, weird
comment:16 Changed 2 years ago by timmywil
+1,
comment:17 Changed 2 years ago by gnarf
- Description modified (diff)
This seems to be an issue in Opera itself... It isn't throwing an exception for Unknown psuedo class when the non-standard :selected is on the right side of the comma...
comment:18 follow-up: ↓ 20 Changed 2 years ago by dmethvin
-1, As discussed in the Monday meeting, this is an Opera bug so I think we should close it wontfix and let the Operatics do their thing.
comment:19 Changed 2 years ago by john
- Description modified (diff)
+0, I fear what's actually happening here. Opera's querySelectorAll is really bad.
comment:20 in reply to: ↑ 18 Changed 2 years ago by scott.gonzalez
- Description modified (diff)
Replying to dmethvin:
-1, As discussed in the Monday meeting, this is an Opera bug so I think we should close it wontfix and let the Operatics do their thing.
Isn't one of the main purposes of jQuery to overcome browser bugs?
comment:22 Changed 2 years ago by ajpiano
- Description modified (diff)
+0, If this is an opera bug and only affects pseudoselectors, we might have to suck it up. Seems like it could be high cost, low reward...and there could be a fixed Opera, and we know how Opera users are (they love updating).
comment:23 Changed 2 years ago by miketaylr
This was an Opera bug, but it's been fixed in Presto since reported. The problem was "querySelectorAll does not throw for an unsupported pseudo-class part of selector if there is a valid part first."
So, either wait for your users to upgrade to whatever version the fix gets integrated (12? dunno), or don't use custom non-QSA selectors.
comment:24 Changed 2 years ago by rwaldron
- Keywords browser-opera,1.7-discuss removed
- Priority changed from blocker to low
- Milestone changed from 1.next to 1.7
comment:25 Changed 2 years ago by rwaldron
- Status changed from open to closed
- Resolution set to wontfix
comment:26 Changed 18 months ago by sindresorhus
#10921 is a duplicate of this ticket.
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

Hi, can you please post a test case built using jsfiddle.net? The code snippet you provided isn't enough since it's not even clear what "this" is.