Ancestors

Written by Thomas Michael Semmler on 2024-12-19 at 12:42

Omg. I attempted to debug an issue in safari, where a position: fixed; element didn't correctly align to the viewports edge and I couldn't find out why, until I noticed that it is now relatively positioned to the next element with container: inline-size; on it.

Is this how it is supposed to be? This is only the case in safari

[#]safari #css #containerqueries #html #webdev

=> More informations about this toot | More toots from nachtfunke@indieweb.social

Written by Manuel Matuzović on 2024-12-19 at 12:58

@nachtfunke If you ask me it should be like that in all browsers because the property and value apply layout containment which creates a fixed positioning containing block. Or am I wrong @mia?

=> More informations about this toot | More toots from matuzo@front-end.social

Written by Mia (web luddite) on 2024-12-19 at 15:30

@matuzo @nachtfunke this was how the feature worked initially. We thought that was required for proper containment. But it's not! And browsers should hopefully all be removing that asap! (@jensimmons, @emilio)

=> More informations about this toot | More toots from mia@front-end.social

Written by Thomas Michael Semmler on 2024-12-20 at 11:55

@mia @matuzo @jensimmons @emilio just so I understand, Safari's behaviour here is the intended, correct way?

=> More informations about this toot | More toots from nachtfunke@indieweb.social

Toot

Written by Manuel Matuzović on 2024-12-20 at 12:22

@nachtfunke @mia @jensimmons @emilio use to be the intended behaviour but will change soon. Afaik it's already different in TP.

=> More informations about this toot | More toots from matuzo@front-end.social

Descendants

Written by Thomas Michael Semmler on 2024-12-20 at 12:26

@matuzo @mia @emilio @jensimmons alright, thank you! Makes sense.

=> More informations about this toot | More toots from nachtfunke@indieweb.social