- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Apr 2017 03:46:34 +0000
- To: public-css-archive@w3.org
Thank you for the great feedback, @bzbarsky. > In practice, what Gecko seems to implement here is to start at the thing you inherit style from (some handwaving about ::first-line here), and walk up the inheritance chain to the first thing with display not equal to "contents". Blink [checks parent](https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/layout/LayoutBox.h?type=cs&q=IsWritingModeRoot&l=1139) too, not containing block. I believe WebKit does so too. Is the logic mentioned here the same as [blockificaiton](https://drafts.csswg.org/css-display/#blockify)? If so, can we say "blockify if the element has different writing-mode from its parent"? If different, is the fix of s/containing block/parent box/ appropriate? I'm not very familiar with run-in and details of display types, advice appreciated. /cc @fantasai @rune-opera -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1212#issuecomment-293771796 using your GitHub account
Received on Thursday, 13 April 2017 03:46:42 UTC