Hixie just made this change. We should make it ASAP and ram it into 1.9.1, since sites will have to be adjusted for it. The reason for this change is that it's completely natural to write "if (v.canPlayType(...))" or "if (!v.canPlayType(...))". And thanks to JS string->bool conversion, this happily always passes (or always fails) for all possible return values. This issue was brought up on the whatwg list ages ago, but Hixie forgot to change the spec. By returning "" instead of "no", simple uses of canPlayType will treat "no" as false and basically do what the author expects.
Created attachment 387822 [details] [diff] [review] fix
Attachment #387822 - Flags: review?(chris.double)
10 years ago
Yeah, let's block on this... needs review soon though.
Flags: blocking126.96.36.199? → blocking188.8.131.52+
Whiteboard: [needs r=cdouble]
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Comment on attachment 387822 [details] [diff] [review] fix Has to wait for 184.108.40.206
Attachment #387822 - Flags: approval220.127.116.11?
blocking1.9.1: --- → .2+
Flags: blocking18.104.22.168+ → blocking22.214.171.124-
Comment on attachment 387822 [details] [diff] [review] fix a=beltzner, please land on mozilla-1.9.1
Attachment #387822 - Flags: approval126.96.36.199? → approval188.8.131.52+
10 years ago
status1.9.1: --- → .2-fixed
Verified on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:184.108.40.206) Gecko/20090729 Firefox/3.5.2. Patch has testcases
Mass change: adding fixed1.9.2 keyword (This bug was identified as a mozilla1.9.2 blocker which was fixed before the mozilla-1.9.2 repository was branched (August 13th, 2009) as per this query: http://is.gd/2ydcb - if this bug is not actually fixed on mozilla1.9.2, please remove the keyword. Apologies for the bugspam)
status1.9.2: --- → beta1-fixed
You need to log in before you can comment on or make changes to this bug.