Bug 160998

Summary: Attr.prefix / Element.prefix attribute should be readonly
Product: WebKit Reporter: Chris Dumez <cdumez>
Component: DOMAssignee: Chris Dumez <cdumez>
Status: RESOLVED FIXED    
Severity: Normal CC: cdumez, cmarcelo, commit-queue, darin, dbates, esprehn+autocc, kangil.han, kondapallykalyan, rniwa, sam
Priority: P2 Keywords: WebExposed
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Chris Dumez
Reported 2016-08-19 10:03:11 PDT
Attr.prefix / Element.prefix attribute should be readonly: - https://dom.spec.whatwg.org/#element - https://dom.spec.whatwg.org/#attr Firefox and Chrome agree with the specification.
Attachments
Patch (18.78 KB, patch)
2016-08-19 10:39 PDT, Chris Dumez 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Chris Dumez
Comment 1 2016-08-19 10:39:22 PDT
Created attachment 286458 [details] Patch
Daniel Bates
Comment 2 2016-08-19 11:46:30 PDT
Comment on attachment 286458 [details] Patch I take it there is little compatibility risk with XHTML documents. Out of curiosity, do we know the motivation for this change of behavior?
Chris Dumez
Comment 3 2016-08-19 11:55:59 PDT
(In reply to comment #2) > Comment on attachment 286458 [details] > Patch > > I take it there is little compatibility risk with XHTML documents. Out of > curiosity, do we know the motivation for this change of behavior? Hopefully, not a big compatibility risk given that: - Firefox made this change in Firefox 5 (~5 years ago) - Chrome made this change in Mid-2014 - IE also does not have a setter - We do not throw when trying to set an attribute that is readonly, it is merely ignored. I could not find the motivation for this change via Googling.
WebKit Commit Bot
Comment 4 2016-08-19 12:45:42 PDT
Comment on attachment 286458 [details] Patch Clearing flags on attachment: 286458 Committed r204648: <http://trac.webkit.org/changeset/204648>
WebKit Commit Bot
Comment 5 2016-08-19 12:45:47 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.