Margin Auto w/ a fixed width
Absolute 50% w/ negative margins
Text-align center parent w/ inline-block display on children
If it was sarcasm, disregard my stupidity.
Margin Auto w/ a fixed width
Absolute 50% w/ negative margins
Text-align center parent w/ inline-block display on children
If it was sarcasm, disregard my stupidity.
The whole thing feels like you are stretching something beyond what it was intended to be used for.
Things like element positioning should be so so simple that if you search about it, you get nothing back because no one had a problem to ask for solutions.
Although I must say I'm not mocking CSS in particular, most web technologies feel this way because they were designed many years ago for a web that was supposed to have simple 'documents' like an article, text and paragraphs and today each component of it is expected to do a lot more.
It's not getting all that much better either because each new version and improvement is building on top of the previous decisions, etc...
> most web technologies feel this way
Most technologies you don't know feel this way. And the reason—you don't know them. > It's not getting all that much better either because each
> new version and improvement is building on top of the
> previous decisions
In this case: no.Container has fixed dimensions in my example, but it does not matter in this case.
Btw. your approach is exactly same that we had 10 years ago but with CSS table behavior faking rather than table tag.
Yay. Progress.
It's like variables (yeah I know, LESS / SASS ...).
Yes, totally intuitive and logical solutions all of them.
If you have w3c Stockholm syndrome, that is.
E.g "Just absolute 50% it with a negative margin" (oh, yes, and you would have to know the width beforehand).
>If it was sarcasm, disregard my stupidity.
It's not the stupidity, is the willingness to put up with BS convoluted inelegant workarounds for lack of basic, bread and butter, features.
If you value elegant APIs, KISS and DSLs, you should run screaming in the opposite direction in all those three, horrible, horrible, techniques.
W3C first came up with their (broken) model, and then they kludged solutions to use cases with it, instead of starting from the use cases first. That's why we have had the tables before and the need for the flexbox and grid layout now.
You're right, there is a willingness to put up with it. Mainly because I understand how these solutions work, how to debug them, and make everything nice and peachy. Do I wish things were better? Of course! Who wouldn't?