Re: [csswg-drafts] [css-text] cursive shaping breaks needs better scoping (#698)

> @jfkthame Right, but @r12a seems to be challenging that decision so wanted to ask your opinion.

IIUC, this was mostly about font-related properties (size, weight, etc); he then mentioned border as well:

> Note also that a border doesn't break the joining behaviour in Firefox and Edge. This perhaps seems like reasonable behaviour for highlighting items, and i wonder whether we should drop that from the list of things that break shaping? I suppose the argument (as for margins and padding) is that this might have been a block element that has been added inline. It seems a pity, however, that such a possibility would rule out the ability to put a border around one character in a cursive sequence using inline markup when wanted.

but the hypothetical use-case suggested here would be better served by outline, IMO.

I think the properties that introduce visual separation between the adjacent elements (so any of margin/border/padding at the relevant side) *should* indeed interrupt shaping, and I've seen sites where the current Firefox behavior of shaping across such gaps results in broken rendering. People do things like navigation or menu bars across a page:

    <div class="nav"><a>home</a><a>away</a></div>

and apply margins to the `<a>` elements to spread them across the line, and when Firefox applies shaping across the resulting gaps, the result looks terrible. (I don't have a bug number to hand but we've had real-world reports of this.)

-- 
GitHub Notification of comment by jfkthame
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/698#issuecomment-444467145 using your GitHub account

Received on Wednesday, 5 December 2018 12:22:57 UTC