- From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Apr 2017 02:20:43 +0000
- To: public-css-archive@w3.org
> Aside from display: contents, what else would make the parent box not the parent element? It depends on how you define "parent box", obviously. I have yet to see a definition, so I can't tell you for sure. But in terms of implementations, out-of-flows have a parent box that is not their parent element in at least some implementations. Also, the right question is "what else that might ever get defined in CSS would make the parent box not the parent element?" That is, if the intent is for computed style to not depend on box construction, but the definition is done in terms of boxes, it becomes very hard to implement computed style without reference to boxes that is not just going to break as new CSS features are added. > changing the inner display type doesn't seem necessary Um... I don't follow. If I absolutely position a thing that's display:inline, its inner display had better change. That's how it's been specced forever, how it's implemented in all browsers, and websites depend on it. Am I just missing something about the change you just made to css-display and how it relates to this case? -- GitHub Notification of comment by bzbarsky Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1212#issuecomment-295043410 using your GitHub account
Received on Wednesday, 19 April 2017 02:20:49 UTC