I don't think its entirely possible to have a website, look and feel exactly the same on every browser, on every OS... Its never been done with anything - software never looks or behaves the same way (unless its entire engine is ported over - ie. Games) Because OS's have their defining features, they strive to be different.
>From that, we cannot expect to ever be able to make a singular website in HTML, and CSS which will look identical on every OS and every Browser... The best shot we have to try is Browsercam, other than that, there really isn't much more possible to do... ----------------------------- Chris Stratford [EMAIL PROTECTED] www.neester.com ----------------------------- -----Original Message----- From: Justin French [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 4:12 PM To: [EMAIL PROTECTED] Subject: Re: [WSG] Programmer's Challenge [Virus checkedAU] On Tuesday, February 3, 2004, at 03:14 PM, Ryan Christie wrote: > I think that what was more in our minds was a browser that could > switch rendering engines on the fly in one window. For example, in the > famous FB.7 release, if you navigate to a website that has different > CSS styles available to be loaded, you can switch styles using an icon > that pops up in the lower left-hand corner (for example, > http://www.theward.net, or http://www.texturizer.net/firebird) ... If > there was an application out there that I could use to switch from > rendering engine to rendering engine, browser to browser ... I would > galdly pay over US$100 for the convienience. Wow -- a whole $100 for something that would save you endless hours of work??? Big spender! I just can't see it being possible, unless all browser manufacturers released the source code of their rendering engine (not a chance in the case of IE). Even if they did, there would still be inconsistencies due to the fact that the rendering engines aren't operating in their intended environment. What it seems you're asking for is a plug-in for something like Mozilla which can be set to badly render web pages with bugs (like IE's box model), emulating those rendering engines. Again, the problem here is that you aren't testing against the browser, you're testing against the plug-in's ability to emulate that browser's rendering engine. And it's not just the rendering engine that needs to be tested -- it's the UI (IE's lack of text sizing for px and pt fonts for example), and truckloads of underlying code modules (PNG, JavaScript, the list goes on). The absolute best possible scenario I can think of (and even then, I have no idea if it can be done) is if you loaded everything onto a Mac running OSX, Virtual PC (for the Windows browsers), an XWindows style emulator (for Linux GUI browsers), then came up with an AppleScript for your default browser (eg Safari) which opened up a new window in all installed browsers, using the URL of your current Safari window. You can then systematically look at all the open windows, click around a little, then close them when you're done. EVEN THEN, it's not perfect... you're not testing the windows & linux browsers in a perfect environment (Virtual PC & XWindows are emulators, not physical machines, and are extremely slow), and there's the fact that the Multiple IE thing isn't perfect at all. I'd never say never, but I will say 'dream on' :) Justin French ***************************************************** The discussion list for http://webstandardsgroup.org/ ***************************************************** ***************************************************** The discussion list for http://webstandardsgroup.org/ *****************************************************
