Now, in regard to the above issue, the Mozilla ActiveX Control is NOT the problem, the problem is the WB Internal Web Server.
Comments below as per the above thread examples.
The WB Internal Web Server does not send the correct content-type header for CSS style sheets, it sends text/html when it should send text/css.
As a result of this Firefox being more rigid rejects the stylesheet.
Look at the bill anton example in the above thread page 2, works for HTML but as PHP it fails, well actually it will fail as HTML also, but first some quick info...
When you are using the internal web server and preview a HTML file, the file is opened directly by the browser. WB uses file:// NOT http://.
thats fine, no problem. In this case FF will work, as it is opening the file locally.
However with a PHP file, preview WB will use the internal web server, and you would see something like http://localhost:89/~C/test/index.php. Now
the example will fail in Firefox, the content-type header is wrong.
So leave WB running, now start Firefox, point it to HTML example (above thread), you'll need something like:
http://localhost:89/~C/TEST/index.htm (~C is the drive, the rest is the local path/file).
Now you ARE using the WB Internal Web Server and NO Mozilla ActiveX control, notice the stylesheet failed, check Firefox error console!
As mentioned, here we see simple html with etxernal style sheet failing (albeit Firefox only).
Hope this makes sense, I could provide more detail, but since the above thread was available I took a shortcut.
If you download WGET for windows, you can simply use: wget -S http://localhost:89/~C/TEST/SOMEFILE.CSS, here you can see the header information that the browser would, the content-type is incorrectly shown as text/html it should show text/css.
Cheers all
