Open Bug 1604636 Opened 6 years ago Updated 3 years ago

Rendering differences on Zalgo text

Categories

(Core :: Layout: Text and Fonts, defect, P3)

defect

Tracking

()

People

(Reporter: mgaudet, Unassigned)

Details

Attachments

(4 files)

Attached image Nightly Rendering.

https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1969471 has some Zalgo text it, and it renders quite a bit worse in nightly than in either Chrome or Safari.

(See Attachments)

Attached image Safari.png
Attached image Chrome.png

(I'd argue Chrome's got the clearest rendering; but as to correctness ¯_(ツ)_/¯)

Attachment #9116554 - Attachment description: Release rendering → Release rendering (Windows)

I don't think there is any particularly "correct" rendering for junk like this. In any given browser, you're probably seeing a mixture of various fonts, depending on browser defaults and whatever fallback finds in the environment, as the main font being used for the content doesn't support many of the characters that are present. The result of throwing lots of combining marks in a mixture of fonts into the text can't really be expected to be consistent or predictable or "readable".

If the content were styled with a font that actually supported all the characters present, we could discuss whether it's being rendered correctly. As it is, it looks more like someone just threw handfuls of glyphs at the page, and they stuck wherever they happen to fall. Different browsers, or even the same browser on different systems, will likely have grabbed glyphs from different font buckets, so naturally the results will vary.

Priority: -- → P3
Severity: normal normal → S3 S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: