https://code.google.com/p/chromium/source/search?q=file%3Anode%5C.idl+attributes&origq=file%3Anode%5C.idl+attributes&btnG=Search+Trunk
Also, hasAttributes is in the wrong idl file. The following should all be moved to Element.idl attributes hasAttributes
Created attachment 189599 [details] Patch
Comment on attachment 189599 [details] Patch Are we worried about the compatibility impact of this change?
Comment on attachment 189599 [details] Patch Attachment 189599 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/16695354 New failing tests: fast/dom/Node/initial-values.html
(In reply to comment #3) > (From update of attachment 189599 [details]) > Are we worried about the compatibility impact of this change? Not really. attributes returned null on non Elements before and now it will return undefined. This part I'm completely confident that it is safe. It is possible that someone has code out there that calls hasAttributes() on an Attr, Text, DocumentFragment or Document but it unlikely and wrong. I could definitely split this into two patches just to make things easier to rollback in case of unforeseen issues.
Created attachment 189610 [details] Patch
Comment on attachment 189610 [details] Patch Ok.
Comment on attachment 189610 [details] Patch Clearing flags on attachment: 189610 Committed r143663: <http://trac.webkit.org/changeset/143663>
All reviewed patches have been landed. Closing bug.