Intent to implement and ship: text-transform: full-size-kana

[Xidorn Quan]

Summary: A new value of text-transform to convert small Kanas to their full-size counterparts to increase legibility in the expense of accuracy, usually when font size is small, e.g. in ruby.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1498148

Link to standard: https://drafts.csswg.org/css-text-3/#valdef-text-transform-full-size-kana

Platform coverage: All platforms

Estimated or target release: 64

Preference behind which this will be implemented: N/A

Is this feature enabled by default in sandboxed iframes? Yes.

DevTools bug: no extra devtools support is needed.

Do other browser engines implement this? No signal.

web-platform-tests: A new wpt is being added in the implementing bug.

Is this feature restricted to secure contexts? No, because it is just a new value to an existing CSS property.


This feature is currently marked "At Risk" in the spec, but it is a small feature, and causes mostly just cosmetic changes, so it is unlikely to cause any webcompat issue for shipping or unshipping if needed.


- Xidorn

[flo...@rivoal.net]

On Saturday, October 13, 2018 at 9:21:35 PM UTC+9, Xidorn Quan wrote:
> Summary: A new value of text-transform to convert small Kanas to their full-size counterparts to increase legibility in the expense of accuracy, usually when font size is small, e.g. in ruby.
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1498148
>
> Link to standard: https://drafts.csswg.org/css-text-3/#valdef-text-transform-full-size-kana

Looks good to me.

Supporting this will be help authors create documents where they no longer have to choose between using semantically correct markup (small kana) and making ruby look like what they want (full-size-kana).

> web-platform-tests: A new wpt is being added in the implementing bug.

More tests are good, but I've already submitted a PR for this. I suggest reviewing it while you're at it.

https://github.com/web-platform-tests/wpt/pull/13461

> This feature is currently marked "At Risk" in the spec, but it is a small feature, and causes mostly just cosmetic changes, so it is unlikely to cause any webcompat issue for shipping or unshipping if needed.

Pay no attention to "at risk", this is merely about allowing us to push this feature from one level of the spec to the next if we try to transition level 3 out of CR before this is implemented in all engines. This doesn't mean we're not confident in the design of the feature.

—Florian