Bug Tracker

Opened 8 years ago

Closed 8 years ago

#7567 closed bug (invalid)

jQuery passes too much elements to Sizzle.filter in Internet Explorer

Reported by: thereloaded Owned by: thereloaded
Priority: undecided Milestone: 1.5
Component: unfiled Version: 1.4.4
Keywords: Cc:
Blocked by: Blocking:

Description

In Internet Explorer more elements are passed and matched in Sizzle.filter than actually exist on the page.

I made a testcase. Its not really beautiful, but maybe enough to illustrate: http://jsfiddle.net/VySgC/4/ Just click on the firebug-icon in the right-bottom corner to see the results. (sometimes the console is empty, dunno why, try to use Ctrl+F5).

Change History (8)

comment:1 Changed 8 years ago by snover

Owner: set to thereloaded
Status: newpending

Your test case does not work. Please provide a working, reduced test case showing only the bare minimum code necessary to illustrate your problem. Read the How to Report Bugs for more detailed instructions.

comment:2 Changed 8 years ago by anonymous

uhm. what doesnt work? works perfect in any browser (ie7, ie8, ff, safari, chrome, opera) and any computer i've access.

comment:3 Changed 8 years ago by thereloaded

Status: pendingnew

ok, i guess my description is maybe not enough.

In firefox only one element is passed to Sizzle.filter and in internet explorer 8 and opera there are 4 elements. for firefox the one element doesnt match. for ie8 there are 4 matches for CLASS, 1 for PSEUDO and 3 for TAG. In opera there are 3 matches for CLASS and 3 for TAG.

also is it allowed to use firebug-lite for my testcase. or do i have to echo the results to the resultwindow?

comment:4 Changed 8 years ago by jitter

Status: newpending

There are several issues with your test case.

1) It seems to use a modified version of jQuery 1.4.4. You failed to even mentioned that. Nor did you explain what the modifications do.

2) The server where this modified version resides seems to return a 404 for this file for every other request which makes debugging very difficult.

3) The javascript code is wrapped twice

window.onload=function(){
    jQuery(document).ready(function(){
      ....
    })
}

4) The inner-workings of jQuery/Sizzle are non trivial and the results you see might have to do with different browsers quirks which jQuery handles for you. By e.g. having to call certain internal functions more often then you expect it to.

5) It isn't really clear what you expect the output to be.

So unless you can show specifically that/what jQuery/Sizzle does wrong in your opinion by providing a test where the result is wrong I guess it will be unlikely that someone is going to take the time to reverseengineer what your complaint is about.

If you mean to report a "performance" issue (e.g. Opera/IE do more work then necessary when selecting stuff) you should even more go into detail where you think jQuery/Sizzle goes wrong

Last edited 8 years ago by jitter (previous) (diff)

comment:5 Changed 8 years ago by thereloaded

Status: pendingnew

sorry for the inconvenience, i tried to get some answers on the forum, but the only advice i got was to file a bugreport. i will rework my testcase and write a better documentation. thanks a lot.

comment:6 in reply to:  5 Changed 8 years ago by jitter

Replying to thereloaded:

sorry for the inconvenience, i tried to get some answers on the forum, but the only advice i got was to file a bugreport. i will rework my testcase and write a better documentation. thanks a lot.

No need to be sorry. If you could provide a clearer test case that would be great then we will further investigate the issue.

Adding the post you are where referring to

jQuery Forum thread

Last edited 8 years ago by jitter (previous) (diff)

comment:7 Changed 8 years ago by snover

Status: newpending

Set to pending close until/unless bug reporter provides a workable test case.

comment:8 Changed 8 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.