- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Jan 2017 14:50:34 +0000
- To: public-css-archive@w3.org
I agree with @drott, #843 is a good issue to discuss separately.
For `ink`, I'm starting to wonder why this feature is an opt-in
design.
* From implementors:
* WebKit skips ink by default.
* Blink implements and wish to skip ink by default in near future
too.
* IIUC Gecko is also looking into this. @upsuper, do you think you
want to enable by default when Gecko supports?
* From authors:
* @ebraminio
[commented](https://github.com/w3c/csswg-drafts/issues/711#issuecomment-264450649)
he wants to skip ink by default.
* Some blogs already have `text-decoration-skip: ink` by default;
e.g., [this page](https://hail2u.net/blog/git-release-v1.2.2.html) has
`a { text-decoration-skip: ink; }`.
I think if all these observations are correct, we should:
* Make skip ink the default behavior for supported configurations. For
non-supported fonts/OS/UA, not skipping is a good fallback behavior.
* Remove `ink` from `text-decoration-skip`.
* Give authors ability to disable skip ink if such feature is desired.
* Give authors ability to force skip ink for undesired cases (e.g.,
line-through) if desired.
...is this too wild?
--
GitHub Notification of comment by kojiishi
Please view or discuss this issue at
https://github.com/w3c/csswg-drafts/issues/727#issuecomment-270130504
using your GitHub account
Received on Tuesday, 3 January 2017 14:50:40 UTC