Is the idea that we should stick in inheritBackgroundColor whenever we encounter cases like the following? (I see the "get rid of this somehow" comment.) <head> <title></title> <style type="text/css"> body {background: #000000; color: #00ff00} </style> </head> <body> <SPAN STYLE='background:#fff6aa;'>link background dark( <SMALL><A HREF="/">link</A></SMALL> )</SPAN> <p> <SPAN STYLE='background:#fff6aa;'>link background light( <A HREF="/">link</A>) </SPAN> </body>
On Sat, Jan 24, 2009 at 05:43:52PM +0000, corvid wrote:
Is the idea that we should stick in inheritBackgroundColor whenever we encounter cases like the following? (I see the "get rid of this somehow" comment.)
The inheritBackgroundColor thing is a workaround for elements (<a>, <small> in the below case) that do not create a new dw widget. Things like: <span style="border: 2px solid black">hello</span> don't work at all. I'd like to see a general solution for this but have no idea yet. It's also somehow related to the CSS property "display" (http://www.w3.org/TR/CSS21/visuren.html#display-prop) which is not yet supported at all. But yes, as long as we stick with inheritBackgroundColor, we will need to add it whenever no dw widget is created. Cheers, Johannes
<head> <title></title> <style type="text/css"> body {background: #000000; color: #00ff00} </style> </head> <body> <SPAN STYLE='background:#fff6aa;'>link background dark( <SMALL><A HREF="/">link</A></SMALL> )</SPAN> <p> <SPAN STYLE='background:#fff6aa;'>link background light( <A HREF="/">link</A>) </SPAN> </body>
_______________________________________________ Dillo-dev mailing list Dillo-dev@dillo.org http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev
participants (2)
-
corvid＠lavabit.com -
Johannes.Hofmann＠gmx.de