Timeline for The scope of \newcommand is the entire page
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot | replaced http://stackapps.com/ with https://stackapps.com/ | |
| Jan 20, 2014 at 8:55 | history | edited | Ilmari Karonen | CC BY-SA 3.0 | added 529 characters in body |
| Jan 18, 2014 at 22:42 | comment | added | Davide Cervone | Javascript doesn't have access to the clipboard (for security reasons), so that is not likely to be a solution. There are some Flash-based kludges, but in general, browsers prevent javascript frmo modifying the clipboard. | |
| Jan 18, 2014 at 17:36 | comment | added | Bill Dubuque | Thanks! Even something more primitive such as saving to the clipboard would be helpful. The goal is to guarantee that one will not lose much work even if the browser crashes (which is very far from true for the SE draft saving feature) | |
| Jan 18, 2014 at 17:11 | comment | added | Ilmari Karonen | It might be possible using LocalStorage, although if Chrome crashes badly enough, that might not be perfectly safe either. I've never actually used LocalStorage before, but I could take a look into it. I'd also have to find some way to keep it from fighting with the SE builtin autosave feature, though. | |
| Jan 18, 2014 at 17:05 | comment | added | Bill Dubuque | I highly doubt it will ever happen. David claims it is a bug in Chrome tckled by MathJax. So the only hope is a workaround. Surely it must be very easy to implement a halfway decent autosave feature in SOUP, right? This would be the best thing since sliced bread. It would save many Chrome users countless hours of lost work. | |
| Jan 18, 2014 at 16:49 | comment | added | Ilmari Karonen | I agree. I can't really fix it without knowing why it happens, though, and I don't think anyone's really figured that out yet. (If someone has, please do tell me.) | |
| Jan 18, 2014 at 16:47 | comment | added | Bill Dubuque | Alas, the SE "autosave" feature is a kludge that works only rarely to recover from Chrome crashes. Any heavy use of MathJax + Chrome causes frequent Chrome crashses, making MathJax essentially unusable on Chrome. It's been this way for many years now. If it cannot be fixed, it would be really, really great to have some workaround, if that is not too much trouble to implement. This is by far the worst software problem I've encountered in a few decades of heavy software use. It's a shame that it has gone on this long. You can see many complaints about it in old meta posts. | |
| Jan 18, 2014 at 16:04 | comment | added | Ilmari Karonen | @Bill: The SE editor is already supposed to autosave posts, although only every 45 seconds. Of course, the real problem here is MathJax crashing Chrome, which presumably counts as a bug in both MathJax and Chrome. FWIW, I suspect things may have improved somewhat -- I use both Firefox and Chrome, and do recall experiencing poor rendering and slowdowns during editing (if not outright crashes) on the latter in the past, but not so much recently (except on the Android version of Chrome, which does get bogged down by lots of math). | |
| Jan 18, 2014 at 15:56 | comment | added | Bill Dubuque | Is it possible that SOUP could implement some sort of autosave feature to prevent loss of work due to frequent Chrome + MathJax crashes? The problem is so severe that I don't even dare to use MathJax with Chrome any more (except for trivial answers), having already lost countless hours of work due to such crashes. | |
| Jan 18, 2014 at 14:29 | history | edited | Ilmari Karonen | CC BY-SA 3.0 | added 5 characters in body |
| Jan 18, 2014 at 14:24 | history | answered | Ilmari Karonen | CC BY-SA 3.0 |