Post #2218806
2026-05-07 11:15 UTC
Replies (3)
-
@DLC@mstdn.social 2026-05-09 07:32
@SRAZKVT@tech.lgbt I don't think so either, but they belong in the client? Not per website… Let the website declare the layout it prefers: Use semantic tags: text text code … Desc See Desc See
-
@dillo@fosstodon.org 2026-05-09 15:44
@SRAZKVT@tech.lgbt @DLC@mstdn.social the problem with CSS is not so much in design of CSS itself but in the complexity of HTML which make each page have its own set of unique CSS rules. I agree with authors being able to suggest a set of styles, but those should be optional on the client. That way you can reliably set your own scheme for all the pages **and still be sure that it will reliably work**. This is also important for readability, not only for the aesthetics of the page.
-
@navi@social.vlhl.dev 2026-05-09 16:45
@SRAZKVT@tech.lgbt @DLC@mstdn.social @dillo@fosstodon.org i feel like the majority of things that need css for layout should be structually semantic instead e.g. it doesn't make sense that a navigation side/top bar is a div holding a unordered list, that can only show that it's actually supposed to be if the css is correct yea exists iirc, but i see people not using it often -- imo if we don't allow much css at all, it'll mean people can't hack around having proper structure