Closed
Bug 912460
Opened 11 years ago
Closed 11 years ago
Header covers content on large font size or narrow browser window
Categories
(bugzilla.mozilla.org Graveyard :: Sandstone/Mozilla Skin, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Kyli, Assigned: glob)
References
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.57 Safari/537.36
Steps to reproduce:
Increase browser default font size
Actual results:
The top bar, which is sized automatically by its content, becomes taller, obscuring the content below it, which is offset exactly 80 pixels from the top
Expected results:
The content moves down proportionately because it is offset from the top by ems or pts, which scale with the user's font preference
Updated•11 years ago
|
Assignee: ui → nobody
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: 4.2.6 → Production
Component: User Interface → Sandstone/Mozilla Skin
Summary: Top bar covers content on large font size → Header covers content on large font size
Comment 1•11 years ago
|
||
Bram. When you have a spare cycle, can you take a look at this and also bug 908371. Seems like it would just be a CSS change needed but your CSS-fu is stronger.
dkl
Flags: needinfo?(bram)
Summary: Header covers content on large font size → Header covers content on large font size or narrow browser window
Assignee: nobody → glob
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attachment #801366 -
Flags: review?(dkl)
Flags: needinfo?(bram)
Comment 5•11 years ago
|
||
Comment on attachment 801366 [details] [diff] [review]
912460_1.patch
Review of attachment 801366 [details] [diff] [review]:
-----------------------------------------------------------------
Good. r=dkl
Attachment #801366 -
Flags: review?(dkl) → review+
Committing to: bzr+ssh://bjones%40mozilla.com@bzr.mozilla.org/bmo/4.2/
modified skins/contrib/Mozilla/global.css
Committed revision 8996.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Not fixed... dunno why it was RESOLVED FIXED.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 8•11 years ago
|
||
It's marked fixed because it was committed to the source repo. However deployments to bugzilla.mozilla.org only happen approximately once a week, and this just missed the last one. Follow glob's blog (http://globau.wordpress.com/) if you'd like to see when things are deployed.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 10•11 years ago
|
||
Yes, as I say, we are fully aware that this still exists on bugzilla.mozilla.org. At our next update (probably next Thursday), the fix will be deployed, and the problem will go away.
Comment 11•11 years ago
|
||
I am aware of this bug and was planning on working on it tomorrow after our user research session is done. But it sounds like a fix is already deployed.
@glob, does the fix fully resolves the problem? If so, I think I’ll have to skip on this bug. Sorry!
Assignee | ||
Comment 12•11 years ago
|
||
(In reply to Bram Pitoyo [:bram] from comment #11)
> @glob, does the fix fully resolves the problem? If so, I think I’ll have to
> skip on this bug. Sorry!
yes, i believe we're good here :)
Assignee | ||
Comment 13•11 years ago
|
||
this fix is now live.
Updated•6 years ago
|
Product: bugzilla.mozilla.org → bugzilla.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•