- From: SelenIT via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Aug 2017 12:42:10 +0000
- To: public-css-archive@w3.org
I still consider "multi-box" inline elements created by block box intrusion contradicting the Priority of Constituencies principle. I see completely no reason for them to be any different from inline boxes fragmented between different page or column boxes, other than theoretical difficuilty to describe the the box tree in the first case. And I see no reasons for the author to expect them to render differently. Are there really no other way to resolve the box tree problem in that case other than making inline element "multi-box"? Can't we, for example, consider two anonymous block boxes created by the block intrusion a single anonymous block box fragmented into two parts instead, with single, but fragmented, inline box inside? -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1706#issuecomment-321243750 using your GitHub account
Received on Wednesday, 9 August 2017 12:42:11 UTC