- From: <bugzilla@jessica.w3.org>
- Date: Wed, 26 Nov 2014 19:22:39 +0000
- To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27384 --- Comment #23 from Boris Zbarsky <bzbarsky@mit.edu> --- The only cases where that causes a problem is when the missing case is treated different from a "falsey" case or from explicit "undefined". We found two instances of that in specs, leading to <https://www.w3.org/Bugs/Public/show_bug.cgi?id=25686> and <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23565>, which both resulted in spec changes (the former to explicitly treat undefined and missing differently, the latter to change the missing behavior to be the falsey behavior. There was also an issue in window.open() for the feature string; it used to become "undefined" and now becomes "". The behavior of both is not specified, so it's hard to tell what the compat behavior is; it depends on what the UA does with those two values. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 26 November 2014 19:22:40 UTC