-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[css-position-3] Coordinates of Containing Blocks of Positioned Boxes from Inline Boxes with Mixed Bidi Direction Text Content are Unclear #7917
Comments
Thanks, this looks like an error in translating the spec from CSS2. The correct definition is this one: https://www.w3.org/TR/CSS2/visudet.html#containing-block-details |
Is there a specific reason to not go for the bounding box of all inline boxes of the element? |
Yes, there is. If the first fragment is a small portion at the end of a line, for example, then positioning yourself at the start/start corner of the bounding box will cause you to position in an unrelated area, not next to any fragment of the actual inline. The edits we just pushed do clarify that when there are multiple fragments on the first/last line, you take the visually first/last one (for the reasons you gave in the original comment). That said, it doesn't appear to be super well-defined what it means if the edges of a containing block are in the wrong order, so we're raising that as a separate issue. |
Filed issue about multi-line containing blocks here: #8284 |
Thanks for elaborating. |
"css-position-3: 2.1. Containing Blocks of Positioned Boxes" says:
When taking into account bidi (see "css-writing-modes-3: 2.4.5. Reordering-induced Box Fragmentation") it is unclear whether first and last are meant logically or visually.
While we consider visual the only useful and expected interpretation in this case, we normally would assume logical when nothing is specified.
Chrome and Firefox have different interpretations:
Source:
Chrome (visual):
![image](https://user-images.githubusercontent.com/43403851/196694766-55b605a7-d9eb-48a1-bf2c-c7da517a7ecd.png)
Firefox (logical):
![image](https://user-images.githubusercontent.com/43403851/196694840-5f1e5246-110d-475c-978c-a861e73dc22e.png)
This also demonstrates how unexpected the logical version is.
Whether extending the paragraph is enough or the processes requires more detailed specification we are not sure.
The text was updated successfully, but these errors were encountered: