Re: css name clashes

[Pete Helgren <Pete@xxxxxxxxxx>]

Excellent!  Just what I was looking for!  Wow! You can turn off an 
applied style just by clicking next to it! Very nice.

Thanks for that pointer.


Jeffrey Day wrote:
> 1. Right click on the element on the page -> Select 'Inspect Element'
> 2. That should create a split frame on the bottom of the screen.
> 3. On the right hand section, it will show the CSS rules applied to that element, and if any have been superceded, they will be crossed out/striked through.
>
>   
> > > > On 11/6/2008 at 10:39 AM, in message <49130F9B.8010000@xxxxxxxxxx>, Pete Helgren <Pete@xxxxxxxxxx> wrote:
> > > >         
> Not that this is a Firebug tutorial forum, but, how do I see this in 
> Firebug?  I use Firebug because I am a Firefox user but I can't see 
> anything useful on the css tab. It shows me the css for a selected file, 
> but I can't get a view that shows me where an element is defined 
> multiple times across files in a single page.
>
> Got a quick pointer?
>
> Pete
>
>
> Jeffrey Day wrote:
>   
> > 2 great tools for this are: Stylizer or Firefox/Firebug
> >
> >
> >   
> >     
> > > > > On 11/6/2008 at 9:59 AM, in message <4913064F.7030503@xxxxxxxxxx>, Pete Helgren <Pete@xxxxxxxxxx> wrote:
> > > > >         
> > > > >           
> > 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
> >   
> >