Many people have some sort of reset stylesheet, that turns on a border
for every div or every element. The 'perfect' version of this idea can
get very complex, but something as simple as setting a border on all
divs can often show you where something is stretching or floating where
you were not
: Monday, September 01, 2008 9:57 AM
Subject: RE: [WSG] Figures out issues. Standards for troubleshooting css
Many people have some sort of reset stylesheet, that turns on a border for
every div or every element. The 'perfect' version of this idea can get very
complex, but something as simple
For problems with box alignment, I know I usually turn on background colors
to clearly see the size and position of the boxes the browser is using.
Or is that a newbie answer?
On Sat, Aug 30, 2008 at 11:32 PM, Michael Horowitz
[EMAIL PROTECTED] wrote:
Just figured out my recent issues.
Actually that helped me with my image problem. It let me know the issue
was with how I was defining my background image when it worked with a
background color.
The hardest thing about learning a new language is learning its
troubleshooting techniques.
Michael Horowitz
Your Computer
That's so true. Just figuring out how to reliably display debugging data in
a new language can often take awhile. But there are a host of
troubleshooting principles that can be applied almost universally.
I've found it almost universally applicable to keep simplifying the problem
until you get to
Fred Ballard wrote:
For problems with box alignment, I know I usually turn on
background colors to clearly see the size and position of the boxes
the browser is using.
Or is that a newbie answer?
Definitely not a newbie method. Setting backgrounds is one of the
quickest ways to check
My first steps are of course make sure things validate. Beyond that I don't
have any standard steps besides really using google. Any good lists of
generic steps people do when troubleshooting CSS issues.
One URL: http://getfirebug.com/
Regards,
Rimantas
--
http://rimantas.com/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Gunlaug Sørtun
Sent: 31 August 2008 19:56
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Figures out issues. Standards for troubleshooting css
Fred Ballard wrote:
For problems with box alignment, I know I usually
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Michael Horowitz
Sent: Sunday, August 31, 2008 10:23 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Figures out issues. Standards for troubleshooting css
Actually that helped me with my image
:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
Behalf Of Michael Horowitz
Sent: Sunday, August 31, 2008 10:23 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Figures out issues. Standards for troubleshooting css
Actually that helped me with my image
Setting backgrounds is one of the quickest ways to check line-ups
while designing and troubleshooting.
Another technique I use daily is to invalidate CSS rules instead of
commenting them out during troubleshooting.
I second these techniques. I use bg colours as well and invalidate CSS
by
Just figured out my recent issues. Nothing really special for the
resolution.
Brings up a newbie question is standard steps people use for
troubleshooting.
My first steps are of course make sure things validate. Beyond that I
don't have any standard steps besides really using google. Any
12 matches
Mail list logo