Website changes/updates

[Unknown W. Brackets]

The Web Developer Extension for Firefox.  Microsoft developed a similar 
toolbar for IE (forget the name but it's like Web Developer Toolbar for IE.)

Also, obviously, following standards bodies, setting your Content-Type 
to application/xhtml+xml for testing, validating your html/xhtml/css.

And any browser allows you to disable JavaScript entirely.  Using 
JavaScript debuggers such as WebKit's and Firebug (IE has none afaik.)

Nightlies of WebKit and Firefox/SeaMonkey, as well as the latest Opera, 
also help here for checking against latest specs.

This really isn't as hard as most people make it.  So many want to use 
hacks (e.g. exploiting bugs in implementations) because that can't make 
anything work on all browsers.  In my experience, there is always a 
right way - a clean way that will always work.

I've been doing this for quite some years, written a lot of CSS, XHTML, 
and JavaScript, and it's been a long time since I've done anything that 
wouldn't work in tomorrow's browsers.  People act like it's not true, 
but if you follow the standards (and possibly add an additional IE-only 
stylesheet using conditional comments) you really won't have these problems.

Sorry for ranting.  Sometimes I'm really disappointed with my industry 
(generalizing; many I've worked with are very good.)

-[Unknown]


BCS wrote:
> Walter Bright wrote:
> 
>> 4) clever stuff that'll break with the next browser update
> 
> Does anyone (Mozilla, IE, etc.) maintain a "breakable browser" that is 
> intended to checking what a web page would look like without some things 
> working?