Make about: pages discoverable, put about:about in the help menu

NEW
Unassigned

Status

--
enhancement
11 years ago
8 years ago

People

(Reporter: nelson, Unassigned)

Tracking

Bug Flags:
blocking-seamonkey2.0 -
blocking-seamonkey2.0a1 -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [SmBugEvent])

Now, it's a Great "easter egg" feature.  
You have to know it exists to be able to use it.
Let's get it out in the open.
Flags: blocking-seamonkey2.0a1?
(In reply to comment #0)
> Now, it's a Great "easter egg" feature.  
> You have to know it exists to be able to use it.
> Let's get it out in the open.
> 
This isn't a SM 2.0a1 blocker - it is not something that is broken or can't live without.

IMHO its a debug/reporting facility only. It would probably be better to put it on the Debug/QA menu that is supplied by the DebugQA extension.

It is already on about:about (although I know not everyone knows about that) but additionally, if we choose not to activate crashreporter on the majority of builds then for those builds about:crashes will be useless.
Flags: blocking-seamonkey2.0a1? → blocking-seamonkey2.0a1-
about:about?  An easter egg of easter eggs?
OK, make about:about discoverable!  
Flags: blocking-seamonkey2?
Summary: Make about:crashes discoverable, put it in the help menu → Make about: pages discoverable, put about:about in the help menu
(In reply to comment #1)
> [...] if we choose not to activate crashreporter on the majority of
> builds then for those builds about:crashes will be useless.

Note that unlike Talkback, Breakpad is not (or not yet) built as an extension; this means no easy way for users to enable (or disable) it at will. IMHO this also implies that, as long as only Windows builds are distributed as installers, other builds will have Breakpad always installed and will benefit from a "discoverable" about:crashes menu.
(In reply to comment #3)
> (In reply to comment #1)
> > [...] if we choose not to activate crashreporter on the majority of
> > builds then for those builds about:crashes will be useless.
> 
> Note that unlike Talkback, Breakpad is not (or not yet) built as an extension;
> this means no easy way for users to enable (or disable) it at will. IMHO this
> also implies that, as long as only Windows builds are distributed as
> installers, other builds will have Breakpad always installed and will benefit
> from a "discoverable" about:crashes menu.

Even though breakpad is not an extension it is still configurable in some manner (I don't understand exactly after a brief read) to provide less reports, see bug 424960.

Comment 5

11 years ago
Not blocking anything on such a doubtful "feature".
Flags: blocking-seamonkey2? → blocking-seamonkey2-
So the grand tradition of SM features being "knowledge locked" is codified.
Moving to UI Design component
Assignee: general → nobody
Component: General → UI Design
OS: Windows XP → All
QA Contact: general → ui-design
Hardware: x86 → All
Whiteboard: [SmBugEvent]
You need to log in before you can comment on or make changes to this bug.