Mats: in a caffeine-deprived binge, I’d apparently managed to put some old-school JavaScript-obscuring comments around my CSS. It’s the trailing ”//—>” that seems to be causing Firefox to complain; remove that leading double backslash (”//”), and you’ll be set. Sorry about that.
Veracon: Unnecessary in what sense? Compared to the old table-based way of doing things, I think an extra span is a small price to pay. Of course, your semantic mileage may vary.
Patrick: thanks for the Firefox 1.0.7 note. I’ll take a look at that, but I’m guessing there’s some weird pixel rounding error at play there.
Mark: Fair enough, and you’re obviously more than welcome to use that approach. I normally wouldn’t put any browser-specific hacks in my core stylesheet, but I thought it the best approach for the purposes of a quick write-up.
Ethan
Mats: in a caffeine-deprived binge, I’d apparently managed to put some old-school JavaScript-obscuring comments around my CSS. It’s the trailing ”//—>” that seems to be causing Firefox to complain; remove that leading double backslash (”//”), and you’ll be set. Sorry about that.
Veracon: Unnecessary in what sense? Compared to the old
table-based way of doing things, I think an extraspanis a small price to pay. Of course, your semantic mileage may vary.Patrick: thanks for the Firefox 1.0.7 note. I’ll take a look at that, but I’m guessing there’s some weird pixel rounding error at play there.
Mark: Fair enough, and you’re obviously more than welcome to use that approach. I normally wouldn’t put any browser-specific hacks in my core stylesheet, but I thought it the best approach for the purposes of a quick write-up.
Thanks for the feedback, all!