WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
157211
Node.nodeName should not be nullable
https://bugs.webkit.org/show_bug.cgi?id=157211
Summary
Node.nodeName should not be nullable
Chris Dumez
Reported
2016-04-29 16:03:24 PDT
Node.nodeName should not be nullable as per the specification:
https://dom.spec.whatwg.org/#interface-node
Our implementation never returns null anyway. However, having it as nullable in the IDL means we use jsStringOrNull() instead of jsStringWithCache(), thus doing an unnecessary null check.
Attachments
Patch
(1.57 KB, patch)
2016-04-29 16:08 PDT
,
Chris Dumez
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Chris Dumez
Comment 1
2016-04-29 16:08:28 PDT
Created
attachment 277748
[details]
Patch
WebKit Commit Bot
Comment 2
2016-04-29 17:12:04 PDT
Comment on
attachment 277748
[details]
Patch Clearing flags on attachment: 277748 Committed
r200271
: <
http://trac.webkit.org/changeset/200271
>
WebKit Commit Bot
Comment 3
2016-04-29 17:12:10 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.
Top of Page
Format For Printing
XML
Clone This Bug