Defect #1852
closed
Use regular POST (non-ajax) for wiki preview
0%
Description
I'm filing this as a bug because it has bitten me for the third time and I'm certainly not alone.
Currently the wiki preview is AJAXified, this makes it very easy to lose all your work in progress by performing one of the following actions by accident:
- Hit the back-button
- Middle click anywhere outside the textarea (middle-click means "load URL in copy-buffer" in most browser)
Commonly you'll spend quite some time in the edit/preview cycle before saving a new revision. Losing all changes to a single misclick is a very frustrating expirience.
I propose the following fixes:
- Replace the AJAX preview with a normal POST-preview or at least add the POST-preview as an option
- Use javascript to display a warning dialog when the back-button is pressed (Note: This does not prevent the middle-click accident)
Related issues
Updated by Alteran Ancient over 16 years ago
How about add some javascript to bring-up a verification message if the user attempts the following, in the belief that they could be doing-so by accident.
Updated by Jim Jones over 16 years ago
Alteran Ancient wrote:
How about add some javascript to bring-up a verification message if the user attempts the following, in the belief that they could be doing-so by accident.
If all possible user mistakes can be caught with javascript then I'm fine with that.
But I think at least the middle-click issue is hard to detect.
Frankly, there should just be a straight, non-AJAX preview. AJAX can be helpful and nice - but not in this case.
Updated by Paul Rivier over 16 years ago
Jim Jones wrote:
Frankly, there should just be a straight, non-AJAX preview. AJAX can be helpful and nice - but not in this case.
How is that related to the use of ajax ?
Updated by Jim Jones over 16 years ago
Paul Rivier wrote:
Jim Jones wrote:
Frankly, there should just be a straight, non-AJAX preview. AJAX can be helpful and nice - but not in this case.
How is that related to the use of ajax ?
Try it:
- Start editing a wiki-page in redmine
- Enter some characters
- Hit the preview-link
- Hit the browser back-button (or navigate away from that page by other means)
- Hit the browser forward-button
Result: All your editing is lost irrecoverably.
Counter-example:
- Go to any website that implements regular POST-preview, e.g.: http://moinmo.in/WikiSandBox
- Start editing that page
- Hit the preview-link
- Hit the browser back- and forward-buttons in any order you like
Result: There is no way to lose your edit-buffer after having pressed "Preview" at least once. Firefox even remembers it across browser crashes.
To clarify again: This is not cosmetics, it's a serious usability issue. Imagine deploying redmine to a non-technical audience (e.g. for company-wide use). Now imagine having to explain why your boss just lost half an hour of editing only because he hit the back-button by accident.
Ofcourse the same problem applies to the ticket editing and any other area where AJAX-preview is used as well. I think it's not as serious of a problem there because you don't normally go through the edit/preview cycle as often as with a wiki-page, thus accidents are less likely to happen. Nonetheless it would ofcourse be advisable to fix this problem across all of redmine, for consistency.
Updated by Péter Major over 15 years ago
Hi,
True, it's very hard to use the editor like this, but nothing happened since 9 months. :(
Any progress or something??
Updated by
Updated by Terence Mill about 14 years ago
Duplicate of Issue #2910.
Checkout Drafts plugin
Updated by Jean-Philippe Lang almost 14 years ago
- Subject changed from Wiki AJAX preview is a bad idea to Use regular POST (non-ajax) for wiki preview
- attachments would be uselessly uploaded are more than that, you'd lost your attachments selection
- you'd lost the current textarea position (can be really annoying when editing long text)
- slower previews
I think that a javascript warning when leaving the page without saving would be a good option.
Updated by Mischa The Evil almost 14 years ago
Jean-Philippe Lang wrote:
[...]
I think that a javascript warning when leaving the page without saving would be a good option.
I'd vote +1 for that solution to this persistent issue, seeing all the related issues.
Updated by Terence Mill almost 14 years ago
I think that a javascript warning when leaving the page without saving would be a good option.
+1
Updated by Jean-Philippe Lang almost 14 years ago
- Status changed from New to Closed
- Resolution set to Wont fix
Thanks for the feedback. I'm closing this in favor of #2910 planned for 1.2.0.