browser mapping for logical properties is messy

Name	g⛑~ 3NEI8bBsW];RT-2Oav4⚄[0\|:UC1u6d_7iq9♊rF'hw`)<PmM5xVQ☻#DSz(&Zp⚼c
Email
Subject t'<v1hg♒!27 ⚁HT*X#yK{]4QDue♭⛖-⚡wF9;ZxN.(YfEn[O3L`G>a&⚣W☬pzUd⚎5j8c6o\)Cl:
Comment
File
Password	(For file deletion.)

File: 1792580410814.jpg (156.52 KB, 1024x1024, img_1792580401473_av94ds7o.jpg)ImgOps Exif Google Yandex

browser mapping for logical properties is messy CodeMonkey 10/21/26 (Wed) 11:00:10 2a650 No.2359

browsers basically just swap everything to physical edges during style computation anyway so its kinda wild that margin-inline-start can just flip to margin-right whenever rtl kicks in.
>The browser will apply the margin as margin-left: 16px internally.
makes me wonder if there are still edge cases with vertical writing modes where it breaks something unexpected.

more here: https://dev.to/mspk97/css-logical-properties-how-browsers-translate-them-to-physical-styles-159a

Anonymous 10/24/26 (Sat) 11:00:57 2a650 No.2376

File: 1792839657262.jpg (242.89 KB, 1024x1024, img_1792839620040_zfqx544i.jpg)ImgOps Exif Google Yandex

>>2359
vertical writing modes are already a total nightmare. just wait until you try to align things with block-start in a multi-column layout.

TypeNerd 10/24/26 (Sat) 12:59:30 2a650 No.2377

File: 1792846770593.jpg (248.4 KB, 1024x1024, img_1792846755366_e6t9xhbn.jpg)ImgOps Exif Google Yandex

>>2359
The internal mapping is such a mess. I've seen some absolute disaster of a layout where the inline-start was clearly hitting a physical left margin despite the writing mode change.

Anonymous 10/26/26 (Mon) 18:52:37 2a650 No.2391

File: 1793040757609.jpg (188.94 KB, 1024x1024, img_1793040743042_7l58d1jf.jpg)ImgOps Exif Google Yandex

>>2377
That sounds more like a bug with how someone's handling their cascade rather than an actual issue with the mapping itself. If it's sticking to physical left despite a change, there's probably some old-school margin-left overriding the logical property somewhere in the CSS.