There are development plugins for both IE7 and FireFox that will do this. For IE, I use the IE Developer Toolbar but I found that it makes IE very slow and prone to crashing when it is enabled. I don't do much CSS debugging in FireFox but DOM Inspector does provide some help with CSS. I think there are better plugins for CSS debugging out there.

Matt

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Thursday, November 06, 2008 9:59 AM
To: Web Enabling the AS400 / iSeries
Subject: [WEB400] css name clashes

Anyone have a tool that detects css name clashes? I did some poking
around the web and couldn't find anything immediately useful.

What I have is a situation where a particular element isn't displaying
correctly on a page. The page was an agglomeration of several pages,
each of which had a fully functioning example when run separately. When
I added all these stand alone elements to a single page, a couple of
elements no longer display correctly.

I will use a process of elimination to figure out which .css files has
the conflict but it would be pretty handy to have something that would
read through a series of css references on a page and tell you if you
have definitions in more than one file that could cause conflicts.

Pete Helgren
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.