1901952 - www.francebleu.fr - Rendering is broken when changing default font size to a smaller value

Status: RESOLVED INVALID

(Core :: Layout, defect, P3)

Description

[Raul Bucata]

From github: https://github.com/webcompat/web-bugs/issues/137324.

<!-- @browser: Firefox 128.0 -->
<!-- @ua_header: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 -->
<!-- @reported_with: unknown -->

URL: https://www.francebleu.fr/infos/faits-divers-justice/laval-une-bombe-artisanale-explose-au-lycee-douanier-rousseau-sans-faire-de-blesses-ni-de-degats-8592660#xtor=RSS-147

Browser / Version: Firefox 128.0
Operating System: Linux
Tested Another Browser: Yes Other

Problem type: Design is broken
Description: Items are overlapped
Steps to Reproduce:
Rendering is broken on nightly (non snap), looks OK on stable (snap). No specific tracking protection. Unresponsive to disabling uBlock Origin.
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2024/5/92829076-bd2e-498d-aa2e-32fa2c50935e.jpg">
</details>

<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>

From webcompat.com with ❤️

Change performed by the Move to Bugzilla add-on.

Comment 1

[Raul Bucata]

The issue was reported via the webcompat.com reporter. Since the issue is related to changing font size, we have moved the issue. Please feel free to move the issue to the correct Product and Component.

Comment 2

[Emilio Cobos Álvarez (:emilio)]

I can reproduce. Unfortunately it seems the page is relying on the 16px font-size, which is something that we generally can't fix. This is also reproducible on a clean profile if you have Zoom -> Text Only and zoom out.

Maybe changing the default font-size should give a warning like the text zoom one you added Morgan?

But otherwise I think this is INVALID, unfortunately...

Comment 3

[:gerard-majax]

That was my worry as well, but I preferred we verified there's no bug on our side ☺️

Comment 4

[Daniel Holbert [:dholbert] (vacation until Jun 23)]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #2)

Maybe changing the default font-size should give a warning like the text zoom one you added Morgan?

(This was in bug 1864445, for reference.)

But otherwise I think this is INVALID, unfortunately...

Agreed.

Comment 5

[Daniel Holbert [:dholbert] (vacation until Jun 23)]

We could spin off a followup bug for adding a warning to the preferences UI like in bug 1864445, but I'm a little anxious about warning-creep here. We could just-as-justifiably warn for nearly any non-default configuration option that affects rendering in our preferences. E.g. if a user changes link colors to orange, then they're not going to be able to see any links if they visit a page with an orange background (if the page doesn't define its own color for link-text) -- but I'm not sure it's worth warning the user about this when they adjust their color preferences.

Similarly, if the user chooses some super-cool font as their default serif font (and they keep the default 16px font-size), and their chosen font happens to have unusual metrics, then they might similarly get breakage for pages that aren't prepared for text to be a little larger or smaller than normal.

Rather than warning on every such change in our preferences UI, perhaps it'd be better to have some bit of catch-all UI somewhere to say "the following settings are currently non-default which might conceivably break some web pages if they've got a fragile dependency on default browser settings", and then list customizations to fonts/colors/default-zoom/text-zoom/etc. But I'm not sure where that sort of UI would belong -- possibly in about:support (we already have Important Modified Preferences but that's got a lot of other stuff too and it's a bit buried and not particularly user-readable).

Comment 6

[Morgan Reschenberg [:morgan]]

(In reply to Daniel Holbert [:dholbert] from comment #5)

Rather than warning on every such change in our preferences UI, perhaps it'd be better to have some bit of catch-all UI somewhere to say "the following settings are currently non-default which might conceivably break some web pages if they've got a fragile dependency on default browser settings", and then list customizations to fonts/colors/default-zoom/text-zoom/etc. But I'm not sure where that sort of UI would belong -- possibly in about:support (we already have Important Modified Preferences but that's got a lot of other stuff too and it's a bit buried and not particularly user-readable).

I think this is the best path forward, I'm worried about ~all the potential surfaces we could add warnings to, too.