Sent by Jan Brasna on 3 February 2006 03:03
> to open the HTML (actually .JSP) file, find the element in question, grab
> the class name, then open the associated CSS doc, search for the class name
> and finally make the change. (And of course, the requests are seldom so
> simple, which means the fixes tend to involve a lot more scrolling around
> inside a multi-thousand-line doc looking for a CSS value.)
You shlould have considered using something like Web Inspector
(<http://webkit.opendarwin.org/blog/?p=41>) (or DOM Inspector and many
other plugins).
> So my current consideration is to move the specific positioning information
> back into inline styling. Positioning that is repeated frequently on one
> page will be moved to the header (internal). And, naturally, globally-used
> styles will remain in the blessed external CSS docs.
Since I lose then the ability to cascade and inherit properties I'd go
with some .css files modularity. One can even have a .css for each
separate page or set of typical pages, but I'd avoid inline styling if
possible and reasonable.
--
Jan Brasna :: www.alphanumeric.cz | www.janbrasna.com | www.wdnews.net
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
