
Signature
[ do not email me copies of your followups ]
g o r d o n + n e w s @ b a l d e r 1 3 . s e
>> You must be using the wrong browser, Gordon!
>
> In that case, suggest a different one! I'm happy with the user
> empowerment I currently get from Firefox,
[1] Depends on the exact technique they are using, but
generally - disabling JS stops most rubbish, while if they
are both clever (and stupid) enough to *generate* the pages
with JS, you need to do a direct call for the script(s) and
hunt though the source. The deployer can then obfuscate it,
of course, but ..we are already in the realm of 'not easy'.
OTOH, I thought FF (or Mozilla based browsers in general)
had options for the end user to configure..
- Where new windows appear (floating/tabbed window).
- Whether scripts can close windows.
>..and it also happens to run
> on all of the platforms I commonly use (Linux on 4 different cpu
> architectures + Solaris).
Yes. If I did not have to have such close knowledge of
IE, a Moz. based browser would be my choice. My choice
would probably be Mozilla itself.
There was a conversation recently that suggested that FF
in particualr was not especially good for
- *applet* developers, in that it only offers access to
the Java console if their is a broken applet in the page.
- web-developers, because it similarly hides (AFAIR) options
to get at the page source, and the JS console..
FF is more geared to the end user, than either Java (applet)
developers or web-application developers specifically.
> And yes, I'm fully aware that these things can be circumvented.
Just pointing out that is is often simpler than it looks.

Signature
Andrew Thompson
physci.org 1point1c.org javasaver.com lensescapes.com athompson.info
"The Generals gave thanks, as the other ranks held back the enemy tanks
..for a while."
Pink Floyd 'When The Tigers Broke Free'
Oliver Wong - 09 Sep 2005 15:37 GMT
> There was a conversation recently that suggested that FF
> in particualr was not especially good for
> - *applet* developers, in that it only offers access to
> the Java console if their is a broken applet in the page.
> - web-developers, because it similarly hides (AFAIR) options
> to get at the page source, and the JS console..
I've never had a problem access the page source from FireFox. In fact,
FF even offers syntax highlighting of the HTML source code, while IE shows
the sourcecode in Notepad (which obviously doesn't do syntax highlighting).
On the other hand, FF is particularly bad when working with XML and XSLT
documents, as I think FF caches everything in such a way so that even when
you modify the underlying files and force the browser to refresh (via F5 or
the menu), it still stubbornly uses the cached version.
So when I'm writing XML/XSLT documents, I develop with IE, and then only
at the end check if it still looks right in FireFox.
- Oliver