- From: <bugzilla@jessica.w3.org>
- Date: Wed, 26 Nov 2014 16:07:19 +0000
- To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27384 --- Comment #18 from Philip Jägenstedt <philipj@opera.com> --- You're right, until WebIDL's overload resolution algorithm is implemented correctly addRule(foo, bar, undefined) would behave like addRule(foo, bar, 0). In Blink, "Treat undefined as missing for optional arguments with defaults" has landed: https://code.google.com/p/chromium/issues/detail?id=335871 That isn't relevant to addRule case, but that's the bug to follow if you're interested. I'm not worried about compat issues around insertRule(rule, undefined), and it seems like Blink would be at greater risk, since inserting at 0 can throw an exception. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 26 November 2014 16:07:20 UTC