Closed Bug 643991 Opened 13 years ago Closed 13 years ago

properly handle UX when user navigates away from a shared page prior to error

Categories

(Cloud Services :: Share: Firefox Client, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: formerly-j-r-burke, Assigned: mixedpuppy)

References

Details

Attachments

(1 obsolete file)

In talking over use cases with Bryan, we came up with some error cases that have some problems given the current add-on implementation. How can the user recover if:

1) User navigates to another page and share of previous page ends up failing? Right now they will see an error, but after the error, the share panel is reset to the current page info and not the previous page that had the error.

2) If they close the tab while the share is still trying to complete?

This seems to indicate that the share data should be stored in a add-on global area indexed by URL, and not store the data on the tab.

Then, the error notification bar should displayed in whatever tab the user is currently viewing. If the "fix it" button is clicked, then focus on the tab that has the URL that failed, and if there is no tab with the right URL, pop a new tab to that URL. Make sure the share panel is open showing the error.
Assignee: nobody → mixedpuppy
Attached patch rel=shorturl patch (obsolete) — Splinter Review
Whiteboard: [needs test]
ignore patch, getting too trigger happy, thought I was on a different bug tab
Attachment #523455 - Attachment is obsolete: true
Whiteboard: [needs test]
(In reply to comment #0)
Just to clarify this a bit after talking with FF UX.

In either case, 1) or 2), the issue is that a person has lost the original tab or page they were sharing (by clicking on a link or closing the tab) and the share failed for some reason in between sharing and losing the tab/page.

Firefox doesn't currently have a central place where we could inform the user of an issue like this.  Once we inform the user we want to reopen the erroneous tab/page for the person to retry the share.

So for now we will just open the page which wasn't shared successfully in a background tab.  This avoids interrupting the person in whatever new task they were doing but does risk that they won't see the new tab opened.  

UX requested that we indicate on the tab (similar to how app tabs light up) that the background tab we've opened is an error in sharing.

The background tab can behave exactly as an share error using a notification bar to indicate the problem.
Summary: Edge cases with sharing: move away from per-tab share state → properly handle UX when user navigates away from a shared page prior to error
This was fixed as part of bug 644182 and landed in https://hg.mozilla.org/users/pweitershausen_mozilla.com/fx-share/rev/8a55957fb65e
Status: NEW → RESOLVED
Closed: 13 years ago
Depends on: 644182
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: