Closed
Bug 1128177
Opened 9 years ago
Closed 9 years ago
Dialog to clear data when exiting Firefox needs more space between two columns (in-content preferences)
Categories
(Firefox :: Settings UI, defect, P1)
Firefox
Settings UI
Tracking
()
Tracking | Status | |
---|---|---|
firefox38 | --- | fixed |
People
(Reporter: flod, Assigned: jaws)
References
Details
(Whiteboard: [strings])
Attachments
(3 files)
This screenshot is taken on a localized build (Italian), there's no gutter between the columns. Not sure if it's evident in English as well, given that's usually shorter.
Comment 1•9 years ago
|
||
The width of the first column depends on column.width2 in mozilla/browser/locales/en-US/chrome/browser/sanitize.dtd. This could be increased but needs a check if it also works in normal prefs.
Reporter | ||
Comment 2•9 years ago
|
||
Then we have another issue: this is a screenshot of the window with dialog 40em, column 20em (the text is slightly different because I wanted to make sure I wasn't hitting cached elements). It's completely asymmetrical. To have something better I need to use 25em for the column, which also means I can't have the same value for old/in-content prefs. http://hg.mozilla.org/mozilla-central/file/default/browser/locales/en-US/chrome/browser/sanitize.dtd#l57
Reporter | ||
Updated•9 years ago
|
Summary: [OS X] Dialog to clear data when exiting Firefox needs more space between two columns → [OS X] Dialog to clear data when exiting Firefox needs more space between two columns (in-content preferences)
Assignee | ||
Updated•9 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Summary: [OS X] Dialog to clear data when exiting Firefox needs more space between two columns (in-content preferences) → Dialog to clear data when exiting Firefox needs more space between two columns (in-content preferences)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jaws
Status: NEW → ASSIGNED
Points: --- → 2
Priority: -- → P1
Whiteboard: [strings]
Assignee | ||
Comment 3•9 years ago
|
||
What do you think about this? I didn't tweak the values for en-US yet, but if you're good with this approach then I can find what works before checking this in.
Attachment #8559583 -
Flags: review?(gijskruitbosch+bugs)
Comment 4•9 years ago
|
||
Comment on attachment 8559583 [details] [diff] [review] Patch Review of attachment 8559583 [details] [diff] [review]: ----------------------------------------------------------------- Ugh. I hate XUL layout sometimes. But yes, this would work.
Attachment #8559583 -
Flags: review?(gijskruitbosch+bugs) → review+
Assignee | ||
Comment 5•9 years ago
|
||
Landed with an adjusted column width for the in-content preferences, and tweaked the related localization note. https://hg.mozilla.org/integration/fx-team/rev/f15ed7846547
Iteration: --- → 38.2 - 9 Feb
Flags: qe-verify-
Flags: in-testsuite-
Flags: firefox-backlog+
Comment 6•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f15ed7846547
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox38:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 38
Comment 7•9 years ago
|
||
What version are incontent preferences targeted at? I'm asking because after this, with incontent preferences disabled width of the clear recent history dialog and clear data when exiting Firefox settings dialog share the value of dialog.width2 entity but do not share styling…
Comment 8•9 years ago
|
||
(In reply to Stefan Plewako [:stef] from comment #7) > What version are incontent preferences targeted at? 38. > I'm asking because after this, with incontent preferences disabled width of > the clear recent history dialog and clear data when exiting Firefox settings > dialog share the value of dialog.width2 entity but do not share styling… Please file a separate bug. Also (and please answer this in that new, separate bug) - wasn't this the case before this fix? Doesn't seem like a regression to me...
Comment 9•9 years ago
|
||
Right, the issue predates this and there is already bug for it… https://bugzilla.mozilla.org/show_bug.cgi?id=494210
You need to log in
before you can comment on or make changes to this bug.
Description
•