Open
Bug 1258692
Opened 9 years ago
Updated 3 years ago
Fonts having the font-size specified in rem-units will not zoom in
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: bugzilla-firefox, Unassigned)
Details
(Keywords: css3, fonts)
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160315153207
Steps to reproduce:
I opened some pages (in certain protected areas, bank and government) that contain text with font-size attribute in em units and other in rem units (as appeared later). Browser: Firefox 45.0.1.
I tried the same pages in Internet Explorer 11.0: no problem.
Actual results:
Since some text were very small, I zoomed in. Some text did zoom in, but other texts remained the same (very small).
I checked the font size attributes. The texts not zooming in have the rem-unit. Zooming in only works on the text having the em unit or other.
Expected results:
All texts should zoom in (and out).
Bug title (corrected): Fonts having the font-size specified in rem-units will not zoom in.
Updated•9 years ago
|
Component: Untriaged → Layout: Text
Product: Firefox → Core
Summary: Fonts having the font-size specified in rem-units enlarged when the page is zoomed in → Fonts having the font-size specified in rem-units will not zoom in
Comment 2•9 years ago
|
||
I just tried a simple testcase with elements having both rem and em units, zoomed in, and the text in both types zoomed as expected.
Could you give a specific example of a page where you see this problem (without requiring a bank or gov't login), or create a testcase that shows the same behavior?
(In reply to Jonathan Kew (:jfkthame) from comment #2)
> I just tried a simple testcase with elements having both rem and em units,
> zoomed in, and the text in both types zoomed as expected.
>
> Could you give a specific example of a page where you see this problem
> (without requiring a bank or gov't login), or create a testcase that shows
> the same behavior?
Sorry, I can't. Perhaps it is a very specific situation. Please ignore this bug and change the status appropriately.
My apologies.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•