- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Nov 2016 06:55:13 +0000
- To: public-css-archive@w3.org
Learned [initial-letter
spec](https://drafts.csswg.org/css-inline/#sizing-drop-initials)
quickly, apologies in advance if I missed something obvious.
We should discuss `initial-letter` and `::first-letter` separately. I
understand it's often used together and thus you want to discuss
together, but both technically and spec-wise, they look separate to
me.
For `initial-letter` applying to the inline-level first child of a
block container, I think the spec looks fine to me and, while Blink
doesn't implement this property yet, I suppose it should just work.
The `::first-letter` and `text-combine-upright` looks like an
unfortunate combination. Since `::first-letter` creates a pseudo
element before layout runs, the tree should look like the below to the
layout engine:
```
<p>
<span style="text-combine-upright: all">
<span style="initial-letter: 3">1</span>
3
</span>
is a really nice number
</p>
```
I think how `initial-letter` and `text-combine-upright` should render
this tree is clearly defined; it just does not work well for the use
case.
I don't know how to solve this use case. One possible idea is to
change `initial-letter` so that it determines the first letter in
layout, not in style. Maybe people more familiar on pseudo elements
and `initial-letter` can come up with better ideas?
--
GitHub Notification of comment by kojiishi
Please view or discuss this issue at
https://github.com/w3c/csswg-drafts/issues/653#issuecomment-258357299
using your GitHub account
Received on Friday, 4 November 2016 06:55:19 UTC