Closed
Bug 1264143
Opened 9 years ago
Closed 9 years ago
"No notification will be shown…" text is no longer aligned with the "Do not disturb me" checkbox label
Categories
(Toolkit :: Themes, defect)
Tracking
()
RESOLVED
FIXED
mozilla49
| Tracking | Status | |
|---|---|---|
| firefox47 | --- | unaffected |
| firefox48 | --- | wontfix |
| firefox49 | --- | fixed |
People
(Reporter: MattN, Assigned: jaws)
References
()
Details
(Keywords: regression)
Attachments
(2 files)
Compare 03_prefsContent at https://screenshots.mattn.ca/compare/?oldProject=mozilla-central&oldRev=d62963756d9a9d19cbbb5d8f3dd3c7cfa8fdef88&newProject=mozilla-central&newRev=e847cfcb315f511f4928b03fd47dcf57aad05e1e
I suspect this is from the specificity change in https://hg.mozilla.org/mozilla-central/rev/1af4c6693497#l2.1 which was unreviewed in bug 1263016. It seems like the change to toolkit/themes/shared/in-content/common.inc.css wasn't intended for that bug.
I think there's a non-trivial chance this will regress other in-content pages too with the specificity change.
Flags: needinfo?(jaws)
| Assignee | ||
Comment 1•9 years ago
|
||
Indeed that change was very unintentional and somehow slipped in to that patch from some work on bug 1247214 which landed on top of it. See https://hg.mozilla.org/mozilla-central/rev/4eea4fcaf495#l4.13
Flags: needinfo?(jaws)
| Assignee | ||
Comment 2•9 years ago
|
||
| Assignee | ||
Updated•9 years ago
|
Attachment #8740767 -
Flags: review?(gijskruitbosch+bugs)
Comment 3•9 years ago
|
||
Comment on attachment 8740767 [details] [diff] [review]
Patch
Review of attachment 8740767 [details] [diff] [review]:
-----------------------------------------------------------------
Why are we setting this to 0 so broadly in the first place? From bug 993369, which introduced these, seems like this was originally intended for use in menulists? Of course, by now loads of random other labels rely on this rule to be aligned properly with the subheadings. :-\
Increasing the specificity will fix the .indent case, but not any hypothetical other issues alluded to in comment #0. r=me assuming no such cases exist, probably worth doing a mozscreenshots trypush to find that out. Leaving r?MattN in case he has better ideas.
Attachment #8740767 -
Flags: review?(gijskruitbosch+bugs) → review+
| Assignee | ||
Comment 4•9 years ago
|
||
Richard, do you see a way that we could make those selectors more specific?
Flags: needinfo?(richard.marti)
Comment 5•9 years ago
|
||
Not really. What would work would be adding an id in front like #mainPrefPane .indent {} but this would make the parsing slower and #mainPrefPane would not include the dialogs (I don't know if they use .indent).
Flags: needinfo?(richard.marti)
| Reporter | ||
Comment 6•9 years ago
|
||
Comment on attachment 8740767 [details] [diff] [review]
Patch
(In reply to :Gijs Kruitbosch from comment #3)
> Why are we setting this to 0 so broadly in the first place? From bug 993369,
> which introduced these, seems like this was originally intended for use in
> menulists? Of course, by now loads of random other labels rely on this rule
> to be aligned properly with the subheadings. :-\
I also wonder why we don't revisit the error in bug 993369 instead of a band-aiding.
> Increasing the specificity will fix the .indent case, but not any
> hypothetical other issues alluded to in comment #0. r=me assuming no such
> cases exist, probably worth doing a mozscreenshots trypush to find that out.
Instructions are at https://developer.mozilla.org/en-US/docs/Mozilla/QA/Browser_screenshots#Try_pushes for try pushes.
> Leaving r?MattN in case he has better ideas.
I don't have better ideas other than revisiting the change from bug 993369.
Attachment #8740767 -
Flags: review?(MattN+bmo) → feedback+
| Assignee | ||
Comment 7•9 years ago
|
||
I ran this through mozscreenshots and there were no differences reported.
https://screenshots.mattn.ca/compare/?oldProject=mozilla-central&oldRev=86730d0a82093d705e44f33a34973d28b269f1ea&newProject=try&newRev=e4efe4a4a291878fc587737d2edbefe49c19316d
Keywords: checkin-needed
| Reporter | ||
Comment 8•9 years ago
|
||
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #7)
> I ran this through mozscreenshots and there were no differences reported.
But note that you ran the primary UI configurations but didn't run the preference ones which are what caught this regression:
https://mxr.mozilla.org/mozilla-central/source/browser/tools/mozscreenshots/preferences/browser_preferences.js
You want `--setenv MOZSCREENSHOTS_SETS=Preferences`
Keywords: checkin-needed
| Assignee | ||
Comment 9•9 years ago
|
||
Sorry, I didn't realize that. Repushed to tryserver, https://treeherder.mozilla.org/#/jobs?repo=try&revision=a785d53a5349
| Assignee | ||
Comment 10•9 years ago
|
||
https://screenshots.mattn.ca/compare/?oldProject=mozilla-central&oldRev=86730d0a82093d705e44f33a34973d28b269f1ea&newProject=try&newRev=a785d53a5349aeeb3c591094e691a4ca7e11bf53&filter=.*prefs.*
Shows no difference on Linux, where do-not-disturb is not supported/implemented. Only differences on OSX/Windows is the DND line. Previous mozscreenshots run showed no differences in any of the other tests.
Between the two mozscreenshot runs, only differences were expected.
Keywords: checkin-needed
Comment 11•9 years ago
|
||
Keywords: checkin-needed
Comment 12•9 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox49:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
Updated•9 years ago
|
Version: unspecified → 48 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•