Skip to main content

Bug Tracker

Side navigation

#10924 closed bug (invalid)

Opened November 29, 2011 04:59PM UTC

Closed December 16, 2011 07:57AM UTC

Last modified March 14, 2012 11:08AM UTC

Safari 5 Win (and others ?) prop/attr works great only with uppercase attributes

Reported by: _BenM_ Owned by: _BenM_
Priority: undecided Milestone: None
Component: unfiled Version: 1.7.1
Keywords: Cc:
Blocked by: Blocking:

With disabled and required attributes, prop/attr works fine on Firefox but on Safari 5.1, style is not updated.

I do this in CSS :

input:required:invalid, input:focus:invalid { border-color: red }
input:valid { border-color: green }

This following example doesn't update CSS in Safari :

$('#myid input').prop('required',true).removeProp('disabled');

This one does :

$('#myid input').prop('REQUIRED',true).removeProp('DISABLED');
Attachments (0)
Change History (3)

Changed November 29, 2011 05:35PM UTC by sindresorhus comment:1

owner: → _BenM_
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.

Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: Open the link and click to "Fork" (in the top menu) to get started.

Changed December 01, 2011 12:05PM UTC by anonymous comment:2

Sorry, you can close my ticket.

I don't know why it works with the second line, but with Safari, "required" attribute must be change AFTER "disabled".

So :

$('#myid input').removeProp('disabled').prop('required',true);


And, on multiple examples, Safari prefer prop('required','required') than prop('required',true).

Changed December 16, 2011 07:57AM UTC by trac-o-bot comment:3

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!