Closed Bug 1434127 Opened 7 years ago Closed 1 year ago

Inorrect Japanese character in Yu Gothic font using standard variant sequence

Categories

(Web Compatibility :: Site Reports, defect, P3)

Product:
Web Compatibility
Component:
Site Reports
Platform:
Desktop
Windows
Type:
defect

Tracking

(firefox101 affected)

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox101 --- affected

People

(Reporter: lukasz.korczewski, Assigned: denschub)

References

(
URL
)

Details

(5 keywords)

User Story

platform:windows,mac,linux,android
impact:content-missing
configuration:general
affects:all
branch:release

Attachments

(3 files)

Screenshot_1.png
54.03 KB, image/png
Details
sample html
523 bytes, text/html
Details
sample html using compatibility ideograph code point (not VS)
508 bytes, text/html
Details
Attached image Screenshot_1.png —
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20180103231032 Steps to reproduce: I created a webpage containing the following sequence: "爛︀" a character and standard variant selector #1. I displayed the page in FF using Yu Gothic. Actual results: The character displayed is an unrelated character looking like: 欄. Chrome and Internet Explorer displays the character correctly. Expected results: The character should be exactly the same as without the variant selector, that is: 爛.
Has Regression Range: --- → irrelevant
Has STR: --- → yes
Component: Untriaged → Layout: Text
Keywords: fonts
Product: Firefox → Core
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=feae125fca6f&tochange=864067766916 Triggered by: 9d08e98cc18c Masatoshi Kimura — Bug 989557 - Implement a fallback for CJK Compatibility Ideographs Standardized Variants. r=jfkthame
Blocks: 989557
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [parity-Chrome][parity-Edge]
Version: 57 Branch → 31 Branch
Attached file sample html —
Yu Gothic is incorrect.
Yeah, Yu Gothic has a wrong glyph at U+F91E. Firefox just replaces U+721B U+FE00 with U+F91E because they are supposed to be identical. This is a font issue, not a Firefox one.
Assignee: nobody → VYV03354
Assignee: VYV03354 → nobody
Sent a feedback: https://aka.ms/Pehi91
Component: Layout: Text → Desktop
Product: Core → Tech Evangelism
Version: 31 Branch → unspecified
Priority: -- → P5
Whiteboard: [parity-Chrome][parity-Edge] → [parity-Chrome][parity-Edge][sitewait]
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome, parity-edge
Whiteboard: [parity-Chrome][parity-Edge][sitewait] → [sitewait]
Product: Tech Evangelism → Web Compatibility

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Keywords: webcompat:site-wait

After some research, using codepen.io and even introducing the URL in the toolbar, there is a difference in rendering.

Tested with:

Browser / Version: Firefox Nightly 101.0a1 (2022-04-08) (64-bit) / Chrome Version 100.0.4896.75 (Official Build) (64-bit)
Operating System: Windows 10 PRO x64

Notes:

  1. Reproducible regardless of the status of ETP.
  2. Reproducible on the latest build of Firefox Nightly.
  3. Works as expected using Chrome.
Flags: needinfo?(lukasz.korczewski)
Assignee: nobody → dschubert
URL: codepen.io
Status: NEW → ASSIGNED
status-firefox101: --- → affected
OS: Unspecified → Windows
Hardware: Unspecified → Desktop
Severity: normal → S3

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.

Flags: needinfo?(lukasz.korczewski)

Jonathan, do you know if this is still a valid issue, or if the fallback fonts changed or got updated? We haven't seen recent reports on this, and we're tempted to just close this as incomplete.

Severity: S3 → S2
User Story: (updated)
Flags: needinfo?(jfkthame)
Keywords: webcompat:site-wait → webcompat:needs-diagnosis, webcompat:site-report
Priority: P5 → P3
Whiteboard: [sitewait]

(In reply to Dennis Schubert [:denschub] from comment #9)

Jonathan, do you know if this is still a valid issue, or if the fallback fonts changed or got updated? We haven't seen recent reports on this, and we're tempted to just close this as incomplete.

Why don't you confirm it yourself? A test case is attached to this bug. Nothing has changed. Do I have to report the same problem periodically in order to avoid the bug is forgotten and closed as incomplete?

That said, I suggest closing this bug as INVALID because this is not a Firefox issue. (See my comment #3)

Yeah, as far as I can see this is simply a font bug: Yu Gothic has an incorrect glyph for U+F91E.

(FWIW, I also see the same wrong glyph in Chrome and Edge.)

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Flags: needinfo?(jfkthame)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: