RE: [WSG] E649: The default scripting language must be specified for an intrinsic event:

2008-08-31 Thread Essential eBiz Solutions Ltd
Magento is great in practice, but I've found that the only big thing about it for my customers is the admin facilities. But for a designer it's a lot of hard work. I've seen some fantastic examples of what can be done with Magento and there have been some great features that use jQuery (by far the

Re: [WSG] Figures out issues. Standards for troubleshooting css

2008-08-31 Thread Fred Ballard
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.

Re: [WSG] Figures out issues. Standards for troubleshooting css

2008-08-31 Thread Michael Horowitz
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

Re: [WSG] Figures out issues. Standards for troubleshooting css

2008-08-31 Thread Fred Ballard
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

Re: [WSG] Figures out issues. Standards for troubleshooting css

2008-08-31 Thread Gunlaug Sørtun
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

Re: [WSG] Figures out issues. Standards for troubleshooting css

2008-08-31 Thread Rimantas Liubertas
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/

RE: [WSG] Figures out issues. Standards for troubleshooting css

2008-08-31 Thread Darren Lovelock
The web developer toolbar for firefox can help you to see block level elements, choose - outline outline block level elements. This can sometimes be a big help when sections are behaving oddly. Darren Lovelock Munky Online Web Design http://www.munkyonline.co.uk T: +44 (0)20-8816-8893

RE: [WSG] Figures out issues. Standards for troubleshooting css

2008-08-31 Thread Thierry Koblentz
-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

Re: [WSG] Figures out issues. Standards for troubleshooting css

2008-08-31 Thread huzairy rezuan
Yeah, FireBug really do its job pretty well. Just turn on the inspect menu, and hover it to the section of your page, you will see the box layout. I use it to find out which divs that cause a problem(width problem). On Mon, Sep 1, 2008 at 3:35 AM, Thierry Koblentz [EMAIL PROTECTED] wrote:

RE: [WSG] Figures out issues. Standards for troubleshooting css

2008-08-31 Thread Jens-Uwe Korff
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