- From: kannanwisen via GitHub <noreply@w3.org>
- Date: Sat, 26 Jul 2025 04:33:42 +0000
- To: public-css-archive@w3.org
Thank you for your perspective. I understand the argument that, from a strict specification architecture standpoint, a BFC's direct responsibility is the vertical stacking of block-level boxes. However, I maintain that this narrow definition does not accurately describe the practical reality and full role of a Block Formatting Context. This makes the current wording a misleading oversimplification for developers who rely on the specification for a complete mental model. Here are the key points supporting this view: 1. **Direct Containment of Line Boxes:** A BFC does not only contain block-level boxes. When it encounters inline content, it contains line boxes, which are fundamentally different from block-level boxes. While the mechanism might involve "anonymous block boxes," the practical reality is that the BFC is directly responsible for stacking these line boxes, which are themselves horizontal containers for inline content. A definition that ignores this is incomplete. 2. **Responsibility for Floats:** One of the most critical and practical uses of a new BFC is to contain floats. The BFC must know about the floats inside it to correctly determine its own height and to correctly position the in-flow block boxes around those floats. A definition that makes no mention of this primary function fails to describe what a BFC actually does. 3. **The Developer's Perspective:** A developer debugging a layout issue must consider all interacting elements within a BFC's boundary—block, inline, and floated. The final rendered layout is a result of all these systems working together. A useful definition should describe this holistic reality, not just one isolated aspect of the abstract model. For these reasons, I believe a more precise definition is needed to provide developers with a truly accurate understanding of this foundational layout concept. -- GitHub Notification of comment by kannanwisen Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12524#issuecomment-3121237799 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 26 July 2025 04:33:43 UTC