Bug 125286

Summary: Make HTMLOutputElement.htmlFor settable
Product: WebKit Reporter: Ryosuke Niwa <rniwa>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, ap, benjamin, bfulgham, cdumez, darin, kling, koivisto, syoichi, webkit-bug-importer
Priority: P2 Keywords: BlinkMergeCandidate, InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

Ryosuke Niwa
Reported 2013-12-04 23:41:32 PST
Consider merging https://chromium.googlesource.com/chromium/blink/+/df9b12788c040a6b2d38fd42fca56858736ec5d0 Make HTMLOutputElement.htmlFor settable as per the specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-output-element Calling HTMLOutputElement.htmlFor="foo" should be equivalent to HTMLOutputElement.value.htmlFor="foo". This behavior is consistent with Firefox 23.
Attachments
Ahmad Saleem
Comment 1 2022-08-09 16:54:53 PDT
Within Chrome Commit and Test Cases, there was a link to following: Link - https://simon.html5.org/test/html/dom/reflecting/DOMTokenList/ I test following: > Setting - https://simon.html5.org/test/html/dom/reflecting/DOMTokenList/setting/001.htm All browsers (Safari 15.6, Chrome Canary 106 and Firefox Nightly 105) fail this test. ____ > Getting - All test also show same result, where Safari fail the test, all other browsers also failed the test. _____ rniwa@webkit.org - Is something needed here? Thanks!
Ryosuke Niwa
Comment 2 2022-08-09 23:40:43 PDT
Radar WebKit Bug Importer
Comment 3 2022-08-09 23:41:17 PDT
Note You need to log in before you can comment on or make changes to this bug.