- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Nov 2017 04:10:37 +0000
- To: public-css-archive@w3.org
Yeah, right, I was too terse, sorry. Here's better status: - cathiechen@tencent.com is working on fixing the current layout engine - [crbug.com/626293](https://crbug.com/626293) fixed the "hidden" issue Tab mentioned. - That caused a few regressions, fixed [in Aug](https://chromium-review.googlesource.com/c/chromium/src/+/593433) and [in Nov](https://chromium-review.googlesource.com/c/chromium/src/+/735303), based on [a design proposal](https://docs.google.com/document/d/1bMerTLCSqHZYAERJ2HDr-4auOSw0eIx8QfD2vY92TNo). - The fixes above apply only to boxes that derive from `LayoutBlockFlow` in our native class hierarchy, but not other block-level boxes. Cathie started working on [fixing for Flexbox](https://chromium-review.googlesource.com/c/chromium/src/+/754768), but Lea's `textarea` might be yet another case, and we know grid and some others are also in this category. We're discussing how to fix this better. - In LayoutNG, I'm re-implementing list item marker, and we're trying to share the code/logic as much as possible. -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1934#issuecomment-343042190 using your GitHub account
Received on Thursday, 9 November 2017 04:10:40 UTC