- From: Bernhard Fey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Mar 2023 07:50:07 +0000
- To: public-css-archive@w3.org
> A potential option is to alter the containing block depending on what inset properties are set instead. e.g. if both insets in an axis is set, use the bounding-rect, if one inset is set, use the first/last fragment edge. This is similar to our second proposal: > To enable anchoring boxes both at the (visual) start as well as the end of the multi-line inline in all cases a conditional behavior could be introduced. > Let's say the condition is handled via a property with the values: start (initial), end and auto. auto computes to end when inset-inline-start is auto and inset-inline-end is non-auto, and to start otherwise. > The property isn't necessary as the auto behavior could always be used. But this might be to big of a change and a too far reaching effect of different inset-inline-* values. > If the condition is start the behavior is Firefox-like. If it is end it is as well, but uses the last line instead of the first, so inset-inline-end is actually relative to the visual end of the multi-line inline, like for a single line inline. > (Our approach of extending inline fragments to the line edge at their split points could be combined with this approach.) The major difference is that we don't think there should be 3rd behavior for when both `inset-inline` values are non-`auto`. We expect using the bounding rectangle would break a lot more cases than it would improve. However, if a property to control the behavior would be introduced `bounding-box` could be an additional value. > if I try to position against the bottom left corner in LTR on a multiline box that doesn't start on the left edge, I'll end up somewhere at the bottom middle of the paragraph. Considering that there are no obvious bottom-left and top-right (start-end and end-start) corners that would be fine with us. However it does show that a property giving the author various options is probably the best solution. -- GitHub Notification of comment by bernhardf-ro Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8284#issuecomment-1489851127 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 March 2023 07:50:09 UTC