W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2017

[csswg-drafts] [css-text-decor] A new property for text decorations to skip ink

From: Koji Ishii via GitHub <sysbot+gh@w3.org>
Date: Fri, 20 Jan 2017 11:03:03 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-202112937-1484910181-sysbot+gh@w3.org>
kojiishi has just created a new issue for 

== [css-text-decor] A new property for text decorations to skip ink ==
>From the [IRC 
log](https://log.csswg.org/irc.w3.org/css/2017-01-11/#e757645) of the 
WG discussion on issue #707, #727, and #843, we agreed to add a 
property to control skipping ink in L3, and defer other controls to 

This is to discuss how the property should look like.

@FremyCompany said
>  ink skipping: yes or no should be in level 3

and given #707 and #727, @fantasai suggested

> auto | yes | no


As far as I understand, the discussion points are:
* Property name. Is `text-decoration-skip-ink` appropriate?
  - It may or may not be part of the shorthand in L4, see #843 for 
more details.
  - It may not include `line-through`, does not at least for `auto`, 
see #711 for more details.
* Values:
  - I think it's reasonable to have `auto` as an initial value, and 
we're almost in consensus on this point in #727?
  - Opt-out is quite clear, easy to define, easy to understand. Just 
wondering on the naming, is `no` good?
  - `yes` isn't as clear to me; how should we define it? We're seeing 
a few cases `auto` should not skip ink; `line-through`, per-script, or
 when position is inappropriate in some scripts. Should it turn on for
 all cases? Maybe we want different control for `line-through` and 
per-script to avoid unintentional breakages?

/cc @fantasai @frivoal @litherum @FremyCompany @dbaron @astearns 
@tantek @eaenet @drott
I can't find github account for Jenn and skk (anyone know?), all 
others in the IRC log are on the line above.

Opinions/discussions appreciated.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/962 using your GitHub 
Received on Friday, 20 January 2017 11:04:04 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:07 UTC