Created attachment 799447 [details]
Bugzilla when using a "Very Large" default font
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
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
The content moves down proportionately because it is offset from the top by ems or pts, which scale with the user's font preference
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.
*** Bug 908371 has been marked as a duplicate of this bug. ***
*** Bug 913963 has been marked as a duplicate of this bug. ***
Created attachment 801366 [details] [diff] [review]
Comment on attachment 801366 [details] [diff] [review]
Review of attachment 801366 [details] [diff] [review]:
Committing to: bzr+ssh://firstname.lastname@example.org/bmo/4.2/
Committed revision 8996.
Not fixed... dunno why it was RESOLVED FIXED.
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.
Created attachment 803203 [details]
Bugzilla overflow still exists.png
Illustrating problem still exists
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.
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!
(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 :)
this fix is now live.