- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Oct 2017 20:04:35 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `Change default <sup> and <sub> styling?`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Change default <sup> and <sub> styling?<br> <dael> TabAtkins: Dominic read an article about <sub> and <sup> and was wondering if he could change html styllesheet to support them instead of the basic way we do. I think it's okay, but we need yes/no from other people.<br> <dael> florian: There are comments. The problem is when you start nesting.<br> <dael> TabAtkins: Okay. Reasonable.<br> <dael> Rossen: Let's put it back to the issue. There's discussion. We'll bring it back next week.<br> <dael> Rossen: That's the top of the hour.<br> <dael> Rossen: Thank you everyone, we'll talk next week.<br> <fantasai> TabAtkins, the short answer to Domenic's question is "no"<br> <TabAtkins> Yeah, forgot about needing. Makes sense.<br> <TabAtkins> Could maybe apply it to the first level, and do scaling/shifting for nested stuff, but that's complex.<br> <fantasai> TabAtkins: There were proposals for that, see dbaron's links.<br> <fantasai> TabAtkins: They were rejected.<br> <fantasai> TabAtkins: atm, I think the priority is getting myles to fix synthesis so semantics don't break even in basic cases when the font is missing those glyphs :) :) :)<br> <zcorpan> dbaron: github-log-bot is not awake?<br> <zcorpan> at least I don't see any bot comment in https://github.com/w3c/csswg-drafts/pull/1805<br> <dbaron> github: https://github.com/w3c/csswg-drafts/issues/1888<br> <dbaron> trackbot, end meeting<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1888#issuecomment-337711657 using your GitHub account
Received on Wednesday, 18 October 2017 20:04:40 UTC