Ticket #9166 (closed bug: duplicate)
Prop not setting property if it had previously been removed, and Chrome inconsistency
|Reported by:||jamietre||Owned by:|
After this script runs the test field is not actually disabled (following setting "disabled" property to "true", then "false", then "true" again.) Yet the reported values in the log indicate that jQuery thinks the property is there. Inspecting the HTML shows that it does not exist in the DOM. This behavior is consistent across all browsers.
Additionally, the results returned by testing "prop" value are incorrect in Chrome.
Initially, Chrome correctly reports "false" for prop on a missing property. However, after adding then removing "disabled" Chrome reports "undefined" whereas IE and FF correctly report "false".
- Priority changed from undecided to low
- Resolution set to duplicate
- Status changed from new to closed
- Component changed from unfiled to attributes