Fast Scrolling on fonts.google.com Makes Site Fail
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
People
(Reporter: haik, Unassigned)
Details
Attachments
(1 file)
|
1.03 MB,
image/png
|
Details |
Failure screenshot with console output
When rapidly scrolling up and down on fonts.google.com in Nightly, the site eventually displays an error (a site error, not a browser error) "Something went wrong. Please try again soon." This is reproducible for me on Nightly running macOS 13 Beta (22A379) on a M1 MacBook Pro. I can not reproduce the problem on Release 106. And it is not reproducible with Chrome or Safari.
|
||
Comment 1•3 years ago
|
||
Does this work for you if you change gfx.downloadable_fonts.otl_validation to false? I think that might explain the nightly vs. release difference, and seemed to work for me on my testing.
|
||
Comment 2•3 years ago
|
||
Yeah, from time to time we see invalid font resources on fonts.google.com, and in Nightly that causes them to fail to load because we validate the OpenType layout tables.
I suspect the problem arises when they generate small subset fonts to use on the search page, because going directly to https://fonts.google.com/noto/specimen/Noto+Sans+Marchen works fine and displays the font, but going to https://fonts.google.com/?query=Marchen immediately fails.
|
|
||
Comment 3•3 years ago
|
||
The root of the issue appears to be a harfbuzz font-subsetter bug, now filed as https://github.com/harfbuzz/harfbuzz/issues/3853.
|
|
||
Comment 4•3 years ago
|
||
Alright, it seems this is not a Firefox bug then.
|
Reporter | |
Comment 5•3 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1)
Does this work for you if you change
gfx.downloadable_fonts.otl_validationtofalse? I think that might explain the nightly vs. release difference, and seemed to work for me on my testing.
Yep, with gfx.downloadable_fonts.otl_validation=false I can no longer reproduce the problem.
|
|
||
Comment 6•3 years ago
|
||
Just FTR, a fixed Noto Sans Marchen resource has been deployed on Google Fonts, so this specific case is no longer an issue.
Also, the underlying bug in the harfbuzz font subsetter has been addressed, so it shouldn't keep coming up.
Description
•