Skip to main content

Bug Tracker

Side navigation

#14584 closed bug (fixed)

Opened November 28, 2013 02:06PM UTC

Closed December 20, 2013 09:49PM UTC

Last modified December 20, 2013 10:25PM UTC

Attribute Ends With case-insensitive in some IE8

Reported by: Owned by: gibson042
Priority: low Milestone: 1.11/2.1
Component: selector Version: 1.10.2
Keywords: Cc:
Blocked by: Blocking:

Attribute Ends With Selector [name$="value"] is case-insensitive in some IE8 (Tested with IE8 v.8.0.6001.18702 on Windows Vista).

You can reproduce with this jsFiddle

With my IE8, values for inputs "test1.value", "test2.value" and "testValue" are replaced with this script :


Only "test1.value" and "test2.value" should be replaced.

Attachments (0)
Change History (7)

Changed November 30, 2013 12:19AM UTC by gibson042 comment:1

component: unfiledselector
owner: → gibson042
priority: undecidedlow
status: newassigned

Confirmed. Fortunately, this particular querySelectorAll flaw seems to only affect the name attribute:

Changed December 02, 2013 04:02PM UTC by timmywil comment:2

resolution: → duplicate
status: assignedclosed

Duplicate of #12024.Case sensitivity affects many attributes (and not all of them). This is related to an existing Sizzle issue, which we will probably not fix as it requires maintaining a long list of attributes.

I suppose we could provide a smaller fix for the 2.x branch, but I'd be cautious about targeting specific 2.x issues in Sizzle.

Changed December 02, 2013 04:37PM UTC by gibson042 comment:3

resolution: duplicate
status: closedreopened

This is distinct from #12024 because the root cause is not Sizzle code but the IE8 querySelectorAll that incorrectly matches <input name="LOWER"/> against "[name=lower]".

Changed December 02, 2013 05:00PM UTC by timmywil comment:4

It is not distinct because even if we were to fix the result for IE8 (and I'd be surprised if name was the only attribute affected here), other browsers would continue to be inconsistent when it comes to case sensitivity and attributes. We could fix the name attribute across browsers if we see that attribute as more important than other attributes, but it seems like polishing the brass on the titanic if we're not going to tackle all of them.

Changed December 02, 2013 05:30PM UTC by timmywil comment:5

status: reopenedassigned

Alright, well looking at it from the perspective of providing case-sensitivity for all attribute across browsers (which is useful but still technically wrong), I'm fine with fixing this.

Changed December 20, 2013 09:49PM UTC by Richard Gibson comment:6

resolution: → fixed
status: assignedclosed

Selector: update Sizzle

Fix #14584

Changeset: 29c8003347e8768e26077c6d040203d662009220

Changed December 20, 2013 10:25PM UTC by dmethvin comment:7

milestone: None1.11/2.1