Open
Bug 1434127
Opened 6 years ago
Updated 2 years ago
Inorrect Japanese character in Yu Gothic font using standard variant sequence
Categories
(Web Compatibility :: Site Reports, defect, P5)
Tracking
(firefox101 affected)
ASSIGNED
Tracking | Status | |
---|---|---|
firefox101 | --- | affected |
People
(Reporter: lukasz.korczewski, Assigned: denschub)
References
()
Details
(4 keywords, Whiteboard: [sitewait])
Attachments
(3 files)
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: 爛.
Updated•6 years ago
|
Has Regression Range: --- → irrelevant
Has STR: --- → yes
Component: Untriaged → Layout: Text
Keywords: fonts
Product: Firefox → Core
Comment 1•6 years ago
|
||
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
Comment 2•6 years ago
|
||
Yu Gothic is incorrect.
Comment 3•6 years ago
|
||
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
Updated•6 years ago
|
Assignee: VYV03354 → nobody
Comment 4•6 years ago
|
||
Sent a feedback: https://aka.ms/Pehi91
Component: Layout: Text → Desktop
Product: Core → Tech Evangelism
Version: 31 Branch → unspecified
Updated•6 years ago
|
Priority: -- → P5
Whiteboard: [parity-Chrome][parity-Edge] → [parity-Chrome][parity-Edge][sitewait]
Comment 5•6 years ago
|
||
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]
Updated•5 years ago
|
Product: Tech Evangelism → Web Compatibility
Comment 6•5 years ago
|
||
See bug 1547409. Moving webcompat whiteboard tags to keywords.
Keywords: webcompat:site-wait
Comment 7•2 years ago
•
|
||
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:
- Reproducible regardless of the status of ETP.
- Reproducible on the latest build of Firefox Nightly.
- Works as expected using Chrome.
Flags: needinfo?(lukasz.korczewski)
Updated•2 years ago
|
Assignee: nobody → dschubert
URL: codepen.io
Status: NEW → ASSIGNED
status-firefox101:
--- → affected
OS: Unspecified → Windows
Hardware: Unspecified → Desktop
Updated•2 years ago
|
Severity: normal → S3
Comment 8•2 years ago
|
||
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)
You need to log in
before you can comment on or make changes to this bug.
Description
•