Closed
Bug 862286
Opened 12 years ago
Closed 12 years ago
GCLI panel too narrow for meaningful output
Categories
(DevTools Graveyard :: Graphic Commandline and Toolbar, defect)
DevTools Graveyard
Graphic Commandline and Toolbar
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 23
People
(Reporter: miker, Assigned: miker)
References
Details
Attachments
(3 files, 1 obsolete file)
29.07 KB,
image/png
|
Details | |
97.14 KB,
image/png
|
Details | |
4.16 KB,
patch
|
Details | Diff | Splinter Review |
There are three problems:
1. Wide output is cropped when it could be far wider.
2. Text without a container displayed in a narrow popup so text must be scrolled e.g. bulleted lists.
3. Output is transient so users have to run commands multiple times in order to work through the results.
Items 1 and 2 are illustrated in the attached images.
Assignee | ||
Comment 1•12 years ago
|
||
Assignee | ||
Comment 2•12 years ago
|
||
For item 3 imagine working through the attachment in the previous comment and having to run the command again every time the issue has been addressed.
Assignee | ||
Comment 3•12 years ago
|
||
I don't see any way of solving this without moving GCLI into the toolbox.
Comment 4•12 years ago
|
||
(In reply to Michael Ratcliffe [:miker] [:mratcliffe] from comment #3)
> I don't see any way of solving this without moving GCLI into the toolbox.
Would that mean the output being shown inside the toolbox?
Assignee | ||
Comment 5•12 years ago
|
||
(In reply to Victor Porof [:vp] from comment #4)
> (In reply to Michael Ratcliffe [:miker] [:mratcliffe] from comment #3)
> > I don't see any way of solving this without moving GCLI into the toolbox.
>
> Would that mean the output being shown inside the toolbox?
It is something we have been planning for a while. Something like http://mozilla.github.io/gcli/ but the output would be in the toolbox.
Apart from it fixing the panels issue it is way more discoverable than it currently is.
Comment 6•12 years ago
|
||
We should have the max-width of the output panel to be the same as the width of the command line. Wouldn't that solve this problem?
Assignee | ||
Comment 7•12 years ago
|
||
I can see a few issues with that approach:
- It would allow the contents to be wider but would still clip the contents if they were wide enough.
- The tall, narrow output in comment 1 is nowhere near the current max-width so it would make no difference there.
- The transient nature of the output would still be an issue.
Maybe it is a better solution to what we currently have though.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → mratcliffe
Status: NEW → ASSIGNED
Assignee | ||
Comment 8•12 years ago
|
||
We now size the panel to the width of the longest line or the width of the browser, tweaking for each OS due to differences in panel implementations (no real choices there).
I am unable to get a build working on Windows so it would be great if somebody could give this a go and tweak the WINNT panel adjustment if necessary.
Attachment #747874 -
Flags: review?(jwalker)
Comment 9•12 years ago
|
||
Comment on attachment 747874 [details] [diff] [review]
Patch
Review of attachment 747874 [details] [diff] [review]:
-----------------------------------------------------------------
Nice one.
::: browser/devtools/shared/DeveloperToolbar.jsm
@@ +843,2 @@
>
> + // Adjust max width according to OS.
Could you add:
// We'd like to put this in CSS but we can't do:
// body { width: calc(min(-5px, max-content)); }
// #_panel { max-width: -5px; }
(And can you check that I'm understanding this properly? :)
@@ +855,5 @@
> + }
> +
> + this.document.body.style.width = "-moz-max-content";
> + let frameWidth = parseInt(this._frame.contentWindow
> + .getComputedStyle(this.document.body).width, 10);
Readability nit, would this be easier to follow?:
let style = this._frame.contentWindow.getComputedStyle(this.document.body)
let frameWidth = parseInt(style.width, 10);
Attachment #747874 -
Flags: review?(jwalker) → review+
Assignee | ||
Comment 10•12 years ago
|
||
(In reply to Joe Walker [:jwalker] from comment #9)
> Comment on attachment 747874 [details] [diff] [review]
> Patch
>
> Review of attachment 747874 [details] [diff] [review]:
> -----------------------------------------------------------------
>
> Nice one.
>
> ::: browser/devtools/shared/DeveloperToolbar.jsm
> @@ +843,2 @@
> >
> > + // Adjust max width according to OS.
>
> Could you add:
> // We'd like to put this in CSS but we can't do:
> // body { width: calc(min(-5px, max-content)); }
> // #_panel { max-width: -5px; }
>
> (And can you check that I'm understanding this properly? :)
>
Seems like you understand just fine.
> @@ +855,5 @@
> > + }
> > +
> > + this.document.body.style.width = "-moz-max-content";
> > + let frameWidth = parseInt(this._frame.contentWindow
> > + .getComputedStyle(this.document.body).width, 10);
>
> Readability nit, would this be easier to follow?:
>
> let style = this._frame.contentWindow.getComputedStyle(this.document.body)
> let frameWidth = parseInt(style.width, 10);
Done.
Attachment #747874 -
Attachment is obsolete: true
Assignee | ||
Updated•12 years ago
|
Whiteboard: [land-in-fx-team]
Assignee | ||
Comment 11•12 years ago
|
||
Whiteboard: [land-in-fx-team] → [fixed-in-fx-team]
Comment 12•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 23
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
•