Closed
Bug 1334030
Opened 7 years ago
Closed 6 years ago
www.pakistanpapers.com (and other pages) - fonts are sized differently in chrome and firefox
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1127441
People
(Reporter: karlcow, Unassigned)
References
Details
(Whiteboard: [webcompat])
This is a spinoff of a webcompat issues https://webcompat.com/issues/4310 The framesets content are resized differently in Chrome and Firefox. Chrome seems to apply a zoom for some part of the content. The code is: <frameset rows="90,*" frameborder="NO" framespacing="0" border="0"> <frameset cols="18%,*"> <frame src="pak/logo.html" name="logo" frameborder="NO" scrolling="NO"> <frame src="pak/ad.html" name="top" marginwidth="0" marginheight="0" scrolling="NO" noresize="NORESIZE" frameborder="NO" align="TOP" border="0"> </frameset> <frameset cols="18%,*"> <frame src="pak/left.html" name="left" marginwidth="0" marginheight="0" frameborder="NO" border="0" scrolling="NO"> <frame src="pak/headlines.html" name="main" frameborder="NO"> </frameset> <noframes> <BODY> <P>This page uses frames, but your browser doesn't support them. Please get a decent browser from <a href="http://www.microsoft.com/ie">Microsoft</a> or <a href="http://www.netscape.com">Netscape</a> </P></BODY></noframes> </frameset>
Reporter | ||
Updated•7 years ago
|
See Also: → https://webcompat.com/issues/4310
Whiteboard: [webcompat]
Comment 1•7 years ago
|
||
I don't see any fundamental difference in how the <frame>s are handled in those screenshots. It just seems the text is larger in one of them. Is that difference still present if you load just that frame? http://www.pakistanpapers.com/pak/headlines.html
Flags: needinfo?(kdubost)
Reporter | ||
Comment 2•7 years ago
|
||
ok on a closer look. the same thing is happening with the individual pages. So probably not related to frames, but to usual differences we handled viewport and text size compared to Chrome. Chrome does some magic with font-size. (to be fixed but working on that https://github.com/whatwg/compat/issues/62 ) For example this specific page is has a font-size: 16px the "li" elements in Firefox have 16px too, but in Chrome they become 45.8793px. So Chrome has artificially inflated the fonts. I think there is already an issue for this in Bugzilla. Need to find this and close as a duplicate.
Flags: needinfo?(kdubost)
Reporter | ||
Comment 3•6 years ago
|
||
What do you think about this one? (in the context of Bug 1123938 ) Thanks.
Flags: needinfo?(botond)
Comment 4•6 years ago
|
||
It doesn't seem to be bug 1423013, nor any of the other dependent bugs I've filed so far for bug 1123938. It seems to be some sort of font inflation heuristic that Chrome is using and we are not. In fact, I see the same effect when looking at any bugzilla page, including this one. In Fennec, the text in the comments is small and you have to zoom in to read in, while in Chrome the text is large enough to be readable right off the bat.
Flags: needinfo?(botond)
Comment 5•6 years ago
|
||
workaround |
If, in Fennec, you go to Settings -> Accessibility and enable "Use system font size", we do the font inflation as well, with results comparable to Chrome. It looks like that setting was changed to be off by default in bug 1127441. So, I think this is a WONTFIX, unless you'd like to argue that for webcompat reasons the setting should be on by default (in which case, please move the bug to the Firefox for Android component).
Blocks: 1127441
Updated•6 years ago
|
Summary: www.pakistanpapers.com - framesets are sized differently in chrome and firefox → www.pakistanpapers.com (and other pages) - fonts are sized differently in chrome and firefox
Reporter | ||
Comment 6•6 years ago
|
||
Ah font inflation I had forgotten about this. Thanks a lot. Let's close this.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Core → Core Graveyard
Assignee | ||
Updated•6 years ago
|
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•