4 ms·

I would fix the FF bugs ASAP. You'll have to do it eventually so put that at the top of your to-do list. The fixes probably aren't that hard. Thanks to fireb

by imp 19y ago

I would fix the FF bugs ASAP. You'll have to do it eventually so put that at the top of your to-do list. The fixes probably aren't that hard. Thanks to firebug you could probably pin-point the bugs really fast. It's probably better to put off the launch for a few days to avoid making a really bad impression to potential users.

jkush 19y ago
See here: http://www.w3schools.com/browsers/browsers_stats.asp http://www.w3schools.com/browsers/browsers_stats.asp What you can take from this is while being IE compatible only will give you about 58% of users, you can see that FF is growing steadily and will probably catch up someday in the not too distant future. It also depends on what kind of web app this is. If it's something for younger people, or people more technology inclined, the FF visits may be a lot higher than the graph suggests.
dawie 19y ago
Easier said that done. My app relies heavily on AJAX and has lots of Javascript...
- jkush 19y ago
  Did you use a library such as open rico or something based on prototype? If not, consider porting your existing code to use them as those libraries have solved many of the complexities of writing cross browser AJAX code.
- imp 19y ago
  I feel for you. When I wrote my first AJAX program, there was a lot of javascript controlling the UI. It was almost complete before I looked at it in IE for the first time. Two days and 10,000 alert boxes later I had it working. It's a necessary evil. No one enjoys it, but if you don't make the fixes you'll prevent a lot of people (including myself, a FF user) from ever even trying your website. If I try it once and it completely breaks, I'm never going to come back. If there are one or two non-critical features that are creating all of the bugs, then perhaps remove them initially and add them once you've fixed the compatibility bugs.
- imp 19y ago
  Also, if you don't have this book yet, get it now. It lists all javascript and css methods and which versions of which browsers support them. I relied on it heavily when writing/debugging my web app user interface. http://www.amazon.com/Dynamic-HTML-Definitive-Reference-Html/dp/0596527403/ref=pd_bbs_sr_1/103-3913841-7071807?ie=UTF8&s=books&qid=1177690841&sr=8-1 http://www.amazon.com/Dynamic-HTML-Definitive-Reference-Html/dp/0596527403/ref=pd_bbs_sr_1/103-3913841-7071807?ie=UTF8&s=books&qid=1177690841&sr=8-1

by imp 19y ago

jkush 19y ago

See here: http://www.w3schools.com/browsers/browsers_stats.asp http://www.w3schools.com/browsers/browsers_stats.asp What you can take from this is while being IE compatible only will give you about 58% of users, you can see that FF is growing steadily and will probably catch up someday in the not too distant future. It also depends on what kind of web app this is. If it's something for younger people, or people more technology inclined, the FF visits may be a lot higher than the graph suggests.

dawie 19y ago

Easier said that done. My app relies heavily on AJAX and has lots of Javascript...

jkush 19y ago
Did you use a library such as open rico or something based on prototype? If not, consider porting your existing code to use them as those libraries have solved many of the complexities of writing cross browser AJAX code.
imp 19y ago
I feel for you. When I wrote my first AJAX program, there was a lot of javascript controlling the UI. It was almost complete before I looked at it in IE for the first time. Two days and 10,000 alert boxes later I had it working. It's a necessary evil. No one enjoys it, but if you don't make the fixes you'll prevent a lot of people (including myself, a FF user) from ever even trying your website. If I try it once and it completely breaks, I'm never going to come back. If there are one or two non-critical features that are creating all of the bugs, then perhaps remove them initially and add them once you've fixed the compatibility bugs.
imp 19y ago
Also, if you don't have this book yet, get it now. It lists all javascript and css methods and which versions of which browsers support them. I relied on it heavily when writing/debugging my web app user interface. http://www.amazon.com/Dynamic-HTML-Definitive-Reference-Html/dp/0596527403/ref=pd_bbs_sr_1/103-3913841-7071807?ie=UTF8&s=books&qid=1177690841&sr=8-1 http://www.amazon.com/Dynamic-HTML-Definitive-Reference-Html/dp/0596527403/ref=pd_bbs_sr_1/103-3913841-7071807?ie=UTF8&s=books&qid=1177690841&sr=8-1