On Mon, 18 Feb 2013 13:13:30 -0300, George Ludwig <georgelud...@gmail.com>
wrote:
In CSS, the problem is almost always that some unexpected rule is being
followed rather than the one you think. I've found Chrome to be an
invaluable tool in locating the exact source of the CSS rule being
followed, plus it enables you to play around with
changing the value.
Firefox add-on Firebug is also very good for this.
By the way, the original message in this thread seems to be a
misunderstanding of how CSS works. Tapestry doesn't change CSS files: it
just includes them. Unless your CSS files aren't included or included in
the wrong order, this isn't a Tapestry issue at all.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
