View source in tab formatting options aren't very discoverable

NEW
Unassigned

Status

()

Toolkit
View Source
2 years ago
2 years ago

People

(Reporter: bz, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

[Tracking Requested - why for this release]: Serious view-source usability regression

A normal view-source window has separate options for toggling wrapping of long lines and syntax highlighting.  view-source in a tab seems to have lost those options.

Maybe this is some of the stuff Paul though was unimportant in bug 1067325 comment 1?  I assure you, it's important for me....
These formatting options are accessible via the context menu in a view source tab.  Does that work for your use case?
Flags: needinfo?(bzbarsky)
Hmm.  I can make that work, I guess.  Not terribly discoverable, but now that I know it's there...
Flags: needinfo?(bzbarsky)
(In reply to Not doing reviews right now from comment #2)
> Hmm.  I can make that work, I guess.  Not terribly discoverable, but now
> that I know it's there...

Right, I agree it's not as easy to find as it is in window mode.

I'll morph this into making them easier to find.
No longer blocks: 1067325
status-firefox41: affected → ---
tracking-firefox41: ? → ---
Keywords: regression
Summary: View source in tab doesn't provide the formatting options normal view-source does → View source in tab formatting options aren't very discoverable
We should add a horizontal toolbar at the top of the View Source page that includes the options found in the context menu.

This can also be used to get rid of the "Go to line" modal dialog by replacing that with a textbox in the toolbar "Go to line: [       ]"
Created attachment 8723660 [details] [diff] [review]
Really hacky proof-of-concept

This patch would likely need to be rewritten so that we can reuse contextMenuItems so it would work for the toolbar as well as the context menu.

I don't have time to work on this bug, but maybe someone else wants to look at what I have and put together a better patch.
You need to log in before you can comment on or make changes to this bug.