Closed
Bug 180156
Opened 22 years ago
Closed 22 years ago
bookmark overflow chevron can overlap bookmark name text
Categories
(Firefox :: Toolbars and Customization, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: david, Assigned: hyatt)
Details
Attachments
(3 files, 5 obsolete files)
14.86 KB,
image/png
|
Details | |
1.29 KB,
patch
|
Details | Diff | Splinter Review | |
1.42 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021112 Phoenix/0.4
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021112 Phoenix/0.4
If you resize the window to the 'correct' width, the bookmark overflow chevron
can overlap the bookmark item to the left of it.
Reproducible: Always
Steps to Reproduce:
1. Horizontally resize the window so the chevron appears.
2. Continue to resize the window until the chevron overlaps the bookmark to the
left of the chevron.
Actual Results:
The chevron overlaps the bookmark.
More specifically, the calculation which determines whether to put a bookmark
item into the overflow menu doesn't take the chevron button's width into account.
Expected Results:
The chevron should not overlap the bookmark.
The calculation to determine if a bookmark item overflows should take the
chevron's width into account, if the chevron is being displayed.
Comment 3•22 years ago
|
||
Another Bookmarks toolbar chevron problem :)
Possibly related to;
bug 177266
bug 177507
Thanks for the screenshot and the patch.
-->Confirming, marking as new, OS to all.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
Comment 4•22 years ago
|
||
Comment on attachment 106246 [details] [diff] [review]
possible fix
dave, can you look at this patch and see if it's useful? thanks.
Attachment #106246 -
Flags: review?(hyatt)
Attachment #106246 -
Attachment is obsolete: true
Attachment #117862 -
Flags: review?(chanial)
Comment 7•22 years ago
|
||
djk: thx for the patch, I'll look at it as soon as I have time.
Currently... I haven't... :(
moved chevronWidth calculation out of the loop; no need to
uncollapse/recollapse the chevron, either.
(compared to previous patch).
Attachment #117862 -
Attachment is obsolete: true
Attachment #118006 -
Flags: review?(chanial)
Attachment #106246 -
Flags: review?(hyatt)
Attachment #117862 -
Flags: review?(chanial)
The previous patch assumed that the chevron would always be uncollapsed when
the code to read its width was reached; that's not always the case.
This new patch gets the width, even if the chevron is collapsed at the time.
Attachment #118006 -
Attachment is obsolete: true
Attachment #118289 -
Flags: review?(chanial)
Attachment #118006 -
Flags: review?(chanial)
Comment 10•22 years ago
|
||
Comment on attachment 118289 [details] [diff] [review]
hello, edge case (tweaked patch for an edge case I found)
>+ var chevronWidth = 0;
>+ if (chevron.collapsed) {
>+ chevron.collapsed = false;
>+ chevronWidth = chevron.boxObject.width;
>+ chevron.collapsed = true;
>+ } else {
>+ chevronWidth = chevron.boxObject.width;
>+ }
> chevron.collapsed = true;
Why not just:
chevron.collapsed = false;
var chevronWidth = chevron.width;
chevron.collapsed = true;
?
Comment 11•22 years ago
|
||
Oops I meant chevron.boxObject.width of course :-) /me needs sleep
Reporter | ||
Comment 12•22 years ago
|
||
neil:
Duh, of course! I was so concerned with fixing the edge case I found, I missed
that obvious flaw.
I guess I was still thinking of my first patch on this bug, where the .collapsed
state needed to be restored after getting the width.
Reporter | ||
Comment 13•22 years ago
|
||
Attachment #118289 -
Attachment is obsolete: true
Attachment #119066 -
Flags: review?(chanial)
Attachment #118289 -
Flags: review?(chanial)
Comment 14•22 years ago
|
||
This is still there in the FB 0.6.1rc1 - why is it that I keep seeing patches by
djk which aren't getting checked in?
Anyway, this problem still exists.
Reporter | ||
Comment 16•22 years ago
|
||
> why is it that I keep seeing patches by
> djk which aren't getting checked in?
Hopefully because nobody has looked at them; not because they suck. ;-)
I've seen one of my patches get checked in recently, so it's probably just a
matter of time before we hear more about the others.
David
Comment 17•22 years ago
|
||
shouldnt this bug be assigned to jdk then?
Comment 18•22 years ago
|
||
This is djk's patch in the de-bitrotted state.
djk, thanks for the patch. I hope you don't mind my doing.
Attachment #119066 -
Attachment is obsolete: true
Updated•22 years ago
|
Attachment #119066 -
Flags: review?(chanial)
Comment 19•22 years ago
|
||
Comment on attachment 128692 [details] [diff] [review]
djk's patch with bitrot removed
Noririty, can you please review?
Attachment #128692 -
Flags: review?(noririty)
Reporter | ||
Comment 20•22 years ago
|
||
> This is djk's patch in the de-bitrotted state.
> djk, thanks for the patch. I hope you don't mind my doing.
Not at all! It's nice to see FB development picking up again.
David
Comment 21•22 years ago
|
||
Comment on attachment 128692 [details] [diff] [review]
djk's patch with bitrot removed
>+ if (i == buttons.childNodes.length-1) {
>+ chevronWidth = 0; // last ptf item...
>+ }
Two style nits:
1. Spaces before and after the - operator.
2. Style in this file is to have no {}s for a single statement.
Comment 22•22 years ago
|
||
here's a patch that uses a different approach. What it does it to check if the
previous button will still fit if the chevron is displayed.
Comment 23•22 years ago
|
||
Comment on attachment 128692 [details] [diff] [review]
djk's patch with bitrot removed
I like this way. checked in.
Attachment #128692 -
Flags: review?(noririty)
Updated•18 years ago
|
QA Contact: bugzilla → toolbars
You need to log in
before you can comment on or make changes to this bug.
Description
•