I presume Firefox shares the plug-in architecture with Mozilla (which I
use) so you could get the developer's plug-in, which has indispensable
debugging and validation tools.
On Tuesday, February 8, 2005, at 08:50 AM, Alan Wolfe wrote:
Hey Ted,
�
As a user, firefox is the most awesome browser out there.� As a web
programmer, it's good that it's really stable and reliable�(it's sad
how many browsers really are) but it's got some downfalls too.
�
One downfall is that it's more strict about jtml and javascript syntax.
�
instead of being able to do:
formname.elementname.value='blah';
you have to do the standard syntax of:
document.forms['formname'].elements['elementname'].value='blah';
�
with setting the default value of a select you have to do this for the
option you want do be default:
<option value="some value" selected="true">Some Label
�
and other syntax is different too.� Luckily the required syntax of
firefox is the true, standardized syntax so if you stick to that
you're ok.
�
Another downfall is that it protects the user from malicious
javascript, and errors on the side of safety which means it neuters
what you can do with your javascript.
�
An example is that we have some javascript code to validate a text box
for a valid date value.��In our javascript code, onBlur, it checks the
box to see if it's valid and if not, displays an alert window�saying
"Invalid Date" and then when they click ok, puts the focus back in the
date box so they are required to fix it before continuing.
�
In Firefox, it wont let us keep the user "trapped" inside the date
box, it wont let us set the focus of the box back after OnBlur since
it doesnt know we arent doing something bad to the user (good policy
with all the junk pages out there).
�
great browser, but not so great from our pov sometimes :P
�
----- Original Message -----
From: Ted Wolfley
To: [email protected]
Sent: Tuesday, February 08, 2005 6:58 AM
Subject: Witango-Talk: Firefox 1.0
Hi,
�
We are having more and more clients accessing our web pages with
Firefox 1.0, is there any special Witango coding concerns that I
should be aware of?� I did notice on one of our web pages with a lot
of <select> statements that when I used the javascript function for
going back one page after submitting the form, all of the <select>
statements were not set to the default settings even�though they were
set to the default on submission.� This wasn't happening with IE.
�
Ted Wolfley
Database/Internet Programmer
The Ogden Group of Rochester
phone: (585) 321 1060 x23
fax: (585) 321 0043
[EMAIL PROTECTED]
www.ogdengroup.com
�
_______________________________________________________________________
_
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
