Node.prototype.baseURI should not be nullable |
|||
Issue descriptionFor example, var xmlDoc = document.implementation.createDocument(null, "", null); xmlDoc.documentURI; // Chromium correctly returns "about:blank" xmlDoc.baseURI; // Chromium returns null. Safari and Firefox return "about:blank" Our definition in Node.idl is: readonly attribute DOMString? baseURI; But the specification says: readonly attribute USVString baseURI; This is a reason of two failures in http://w3c-test.org/dom/interfaces.html . I don't think we need intent-to-ship for this.
,
Apr 19 2017
,
Apr 19 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0462cff6ac0ddd51d88e74eb2e356061bbe792b0 commit 0462cff6ac0ddd51d88e74eb2e356061bbe792b0 Author: lpy <lpy@chromium.org> Date: Wed Apr 19 22:44:42 2017 Node.prototype.baseURI should not be nullable The definition of baseURI in Node.idl should be USVString. BUG= 711562 Review-Url: https://codereview.chromium.org/2831753002 Cr-Commit-Position: refs/heads/master@{#465791} [modify] https://crrev.com/0462cff6ac0ddd51d88e74eb2e356061bbe792b0/third_party/WebKit/LayoutTests/external/wpt/dom/interfaces-expected.txt [modify] https://crrev.com/0462cff6ac0ddd51d88e74eb2e356061bbe792b0/third_party/WebKit/Source/core/dom/Document.cpp [modify] https://crrev.com/0462cff6ac0ddd51d88e74eb2e356061bbe792b0/third_party/WebKit/Source/core/dom/Document.h [modify] https://crrev.com/0462cff6ac0ddd51d88e74eb2e356061bbe792b0/third_party/WebKit/Source/core/dom/Node.idl
,
Apr 20 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by tkent@chromium.org
, Apr 14 2017