Vivvy said:
But this really isn't about my design choices. It's about using a browser that is ineffective. When I use firefox it can't access an unacceptable number of websites. I want a browser that will allow me to browse the entire internet, not just what mozilla browser developers think i should see. Firefox and it's proponents may force a standard, but the reality is that standard probably won't look like firefox...
It's clear you have a completely different perspective than I have, Vivvy. You keep talking about Firefox or IE "forcing" or "being" the "standard", when my perspective tells me that IE and Firefox attempt to CONFORM to the standards. They cannot BE the "standard" themselves.
Usually for practical reasons I tell people I work with "make sure it works in whatever browser the client uses" AND in IE for Windows, and then all other standard browsers next. IE 5 for Mac is a hopeless cause and generally should be ignored if possible.
There was a notion sprung a while back to do "object" detection and not "browser" detection, in an effort to decide which direction code should run. If you do "object" detection (ie: does this browser have "document.all", then use it, does this browser support "iframe" then use it, if this browser supports... etc).
You say things like
"not just what mozilla browser developers think i should see" and I can't figure out how that connects to anything. Moz developers aren't "limiting" choices. The only way I DO see "issues" is with the otherwise highly cool application development platform Moz uses called XUL. It's very nnice, but requires a Mozilla browser to make a website into an "application".
I can only suggest you consider viewing the WEB as something that wasn't invented for Internet Explorer to browse, and along came other browsers that weren't as compatible. The very perspective you're exposing creates the problems you're facing. Someone esigned those ASP pages poorly, and now they need to be redone. Javascript aside, HTML rendered output is pretty simple, and its almost ALWAYS bad html coding that causes cross-browser problems.
ALL my pages run in Firefox just fine... and I do LOADS of complex things in my pages. In one interface I created an effect where users selected "rows" by clicking on checkboxes. Those rows highlight with each checkbox by changing their stylesheet. Before I ever tried Firefox I made this feature, cognizant of standards. Firefox came along, and I decided to try it on Moz. Everything worked perfectly.
Vivvy said:
I'm surprised no one has picked up on the fact that i'm not using IE ...
Not sure how we would know unless you were browsing our websites.
What DO you use?
Currently, I use Internet Explorer, Firefox, Netscape, and Safari.
The only really problematic websites for Firefox and others, are those using ActiveX objects. It's ironic that Microsoft started out flirting with support for Netscape "plugins" before usurping the issue and even dismissing Java as a developer open standards option. Hats off for services like GotoMyPC that have still thrived in multiplatform environments while providing one of the best web enhancement services around.
~ Nexus