[Webkit-unassigned] [Bug 267700] <br> tags are incorrectly effected by *{position:absolute; }
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jan 19 05:42:06 PST 2024
https://bugs.webkit.org/show_bug.cgi?id=267700
--- Comment #3 from zalan <zalan at apple.com> ---
(In reply to Thepaceis at gmail.com from comment #2)
> (In reply to zalan from comment #1)
> > Thank you for reporting this issue.
> > This new behavior is considered a progression and it is inline with the CSS
> > spec as discussed here https://github.com/w3c/csswg-drafts/issues/5749
> > (Firefox has been behaving like this for quite some time)
>
> Well, although I may not agree with the reasoning behind this new behaviour,
> I do appreciate you getting back to me.
>
> There needs to be a reliable analogue to \n, and it feels like someone
> didn't think this through.
>
> It would be nice to see a usecase where this new behaviour makes sense? It
I don't think there's a such a use case. This change was carried out simply to align the implementation with the relevant CSS spec i.e. when an inline level element gains out-of-flow positioning, it should stop affecting the neighboring in-flow content. Whether having such forced line break makes sense, I am not sure. You could argue that instead of blockification we should apply inlinification (or rather ignore blockification) on forced line break inline level boxes and let them always be in-flow. If you feel strongly about it, you should open an issue at https://github.com/w3c/csswg-drafts/issues.
I am going to close this bug for now (works as expected).
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240119/008f4e41/attachment.htm>
More information about the webkit-unassigned
mailing list