Closed
Bug 1197394
Opened 9 years ago
Closed 9 years ago
GCLI’s number-type doesn’t accept min/max-value of 0
Categories
(DevTools Graveyard :: Graphic Commandline and Toolbar, defect)
DevTools Graveyard
Graphic Commandline and Toolbar
Tracking
(firefox43 fixed)
RESOLVED
FIXED
Firefox 43
Tracking | Status | |
---|---|---|
firefox43 | --- | fixed |
People
(Reporter: johankj, Assigned: johankj)
References
Details
Attachments
(1 file, 1 obsolete file)
1.20 KB,
patch
|
jwalker
:
review+
|
Details | Diff | Splinter Review |
GCLI’s number-type ignores min or max-values of 0 as seen in bug 970625. E.g.: > type: { name: "number", min: 0 }, won’t have any minimum value, but > type: { name: "number", min: 1 }, will have a minimum value of 1.
Assignee | ||
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
Comment on attachment 8651257 [details] [diff] [review] bug1197394_gcli_numbertype_ignores_min_max_0_value.patch Review of attachment 8651257 [details] [diff] [review]: ----------------------------------------------------------------- ::: toolkit/devtools/gcli/source/lib/gcli/types/number.js @@ +68,5 @@ > return '' + value; > }, > > getMin: function(context) { > + if (this.min != undefined) { Could you use: if (this.min != null) { instead? A test for (x != null) is true if x is null or undefined, where using (x != undefined) is only true if x is undefined, also this is the style used in the rest of GCLI code. Really surprised that this is written as it is TBH.
Attachment #8651257 -
Flags: review?(jwalker) → review+
Comment 3•9 years ago
|
||
Thanks for the patch. I'll uplift it to the GCLI repo.
Assignee | ||
Comment 4•9 years ago
|
||
Attachment #8651257 -
Attachment is obsolete: true
Attachment #8651358 -
Flags: review?(jwalker)
Comment 5•9 years ago
|
||
Comment on attachment 8651358 [details] [diff] [review] bug1197394_gcli_numbertype_ignores_min_max_0_value.patch Review of attachment 8651358 [details] [diff] [review]: ----------------------------------------------------------------- Thanks!
Attachment #8651358 -
Flags: review?(jwalker) → review+
Blocks: 970625
Joe, are you planning to pull this up into GCLI and then back down to Gecko? Or should this patch land in m-c right now, and you'll handle the GCLI repo separately?
Flags: needinfo?(jwalker)
Comment 7•9 years ago
|
||
Just land in m-c, I'll sort GCLI when I'm less busy.
Flags: needinfo?(jwalker)
Johan, are you able to push this to try? I typically use a commit such as: try: -b do -p linux64,macosx64,win32 -u xpcshell,mochitest-dt,mochitest-o,mochitest-e10s-devtools-chrome for most DevTools changes.
Flags: needinfo?(jj)
Assignee | ||
Comment 9•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=43d71b85dd82
Flags: needinfo?(jj)
Keywords: checkin-needed
Comment 10•9 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/821f73eb7aef
Keywords: checkin-needed
Comment 11•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/821f73eb7aef
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox43:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 43
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•6 years ago
|
Product: DevTools → DevTools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•