- From: Di Zhang via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Dec 2024 00:37:17 +0000
- To: public-css-archive@w3.org
After the meeting, we read through these issues, and upon further reflection, we don’t agree these are blocking issues for a first MVP version of reading-flow (defined in [Display Level 4](https://www.w3.org/TR/css-display-4/)). They are either about the new and in-progress Masonry feature or about adding new CSS properties to complement reading-flow. We believe these can be handled as incremental improvements to the CSS reading-flow property, in particular because the Masonry layout mode is still in the Design/Implementation phase and should not be a blocker. For example, it seems natural to add something like `reading-flow: masonry-order` or similar, which would not affect existing values or behavior. We feel that `reading-flow` is a valuable feature, and we are anxious to make it a reality. Having said that, we are happy to collaborate on potential solutions for these use cases ahead of upcoming CSSWG meetings and at the F2F. @rachelandrew has [offered to help](https://github.com/whatwg/html/pull/10613#issuecomment-2553004703) as well. We are hopeful that these issues can be discussed at length at the upcoming CSSWG F2F and get resolved. We will comment with proposals over the coming weeks. -- GitHub Notification of comment by dizhang168 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11328#issuecomment-2556022272 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 December 2024 00:37:18 UTC