> 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/ -~----------~----~----~----~------~----~------~--~---
