Bug 212341 - open-quote / close-quote content doesn’t fallback to language when region not understood
Summary: open-quote / close-quote content doesn’t fallback to language when region not...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: Safari 13
Hardware: Mac macOS 10.14
: P2 Normal
Assignee: Nobody
URL: http://wpt.live/css/css-content/quote...
Keywords: InRadar, WPTImpact
Depends on:
Blocks:
 
Reported: 2020-05-25 02:04 PDT by Robin Whittleton
Modified: 2023-07-27 04:58 PDT (History)
6 users (show)

See Also:


Attachments
Quote testcase (228 bytes, text/html)
2020-05-25 02:04 PDT, Robin Whittleton
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Whittleton 2020-05-25 02:04:05 PDT
Created attachment 400187 [details]
Quote testcase

Webkit attempts to provide automatic quote styles, based on quotesDataLanguageMap (https://trac.webkit.org/browser/webkit/trunk/Source/WebCore/rendering/RenderQuote.cpp?rev=125476#L55 / https://html.spec.whatwg.org/multipage/rendering.html#quotes). This works for the specific languages in the map, but fails when a language-region pair is found that isn’t in the map.

For example (and see the testcase), if you have <q lang="de"> then correct German quotes will be applied, but if you have <q lang="de-AT"> then it just uses straight typographical quotes. <q lang="de-DE"> also fails.

In the case of an unknown region, the quotes displayed should be based on the fallback root language. As I understand it, this is specified in the WhatWG spec by the sentence “The quotes are derived from the delimiter blocks, with fallback handled as specified in the CLDR documentation.”.

This is also a problem in Chromium, but works as expected in Firefox.
Comment 1 Robin Whittleton 2020-05-25 02:11:41 PDT
Chromium bug for the same issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1086115
Comment 2 Radar WebKit Bug Importer 2020-05-25 12:13:17 PDT
<rdar://problem/63603756>
Comment 3 Robin Whittleton 2020-06-10 23:53:06 PDT
Reported as fixed in Chrome, to appear in production in 85.