I just straight up think short hand properties the way they are designed are a bad idea. I've been writing CSS for about 15 years at this point, and I still can't remember the order of any short hand, I have to look it up every time, so I just type it all out instead. At least then I know what I'm looking at when I look at the code next time 'round.
I'd rather see something like named parameters, e.g.:
So, I'm sitting down to create CSS ... what does the browser need to do first: margins on body ... which of them comes first as you scroll down: the top of the body ...
If you came from print publishing, and assume that the browser handles the gutter spacing with defaults then it might even be argued that the right margin should come next!
It's just something you have to learn, none of the options seem more logical to me.
Note I first wrote HTML using pico on a Sun workstation in ~1995; developing with the developments in web development probably causes one to develop strangely. Or, in other words, it's hard to take a fresh view when you've had to deal with IE5.
Maybe someone that looked at a clock or compass? TRBL matches 12o'clock, 3o'clock, 6o'clock, 9o'clock. It also matches N E S W going around the circle
I agree that I'm more familiar with left being first but then should it be LRTB or LTRB. LRTB is common to say. But many APIs take x,y first which would arguably be LT.
Basically I think you could justify almost any order
I disagree. We are inherently used to 2D coordinate systems being X, then Y.
I would instead have made the directional properties go “left, top, right, bottom” instead.