You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Shouldn't the oldValue in both of these assertions be null rather than an empty string? It doesn't seem to me that capture is getting set anywhere prior in order for the old value to be non-null.
The text was updated successfully, but these errors were encountered:
The other problem with this test is the if ('capture' in HTMLInputElement.prototype) { conditional. If this is a tentative test it should be marked as such, but it shouldn't contain optional parts.
Yes, I think it should be null instead of empty string. And also the file should be renamed to something like HTMLInputElement-capture, and the conditional-ness removed.
Honry
added a commit
to Honry/web-platform-tests
that referenced
this issue
Nov 20, 2019
I'm adding support for the
capture
attribute to Gecko and I'm a bit confused by two assertions:wpt/custom-elements/reactions/HTMLInputElement.html
Line 23 in ef6e66c
wpt/custom-elements/reactions/HTMLInputElement.html
Line 46 in ef6e66c
Shouldn't the
oldValue
in both of these assertions benull
rather than an empty string? It doesn't seem to me thatcapture
is getting set anywhere prior in order for the old value to be non-null.The text was updated successfully, but these errors were encountered: