[Webkit-unassigned] [Bug 83298] getMatchedCSSRules() should return null when the second argument is an unrecognized pseudo-element name

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Apr 24 12:38:25 PDT 2012


--- Comment #5 from Kentaro Hara <haraken at chromium.org>  2012-04-24 12:38:23 PST ---
(From update of attachment 138598)
View in context: https://bugs.webkit.org/attachment.cgi?id=138598&action=review

> LayoutTests/fast/dom/Window/getMatchedCSSRules-with-invalid-pseudo-elements.html:18
> +shouldBe("getMatchedCSSRules(document.querySelector('p'), 'before')", "null")
> +shouldBe("getMatchedCSSRules(document.querySelector('p'), 'foo')", "null")

Please add test cases for null and undefined in the second argument.

> Source/WebCore/page/DOMWindow.idl:156
> +                                       in [TreatNullAs=NullString, TreatUndefinedAs=NullString,Optional=DefaultIsUndefined] DOMString pseudoElement);

What is the expected behavior for null or undefined in the second argument? Look at here: https://trac.webkit.org/wiki/WebKitIDL#TreatNullAs

We do not specify [TreatNullAs=NullString, TreatUndefinedAs=NullString], unless the spec requires it.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list