Closed
Bug 490655
Opened 16 years ago
Closed 16 years ago
Clear recent history dialog too wide [en-US]
Categories
(Firefox :: Private Browsing, defect)
Firefox
Private Browsing
Tracking
()
VERIFIED
FIXED
Firefox 3.6a1
People
(Reporter: adw, Assigned: adw)
References
Details
(Keywords: polish, verified1.9.1, Whiteboard: [non-l10n-impact string change])
Attachments
(2 files)
764 bytes,
patch
|
johnath
:
review+
beltzner
:
approval1.9.1-
|
Details | Diff | Splinter Review |
795 bytes,
patch
|
johnath
:
review+
beltzner
:
approval1.9.1+
|
Details | Diff | Splinter Review |
We took the tree out of the recent clear recent history dialog refresh (bug 480169) at the last minute. The dialog is a little too wide as a result.
Although the dialog's width is set via a DTD entity, string freeze was a month before the decision to yank the tree, so it may be too wide in other locales also.
Comment 1•16 years ago
|
||
This change doesn't have an l10n impact aside from being noisy on the files that localizers read. Thus, no entity change, OK with me to take for 3.5 RC1.
Whiteboard: [non-l10n-impact string change]
Updated•16 years ago
|
Assignee | ||
Comment 2•16 years ago
|
||
Not sure who's best to review this. It's basically a visual change, so asking Alex. 28em is pretty much the minimum width that fully displays the duration dropdown in all three themes.
Attachment #375064 -
Flags: review?(faaborg)
Assignee | ||
Updated•16 years ago
|
Attachment #375064 -
Flags: review?(faaborg) → review?(johnath)
Comment 3•16 years ago
|
||
Comment on attachment 375064 [details] [diff] [review]
patch
># HG changeset patch
># User Drew Willcoxon <adw@mozilla.com>
># Date 1241024879 25200
># Node ID 2da9cfcd0892125a5f9f85ecee6b35a54c697c23
># Parent 3a27bee3d7b5b4e2447a1e578ed8436ae71063d8
>Bug 490655 - Clear recent history dialog too wide [en-US]
>
>diff --git a/browser/locales/en-US/chrome/browser/sanitize.dtd b/browser/locales/en-US/chrome/browser/sanitize.dtd
>--- a/browser/locales/en-US/chrome/browser/sanitize.dtd
>+++ b/browser/locales/en-US/chrome/browser/sanitize.dtd
>@@ -58,5 +58,5 @@ that require it. -->
> mockup at bug 480169 -->
> <!ENTITY sanitizeEverythingUndoWarning "This action cannot be undone.">
>
>-<!ENTITY dialog.width "32em">
>+<!ENTITY dialog.width "28em">
> <!ENTITY column.width "14em">
If it makes axel happy, it makes me happy. Have you tested to ensure that things word wrap correctly when they need to? (I know you added flex in the other bug - do these need to land together?)
Attachment #375064 -
Flags: review?(johnath) → review+
Assignee | ||
Comment 4•16 years ago
|
||
(In reply to comment #3)
> If it makes axel happy, it makes me happy. Have you tested to ensure that
> things word wrap correctly when they need to? (I know you added flex in the
> other bug - do these need to land together?)
Things (by which I mean the warning text) don't wrap at all without the flex fix in bug 489700. Big goof on my part. However, even with the narrower dialog of this bug it's not a problem for en-US because the text is pretty short. It's probably a problem for some other locales.
Since this bug is for en-US only, the two patches can land in either order.
Keywords: checkin-needed
Comment 5•16 years ago
|
||
Comment 6•16 years ago
|
||
Based on comment 1 will this land on the 1.9.1 branch? AFAICT this doesn't have a requested 3.5 flag yet.
Assignee | ||
Updated•16 years ago
|
Attachment #375064 -
Flags: approval1.9.1?
Assignee | ||
Comment 7•16 years ago
|
||
Comment on attachment 375064 [details] [diff] [review]
patch
Requesting approval, very low risk, visual polish to CRH dialog, Axel says no l10n impact and fine with him to take in 3.5 (comment 1).
Comment 8•16 years ago
|
||
FWIW, this has caused bug 490655. Since we don't want to fix a polish problem here and cause another one there, this should happen for 1.9.1 alongside the fix to that bug.
Keywords: polish
Updated•16 years ago
|
Attachment #375064 -
Flags: approval1.9.1? → approval1.9.1+
Comment 9•16 years ago
|
||
Comment on attachment 375064 [details] [diff] [review]
patch
a191=beltzner
Comment 10•16 years ago
|
||
Comment on attachment 375064 [details] [diff] [review]
patch
Oops, missed that this caused a regression. I'll approve a roll-up
Attachment #375064 -
Flags: approval1.9.1+ → approval1.9.1-
Assignee | ||
Comment 11•16 years ago
|
||
Sorry Ehsan! I think I've been making your life harder with these privacy and CRH bugs... :\
I'm not sure what "roll-up" means. Bug 493485 is handling the regression on trunk, so given the fact this has been a-'ed, should the 1.9.1 patch go there as well?
Comment 12•16 years ago
|
||
Both patches should be combined for a 1.9.1 patch, yes.
Comment 13•16 years ago
|
||
As whimboo said - the a- here is just because we don't like approving patches that need to land with other patches - those soft dependencies tend to get lost, and then everyone is sad. If you can combine the two co-dependent changes into 1 patch, we should get it reviewed and landed post-haste.
Assignee | ||
Comment 14•16 years ago
|
||
Attachment #378436 -
Flags: review?(johnath)
Updated•16 years ago
|
Attachment #378436 -
Flags: review?(johnath) → review+
Comment 15•16 years ago
|
||
Comment on attachment 378436 [details] [diff] [review]
1.9.1 patch
Looks good to me on Mac
Comment 16•16 years ago
|
||
Comment on attachment 378436 [details] [diff] [review]
1.9.1 patch
This is a 1 line polish change for 1.9.1. Earlier comments made it look like this was tied to the patch in bug 493485, but really it isn't. The trunk landing here made things too thin and bug 493485 was filed to fix it. This 1.9.1 only patch could live over there, but \/\/ - it should land. It's just the "fixed" version of the trunk patch in this bug.
Confused now?
Attachment #378436 -
Flags: approval1.9.1?
Comment 17•16 years ago
|
||
Comment on attachment 378436 [details] [diff] [review]
1.9.1 patch
a191=beltzner
This is the first patch approval I have given due to hopeless confusion.
Attachment #378436 -
Flags: approval1.9.1? → approval1.9.1+
Updated•16 years ago
|
Keywords: checkin-needed
Comment 18•16 years ago
|
||
Keywords: checkin-needed → fixed1.9.1
Comment 19•16 years ago
|
||
I noticed these values are being shared by the ‘Clear recent history’ and the ‘Settings for clearing history’ dialog. Wouldn’t it be wise to use separate values for the latter? That dialog could use smaller values for en-US already, probably for other locales as well. For Dutch/nl for instance, we currently need to use no less than 34/17 to make the lines in ‘Clear recent history’ fit on one line, which causes the Clear recent history dialog to use even more ‘white space’ than it currently does for en-US.
Comment 20•16 years ago
|
||
(In reply to comment #19)
> no less than 34/17 to make the lines in ‘Clear recent history’ fit on one line
I meant the lines in ‘Settings for clearing history’, of course.
Assignee | ||
Comment 21•16 years ago
|
||
(In reply to comment #19)
> ‘Settings for clearing history’ dialog. Wouldn’t it be wise to use separate
> values for the latter?
Totally. Filed bug 494210.
Comment 22•16 years ago
|
||
How can this be verified?
Comment 23•16 years ago
|
||
Simply check bug 493485. This dialog is too narrow now on all platforms. But lets verify this one on trunk and 1.9.1.
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090526 Minefield/3.6a1pre ID:20090526031623
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1pre) Gecko/20090526 Shiretoko/3.5pre ID:20090526031155
Status: RESOLVED → VERIFIED
Keywords: fixed1.9.1 → verified1.9.1
You need to log in
before you can comment on or make changes to this bug.
Description
•