[ 
https://issues.apache.org/jira/browse/JSPWIKI-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290543#comment-14290543
 ] 

David Vittor commented on JSPWIKI-867:
--------------------------------------

I've changed the Delete.jsp file to return the user to the main view page, as 
oppose to the info tab. Redirecting to the "Attach" tab is not easy as there is 
not direct URL way of doing this, at the moment, although this could be done 
with javascript.

However if you return to the "view" page (WikiContext.VIEW) then, the change to 
the attach tab is one less server request, and it's more user friendly. 

Note: This also change also affects when you delete pages, but I think it's a 
nicer user experience going to VIEW rather than INFO.

> Deleting attachments should retain focus on the Attach tab
> ----------------------------------------------------------
>
>                 Key: JSPWIKI-867
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-867
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Default template
>    Affects Versions: 2.10.2
>         Environment: This is using the "PlainVanilla" skin.
>            Reporter: Dave Koelmeyer
>            Priority: Minor
>              Labels: attachments
>
> Procedure to recreate the issue follows:
> Start off with an existing JSPWiki page containing a number of existing 
> attachments. Then, go to the "Attach" tab. Delete one existing attachment by 
> clicking on the "Delete" button, accepting the warning prompt that appears. 
> On successful deletion of the attachment, JSPWiki will then bounce you to the 
> "Info" tab, instead of retaining focus on the "Attach" tab. The net result is 
> the user then has to click back on the "Attach" tab to continue deleting 
> further attachments, repeating the procedure each time for each attachment to 
> be deleted.
> Alternately, checkboxes to select multiple attachments for deletion would be 
> another solution here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to