- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Sat, 25 Jan 2020 22:46:08 +0000
- To: public-css-archive@w3.org
I think I'm fine with that. I'd like to note that the rationale between this issue and #4277 seem to be quite different. This is about overriding per-platform default, and the other is about overriding browser heuristic. If the goal is to override per-platform default of not doing skip ink, a value should still selectively avoid skipping ink on certain characters, while for the other that behavior should be suppressed. However, given https://github.com/w3c/csswg-drafts/issues/2818#issuecomment-416172220 both ideas were from @jfkthame, and I suspect he's probably concerning more about what he said in #4277 rather than per-platform default thingy. Also it doesn't seem to me that difference on per-platform default is something meaningful anymore given the current landscape that every major browser has shipped that by default on all platforms they support. So I think three values like what is done in https://github.com/w3c/csswg-drafts/commit/0d4d229d828ca297f3974a4d1820cd28e112f3d2 makes sense. But similar to @jensimmons in https://github.com/w3c/csswg-drafts/issues/4277#issuecomment-574779188 I personally think `all` is better than `always` as well. The `all` here implies that we apply the skip-ink to all characters touching underline / overline, overriding browser heuristic of conditional applying. And indeed pairing `none` with `always` doesn't feel very sensible. -- GitHub Notification of comment by upsuper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2818#issuecomment-578450094 using your GitHub account
Received on Saturday, 25 January 2020 22:46:09 UTC