search

webcompat / web-bugs

A place to report bugs on websites.
https://webcompat.com
Mozilla Public License 2.0
740 stars 63 forks source link

www.gmbinder.com - Incorrect text rendering #110041

Open deatheternal2 opened 2 years ago

deatheternal2 commented 2 years ago

URL: https://www.gmbinder.com/

Browser / Version: Firefox 91.0 Operating System: Windows 7 Tested Another Browser: Yes Chrome

Problem type: Something else Description: On gmbinder the coding is not working on the diplayed page. Steps to Reproduce: https://www.gmbinder.com/share/-NA_SABGQ0qIf0v2FgFd Is an example. On Chrome the stat block is correct. FireFox doesnt seam to work well with "At its core, GM Binder uses Markdown syntax in its editor, and converts this content into well formed HTML and CSS used to generate PDF files."

View the screenshot Screenshot
Browser Configuration
  • None

From webcompat.com with ❤️

softvision-oana-arbuzov commented 2 years ago

Thanks for the report, I was able to reproduce the issue. image

Note: The issue is not reproducible on Chrome.

Tested with: Browser / Version: Firefox Nightly 106.0a1 (2022-08-31), Firefox Release 104.0.1 Operating System: Windows 10 Pro

Moving to Needsdiagnosis for further investigation.

[qa_35/2022]

wisniewskit commented 2 years ago

If I drop this CSS, Firefox renders as Chrome does for me:

.phb hr + hr + section blockquote {
  column-fill: auto;
}

It looks like Firefox is deciding to only use one column in cases where I'm not sure why it wouldn't use two, so I've filed bz1789548.

It looks we could work around this by using column-fill:balanced for now, as it looks like Chrome, Safari and Firefox are agreeing on the rendering with that value.

webcompat-bot commented 2 years ago

Generate outreach template

wisniewskit commented 2 years ago

@miketaylr: so this is actually Chrome's bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1156312

As TYLin puts it, "They shouldn't force column-balancing with column-fill:auto + height: auto."

wisniewskit commented 2 years ago

@karlcow , does WebKit have a bug on file for this as well? (it seems to also have the same problem, given my testcase).

wisniewskit commented 1 year ago

This is now working the same in Chrome and Firefox, but Safari has not yet fixed the interop issue. I've filed https://bugs.webkit.org/show_bug.cgi?id=255064 for them to take a look.

deatheternal2 commented 1 year ago

thank you very much!

On Wednesday, April 5, 2023 at 04:33:26 PM PDT, Thomas Wisniewski ***@***.***> wrote:

This is now working the same in Chrome and Firefox, but Safari has not yet fixed the interop issue. I've filed https://bugs.webkit.org/show_bug.cgi?id=255064 for them to take a look.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>