While using my new OS X app (available at http://boxen.math.washington.edu/home/iandrus/ ) I noticed that tab completion is broken because Sage parses the user agent as Mozilla/Mac instead of Safari/Mac. There seems to be two ways to handle this:
1. Change the UserAgent to fool Sage into thinking that it's Safari 2. Change UserAgent parsing to recognize SageBrowser (or whatever we call it) I have done #1, but I'm not sure how to do #2. Since the browser can also be used to view non-sage webpages it might make sense to identify as Safari (#1), but I wanted to know what other people think. Is there any advantage to changing the UserAgent parsing to recognize a different browser? The browser is based on Webkit, so it's essentially the same as Safari in terms of javascript/css support. Any feedback would be appreciated. In particular does it satisfy your use case William? I would really like to get something distributed by default for OS X, but have only sporadic times in which I can work on Sage right now. -Ivan Andrus -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
