News for hackers. Stuff that matters.
Re:A Harsh CSS Environment for Testing Widgets by jcsalterego on Sunday June 07, 2009 @01:49PM (#646105)
Neat idea -- and here I thought it was just going to redirect to http://www.microsoft.com/windows/internet-explorer/ D:
Re:A Harsh CSS Environment for Testing Widgets by jack7890 on Sunday June 07, 2009 @02:54PM (#646178)
Incredibly useful. We just released a widget, and will definitely be using this to make sure its bullet-proof.
Re:A Harsh CSS Environment for Testing Widgets by bjclark on Sunday June 07, 2009 @03:06PM (#646198)
We just launched a widget too and were surprised by how hard it was to stop the cascade. This is pretty useful.
Re:A Harsh CSS Environment for Testing Widgets by fortunado on Sunday June 07, 2009 @06:03PM (#646433)
This is probably the fifth "Why didn't I think of that?" thing I've seen on HN today. Really cool stuff... bookmarking it in case I need it one day.
Re:A Harsh CSS Environment for Testing Widgets by r7000 on Sunday June 07, 2009 @06:45PM (#646485)
The exact thought I had. Having just released a widget this weekend I had thought about how to give it a thorough test. I'll just try it out on some different blog platforms was my sad idea. Then, this today. Thank you very much Gabriel!
Re:A Harsh CSS Environment for Testing Widgets by Tichy on Sunday June 07, 2009 @07:06PM (#646504)
Is the "!important" thing part of a coming arms race? Must admit I have not encountered it before. Can they be combined (!important !important or !veryimportant,...), and in a couple of months all style sheets have to be !supermegamegaimportant?
Re:A Harsh CSS Environment for Testing Widgets by Hexstream on Sunday June 07, 2009 @08:25PM (#646590)
This is one of those times I pat myself on the back for reading the specifications directly ;P

http://www.w3.org/TR/CSS21/cascade.html#important-rules

Re:A Harsh CSS Environment for Testing Widgets by Tichy on Monday June 08, 2009 @05:12AM (#647028)
This feature sucks. So once stylehseet authors start using !important everywhere, users will have to use !important everywhere, too. Then in the next incarnation they will introduce a !moreImportant property to overide the !important setting of the user stylesheet.