- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 May 2018 23:43:35 +0000
- To: public-css-archive@w3.org
Oy. There's a good argument for either way: the argument for leaving it as-is, is that in the section defining a particular set of keywords, it's more clearly explained that keyword means in isolation. Probably if the default was simple, I'd lean towards accepting your change... but the "default" outer display type used when an outer display type isn't specified is actually dependent on which inner display type was specified. (It usually implies 'block', but 'ruby' implies 'inline'.) Also, outer display types are only implied if an inner display type is specified and vice versa: if a layout-internal display type is specified, there is no default outer display type or inner display type, as the concept doesn't apply. Ditto 'none' and 'contents'. ... So altogether, I'm leaning towards rejecting this editorial change. I'll check with @tabatkins, though. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2658#issuecomment-391175246 using your GitHub account
Received on Tuesday, 22 May 2018 23:43:41 UTC