Closed
Bug 406552
Opened 17 years ago
Closed 16 years ago
Sidebar in Help Viewer is not collapsible
Categories
(SeaMonkey :: Help Documentation, defect)
SeaMonkey
Help Documentation
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.0a3
People
(Reporter: hand_of_fate2000, Assigned: InvisibleSmiley)
Details
(Keywords: regression)
Attachments
(1 file, 3 obsolete files)
2.78 KB,
patch
|
neil
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b2pre) Gecko/2007113002 SeaMonkey/2.0a1pre Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b2pre) Gecko/2007113002 SeaMonkey/2.0a1pre In the latest trunk, the sidebar in the help viewer has no collapse button. Since this was present in previous releases, this is a regression. Reproducible: Always
Comment 1•16 years ago
|
||
It was present in 1.1.x, is that it?
Updated•16 years ago
|
Assignee: neil → nobody
QA Contact: danielwang → help
Assignee | ||
Comment 2•16 years ago
|
||
(In reply to comment #1) > It was present in 1.1.x, is that it? Yes. Confirming for Windows, setting Platform to All.
OS: Linux → All
Hardware: x86 → All
Comment 3•16 years ago
|
||
This is because we use the toolkit help viewer and toolkit doesn't use grippies.
Assignee | ||
Comment 4•16 years ago
|
||
(In reply to comment #3) > This is because we use the toolkit help viewer and toolkit doesn't use > grippies. Thought so; setting dependency assuming the Toolkit version won't support it.
Depends on: 424130
Comment 5•16 years ago
|
||
Now that the toolkit help viewer is NPOTDB I think that we can get a rs+ if we want to add grippies to this. Want to come up with a patch Jens? Should be just a SMOP.
Comment 6•16 years ago
|
||
Adding grippies means that this bug should probably be moved to toolkit: help viewer. One might also want to consider the current look of the grippies (very outdated).
Assignee | ||
Comment 7•16 years ago
|
||
(In reply to comment #6) > Adding grippies means that this bug should probably be moved to toolkit: help > viewer. Yes. Is there a way to do that in one step? Bugzilla doesn't let me choose Help Viewer when I select Toolkit. :-/ > One might also want to consider the current look of the grippies (very > outdated). Feel free to file a bug (if there is none yet). :-) Patch coming up.
Assignee: nobody → jh
Status: NEW → ASSIGNED
Assignee | ||
Comment 8•16 years ago
|
||
The attached patch unconditionally adds a grippy to the Toolkit Help Viewer. Since help.xul is already preprocessed I'm wondering whether we should take the conditional approach. Questions from my side: 1. what would be the correct symbol (MOZ_SUITE?) and is it defined in this context? 2. who's an appropriate reviewer when this bug is moved to Toolkit:Help Viewer? Not requesting review yet for the above reasons.
Assignee | ||
Comment 9•16 years ago
|
||
Just saw that I forgot to indent. No review request, no problem, right? ;-)
Comment 10•16 years ago
|
||
Whatever you do, I'm quite convinced that this is not suitable for other apps than seamonkey, so a conditional approach is probably what you want.
Assignee | ||
Updated•16 years ago
|
Component: Help → Help Viewer
Product: SeaMonkey → Toolkit
QA Contact: help → help.viewer
Assignee | ||
Comment 11•16 years ago
|
||
This time even with indentation. :-)
Attachment #356323 -
Attachment is obsolete: true
Attachment #356412 -
Flags: review?(neil)
Comment 12•16 years ago
|
||
Comment on attachment 356412 [details] [diff] [review] Conditional approach Actually, now when I think of it, I'm not sure we want the left pane to be hidden completely because we show search results there... The current behavior seems odd to me (after dragging half-way it suddenly becomes hidden).
Assignee | ||
Comment 13•16 years ago
|
||
(In reply to comment #12) > (From update of attachment 356412 [details] [diff] [review]) > Actually, now when I think of it, I'm not sure we want the left pane to be > hidden completely because we show search results there... On the other hand, we're not talking about the default here, only the *option* to collapse the left pane to give more room for the contents on the right. I think that's a case of giving the user choice. > The current behavior > seems odd to me (after dragging half-way it suddenly becomes hidden). Agreed, but that can (and probably should) be changed. For example the browser sidebar (sidebarOverlay.xul) collapses at a much smaller size and I think that's because of min-width defined in navigator.css, #sidebar-splitter (cf. <https://developer.mozilla.org/en/XUL_Tutorial/Splitters>, Splitter example, text below the last image). There was also the question whether this bug could be fixed through a suite overlay. There's a line in suite/common/jar.mn that points to suite/common/helpOverlay.xul so I think SM already is overlaying help.xul. I don't know much about overlaying, though.
Comment 14•16 years ago
|
||
(In reply to comment #13) > (In reply to comment #12) > > (From update of attachment 356412 [details] [diff] [review]) > > Actually, now when I think of it, I'm not sure we want the left pane to be > > hidden completely because we show search results there... > On the other hand, we're not talking about the default here, only the *option* > to collapse the left pane to give more room for the contents on the right. I > think that's a case of giving the user choice. You would need to uncollapse the left pane when the user did a search. > > The current behavior > > seems odd to me (after dragging half-way it suddenly becomes hidden). > Agreed, but that can (and probably should) be changed. For example the browser > sidebar (sidebarOverlay.xul) collapses at a much smaller size and I think > that's because of min-width defined in navigator.css, #sidebar-splitter Yes, that would explain it. > There was also the question whether this bug could be fixed through a suite > overlay. There's a line in suite/common/jar.mn that points to > suite/common/helpOverlay.xul so I think SM already is overlaying help.xul. I > don't know much about overlaying, though. As I recall we do this to handle external links out of help properly. What this means is that we don't need to modify help.xul to add to it, as long as the element in question has an id. (This is how we add the help-external browser.)
Updated•16 years ago
|
Attachment #356412 -
Flags: review?(neil) → review-
Comment 15•16 years ago
|
||
Comment on attachment 356412 [details] [diff] [review] Conditional approach As per comment #14.
Assignee | ||
Updated•16 years ago
|
Component: Help Viewer → Help
Product: Toolkit → SeaMonkey
QA Contact: help.viewer → help
Assignee | ||
Comment 16•16 years ago
|
||
New approach with review comments addressed: - uses suite overlay - shows sidebar when using search - changes min-width to 30px. Template rule is #sidebar-box in sidebarOverlay.css, not #sidebar-splitter in navigator.css as stated previously: it's always the collapsible frame that needs to be targeted. Modern's helpOverlay.xul is empty, that's why a different file is used there (the matching Classic file is part of *stripe)
Attachment #356412 -
Attachment is obsolete: true
Attachment #356788 -
Flags: review?(neil)
Comment 17•16 years ago
|
||
Comment on attachment 356788 [details] [diff] [review] Suite overlay solution >+function showSidebar() { >+ document.getElementById("help-sidebar").collapsed = false; >+} This doesn't quite work, as the *splitter* is supposed to manage the collapsed state, and it still thinks that the sidebar is collapsed. >+ <textbox id="findText" oncommand="showSidebar(); doFind();"/> [Ideally you would add an event listener in the overlay, but then you'd have to fix the <window> too ;-) ] > /* Set the minimum sidebar width so the help contents aren't squeezed together.*/ This comment no longer makes sense; by the way I worked out why you used 30px.
Attachment #356788 -
Flags: review?(neil) → review-
Assignee | ||
Comment 18•16 years ago
|
||
(In reply to comment #17) > (From update of attachment 356788 [details] [diff] [review]) > >+function showSidebar() { > >+ document.getElementById("help-sidebar").collapsed = false; > >+} > This doesn't quite work, as the *splitter* is supposed to manage the collapsed > state, and it still thinks that the sidebar is collapsed. Right. New approach: do it like goToggleSplitter() in abCommon.js. > >+ <textbox id="findText" oncommand="showSidebar(); doFind();"/> > [Ideally you would add an event listener in the overlay, but then you'd have to > fix the <window> too ;-) ] Consistency. ;-) > > /* Set the minimum sidebar width so the help contents aren't squeezed together.*/ > This comment no longer makes sense; by the way I worked out why you used 30px. Removed the comment.
Attachment #356788 -
Attachment is obsolete: true
Attachment #357033 -
Flags: review?(neil)
Updated•16 years ago
|
Attachment #357033 -
Flags: review?(neil) → review+
Assignee | ||
Comment 19•16 years ago
|
||
Neil clarified via IRC r+ is indeed including sr+ here so please check in and close.
Keywords: checkin-needed
Comment 20•16 years ago
|
||
Comment on attachment 357033 [details] [diff] [review] Suite overlay solution v2 [Checkin: Comment 20] http://hg.mozilla.org/comm-central/rev/54b5b742341c
Attachment #357033 -
Attachment description: Suite overlay solution v2 → Suite overlay solution v2
[Checkin: Comment 20]
Updated•16 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.0a3
Comment 21•16 years ago
|
||
Verifying on Linux: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090128 SeaMonkey/2.0a3pre - Build ID: 20090128000434 Help viewer sidebar now has a functioning grippy (clicking it toggles the sidebar's open/closed state).
You need to log in
before you can comment on or make changes to this bug.
Description
•