gorgeous-airport-54386
06/20/2022, 11:51 AM* { margin: 0; padding: 0; }
!"
"oh, i have to put space between my paragraphs, manually"
"but not the paragraphs in forms, only text paragraphs"gorgeous-airport-54386
06/20/2022, 11:52 AMcss
*:should-have(margin: 0) {
margin: 0;
}
tall-dinner-62086
06/20/2022, 12:07 PMcss
* {
margin:0 !important;
}
let God sort'em outrefined-waiter-90422
06/20/2022, 1:00 PMmysterious-toddler-20573
06/20/2022, 1:24 PMbrainy-ice-92385
06/20/2022, 8:36 PM<rant>
CSS was based on basic-ass ubiquitous graphic design language of 1993 and that language has always used the ubiquitous language of manual typesetting, where centering something meant putting blank metal blocks into a machine to manually balance both sides of each line.
CSS's first objective has never been to get you what you want, or something that looks cool, it's always been to give you something that doesn't look like ass with zero work. (like Deniz's ideal)
And from there they've just tacked on attempts at better layout systems like flex and grid while doing insane mental gymnastics to maintain that 600 year old typesetting functionality underneath.
It's analogous to the history of C++ in that way, which is not a compliment.
The original responsive design argument was a philosopher pointing out that CSS's fundamental building blocks make no sense in the actual medium on which it paints, and providing hacks to get closer to that medium.
It's due for the same argument 1cg uses for htmx: what if we went back and made a more reasonable choice from the get-go
</rant>
calm-ice-23682
06/21/2022, 9:29 AMbrainy-ice-92385
06/21/2022, 3:41 PMjust center it dammit
mysterious-toddler-20573
06/21/2022, 4:01 PMmysterious-toddler-20573
06/21/2022, 9:52 PMtall-dinner-62086
06/22/2022, 2:57 PMmysterious-toddler-20573
06/22/2022, 3:05 PMmysterious-toddler-20573
06/22/2022, 3:06 PMmysterious-toddler-20573
06/22/2022, 3:06 PMmysterious-toddler-20573
06/22/2022, 3:06 PMtall-dinner-62086
06/22/2022, 3:14 PMgorgeous-airport-54386
06/22/2022, 3:15 PMgorgeous-airport-54386
06/22/2022, 3:15 PMgorgeous-ghost-95789
06/25/2022, 8:36 PMgorgeous-airport-54386
06/27/2022, 6:56 PMgorgeous-airport-54386
06/27/2022, 6:57 PM--accent
variable
>
> If the user has dark theme enabled system-wide, two things might happen depending on how we implement things:
>
> - The dark theme accent color in missing.css overrides the custom accent
> - The custom accent is used with missing.css’s dark theme colors, probably ugly and bad contrast
>
> Neither of these are desirable. The only way to prevent this would be to force everyone to specify their custom colors in both light and dark theme – even if they don’t want to support dark theme.
>
> As for solutions:
>
> - One option is to require a class to enable automatic theme switching. This will work and not be much trouble, but makes missing.css less valuable as a classless CSS library.
>
> Thoughts?refined-waiter-90422
06/27/2022, 7:09 PM--accent
its reasonable to have them also change --accent-dark
or calc()
something reasonablerefined-waiter-90422
06/27/2022, 7:10 PMjolly-kite-167
06/27/2022, 7:16 PMgorgeous-airport-54386
06/27/2022, 10:43 PMswift-translator-13366
06/28/2022, 7:17 PMgorgeous-airport-54386
06/28/2022, 10:04 PMgorgeous-airport-54386
06/29/2022, 10:13 PMmysterious-toddler-20573
06/29/2022, 10:13 PMmysterious-toddler-20573
06/29/2022, 10:16 PMthe
branch?