Closed Bug 1799942 Opened 3 years ago Closed 3 years ago

[webcontent] Regression: Display names containing Emoji on Nitter aren't bolded

Categories

(Core :: Graphics: Text, defect, P3)

Unspecified
Android
defect

Tracking

()

RESOLVED DUPLICATE of bug 1798036
Tracking Status
firefox-esr102 --- unaffected
firefox106 --- unaffected
firefox107 --- fixed
firefox108 --- fixed

People

(Reporter: kbrosnan, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

From github: https://github.com/mozilla-mobile/fenix/issues/27773.

Site with issue and any steps to reproduce

https://nitter.snopyta.org/firefox

Load the Nitter link in Fenix Nightly and notice that unlike the display names not containing any Emoji the display name of the Firefox account isn't bolded.
This must have regressed somewhere between 106 and 107 because Fenix 106.1.0 is unaffected but 107.0b1 is already affected.

Expected behavior

Screenshot from Fenix 106.1.0:

Actual behavior

Screenshot from Fenix Nightly:

Does toggling Tracking Protection fix the issue? (Press the shield icon in the toolbar while on the site to see toggle)

No.

Can you reproduce in Chrome (or other non-Mozilla browser)?

No Chrome behaves the same as Fenix 106.1.0.

Device information

  • Android device: Pixel 4a (5G)
  • Android version: 13
  • Fenix version: 108.0a1

┆Issue is synchronized with this Jira Task
┆Link To Issue: https://mozilla-hub.atlassian.net/browse/FNXV2-21959

Change performed by the Move to Bugzilla add-on.

Attached image firefox-nitter.png

This is an issue with the variable-font version of Roboto, as seen in bug 1798036, and fixing that should resolve this case as well.

It was exposed here as a side-effect of bug 1791558, which enabled us to use the new Noto Color Emoji font; this affects the text-rendering path that gets used.

Depends on: 1798036
Regressed by: 1791558

Set release status flags based on info from the regressing bug 1791558

Severity: -- → S3
Priority: -- → P3

Although a slightly different example, this is definitely the same underlying issue as bug 1798036; dup'ing.

Status: NEW → RESOLVED
Closed: 3 years ago
Duplicate of bug: 1798036
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: