- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Nov 2016 06:41:11 +0000
- To: public-css-archive@w3.org
I wrote [some testcases](https://dbaron.org/css/test/2016/abspos-in-inline). I'm happy to standardize on the Edge behavior, which I believe matches Chrome for ltr, and does the equivalent for other directions (whereas Chrome does different and sometimes bizarre things for other directions). In particular, as I understand it, that behavior is: * form a containing block from the block-start and inline-start padding-box edges of the first fragment and the block-end and inline-end padding-box edges of the last fragment * If that containing block has a negative width or height, turn each negative width or height into 0 by keeping the edge (in that dimension) that came from the first fragment the same, and changing the edge that came from the last fragment to be equal to the edge from the first fragment I'd note that I didn't thoroughly test different sorts of overlap situations. However, I haven't seen any places Edge deviates from the above description (with EdgeHTML 14.14393). -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/609#issuecomment-259058527 using your GitHub account
Received on Tuesday, 8 November 2016 06:41:17 UTC