No. No no no. Browsers LIE about their identities, forever and always. Whenever possible, check for *what makes the javascript quirky*, not what browser has the quirks. That way, if the bug in the browser gets fixed, your code works with past *and* future versions.
There already exists code in javascript to detect useragents, and display a warning. It takes a fraction of a second; there's no performance issue. It appears to be broken sometimes, and the warning is rather ugly. If you want to help, you can fix the existing code, and make a little CSS doohickey pop up at the bottom of the page and say "It looks like your browser isn't supported. Firefox is, and it's free!". Add a little button & some javascript so they can kill the warning and proceed as normal. Consider the Camino browser. For all intents and purposes, it's Firefox -- but it says that it's Camino, so certain webapps think it's not supported -- even though everything works exactly the same as Firefox. Idiotic. Do NOT change the server code to treat browsers different. On Sun, 22 Apr 2007, Timothy Clemans wrote: > >> Thanks for the report. We really need to add a visible warning when >> a person uses a non-supported browser. Implementing javascript >> tab completion in a web browser textarea was quite tricky -- Tom Boothby >> finally figured out how to do it -- the main trick involves figuring out >> where the cursor is by copying all text up to the cursor and seeing how >> many characters there are (!). > > I'll add that to my list. You just use the user-agent header. For > performance it would be best to all the stuff on the server side > instead of having javascript printing the message(s). It would also > probably be good to format the pages so that icons and stuff that do > not work in browser x do not show up in that browser. It used to be > that I could use a library computer to edit the cells of a worksheet > in slideshow or worksheet mode and just use the execute button, but > that no longer works thanks to the changes to the cell textareas. If > nothing else, the page should be completely viewable without any ugly > stuff showing. > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
