Closed
Bug 1350419
Opened 7 years ago
Closed 7 years ago
console.assert "condition" argument should default to false
Categories
(DevTools :: Console, enhancement, P2)
DevTools
Console
Tracking
(firefox55 affected)
RESOLVED
DUPLICATE
of bug 1357473
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: tromey, Unassigned)
Details
(Keywords: good-first-bug)
According to https://console.spec.whatwg.org/#console-namespace, console.assert's "condition" argument should default to "false". For us, it is currently required. I think this is just a matter of changing the webidl and writing a test case. https://dxr.mozilla.org/mozilla-central/rev/e03e0c60462c775c7558a1dc9d5cf2076c3cd1f9/dom/webidl/Console.webidl#32
Comment 1•7 years ago
|
||
(In reply to Tom Tromey :tromey from comment #0) > According to https://console.spec.whatwg.org/#console-namespace, > console.assert's "condition" argument should default to "false". > For us, it is currently required. > > I think this is just a matter of changing the webidl and writing a test case. > https://dxr.mozilla.org/mozilla-central/rev/ > e03e0c60462c775c7558a1dc9d5cf2076c3cd1f9/dom/webidl/Console.webidl#32 I can help with that, but I have no idea how to write the test... Wouldn't removing "false" from [1] do it for the test part? If not I need some directions... [1]: https://dxr.mozilla.org/mozilla-central/source/dom/tests/browser/browser_ConsoleAPITests.js#230 Thanks!
Reporter | ||
Comment 2•7 years ago
|
||
(In reply to Federico Padua [:fedepad] from comment #1) > Wouldn't removing "false" from [1] do it for the test part? I think adding a new test there, that just calls "console.assert()", would be good enough.
Updated•7 years ago
|
Priority: -- → P2
Reporter | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•