Page MenuHomePhorge

Make an IE CSS hack pass W3C CSS validator
ClosedPublic

Authored by aklapper on Mar 24 2025, 11:11.
Tags
None
Referenced Files
F3954827: D25917.1746457629.diff
Sun, May 4, 15:07
F3905356: D25917.1746321047.diff
Sat, May 3, 01:10
F3851326: D25917.1746117662.diff
Wed, Apr 30, 16:41
F3847212: D25917.1746105935.diff
Wed, Apr 30, 13:25
F3833953: D25917.1746082484.diff
Wed, Apr 30, 06:54
F3803332: D25917.1745982843.diff
Tue, Apr 29, 03:14
F3800481: D25917.1745933606.diff
Mon, Apr 28, 13:33
F3776906: D25917.1745865091.diff
Sun, Apr 27, 18:31

Details

Summary
Test Plan

Paste core.pkg.css into https://jigsaw.w3.org/css-validator/. Optionally, find some ancient Internet Explorer version and run it (I did not).

Diff Detail

Repository
rP Phorge
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Thanks for this patch! Kind reminder: if you touched CSS or JavaScript, please remember to also run this:

./bin/celerity map

⚙️ Thanks! Bip bop I'm a bot - helping for T15209

I've tested in my console:

body {
  margin-top: 100px \9;
}

And:

body {
  margin-top: 100px\9;
}

And both are completely ignored in my browser webs Firefox and Chromium. So this is not supposed to cause regressions there.

This revision is now accepted and ready to land.Mon, Apr 28, 08:13