Closed
Bug 829492
Opened 12 years ago
Closed 7 years ago
[Calendar] No way to cancel calendar account setup.
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(tracking-b2g:+, ux-b2g:2.2, b2g18+)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
b2g18 | + | --- |
People
(Reporter: caseyyee.ca, Unassigned)
References
Details
(Whiteboard: ux-tracking [priority][p=13], )
Attachments
(2 files)
After entering credentials for new CalDav account pressing "save" brings you to a "Please wait while your account is being setup" progress screen.
There should be a way for the user to cancel-out of the setup with a back button. Currently the user will have to wait for a time-out or kill the app to do so.
Updated•12 years ago
|
blocking-b2g: tef? → -
tracking-b2g18:
--- → +
Updated•12 years ago
|
Whiteboard: interaction, ux-p1 → u=user c=calendar s=ux-most-wanted
Updated•12 years ago
|
Assignee: nobody → gaye
Comment 1•12 years ago
|
||
This is important for usability in our constrained-bandwidth target markets. Current implementation is a big papercut in the foyer of the Calendar app experience (setup). Seems relatively low LOE to resolve.
Comment 2•12 years ago
|
||
If LOE means level of effort, then I think I disagree. I tried to write a patch yesterday, but there are a couple of architectural issues that lightsofapollo brought up that I still need to think through...
https://github.com/mozilla-b2g/gaia/pull/8952
On the flip-side, if you were talking about LOE, the village in Estonia, I am in complete agreement. We won't need much of them to get resolution here ;).
Updated•12 years ago
|
Status: NEW → ASSIGNED
Updated•12 years ago
|
Whiteboard: u=user c=calendar s=ux-most-wanted → ux-tracking
Comment 3•11 years ago
|
||
Hi Mike - Did this make it into 1.2?
Updated•11 years ago
|
blocking-b2g: - → backlog
Updated•11 years ago
|
Assignee: gaye → nobody
Updated•11 years ago
|
Whiteboard: ux-tracking → ux-tracking [priority][p=13]
Updated•11 years ago
|
Assignee: nobody → evanxd
Comment 4•11 years ago
|
||
Hi Harly,
Could you give the UX spec for the "back button" on the "Please wait while your account is being setup" page?
Thanks. :)
Flags: needinfo?(hhsu)
Comment 5•11 years ago
|
||
Hi Evan,
Attached is the UX spec for canceling CalDav account setup.
Thanks
Flags: needinfo?(hhsu)
Comment 6•11 years ago
|
||
Hi Harly,
Got you.
It is very clear.
Thanks. :)
Updated•11 years ago
|
Target Milestone: --- → 1.4 S2 (28feb)
Comment 7•11 years ago
|
||
Hi Kevin,
I would like to get your feedback for the path,
then I will add the related tests.
Thanks. :)
Attachment #8382901 -
Flags: feedback?(kgrandon)
Comment 8•11 years ago
|
||
Comment on attachment 8382901 [details]
Pull request
As gaye has mentioned, the proper patch for a cancel button is extremely complex. We would need to delete local data, as well as abort in progress XHRs in lower level libraries.
For now I would instead recommend a `hide` button, which would just hide the screen and allow the calendar to still sync. I'm not sure if this is acceptable from a UX point of view though.
Attachment #8382901 -
Flags: feedback?(kgrandon)
Comment 9•11 years ago
|
||
Hi Kevin,
Got you.
I never know the delete local data things before here, learned.
To do that sounds not easy things, just like you said extremely complex.
Currently, I have no idea to deal with the low level libraries.
Do you just mean that it is extremely complex to do aborting the in progress XHR?
Or we also need to do many other things, for example, delete local data, and other things I don't know yet.
If we need to do many things to abort the XHRs, could you give me some tips for that? I would like to try to figure out that first.
Then we might cc UX guys for your suggestions.
Really thanks.
Comment 10•11 years ago
|
||
I don't know all of the details as I haven't thought of this too much, but I did read the conversation at: https://github.com/mozilla-b2g/gaia/pull/8952
I would recommend you, me, gareth, and james get on a vidyo call to figure out the best way forward here and share knowledge. Thanks!
Comment 11•11 years ago
|
||
Hi Kevin,
Thanks for the suggestions.
Before the meeting, I should learn and make sure something here.
I'm doing needinfo to James and Gareth.
Comment 12•11 years ago
|
||
Hi Gareth,
For this issue, I have a question.
In the https://github.com/mozilla-b2g/gaia/pull/8952 pull request,
why did just stop to do updating the patch on that time?
Did we meet some big problem is very hard to resolve, or some UX issues?
Flags: needinfo?(gaye)
Comment 14•11 years ago
|
||
Comment on attachment 8382901 [details]
Pull request
Hi all,
So how about we do this way https://github.com/mozilla-b2g/gaia/pull/16702/files#diff-dc01c7982a21f4e3a531d2c8574a05b5R154?
Please give me your feedback.
Thanks.
Attachment #8382901 -
Flags: feedback?(kgrandon)
Updated•11 years ago
|
Attachment #8382901 -
Flags: feedback?(gaye)
Updated•11 years ago
|
Attachment #8382901 -
Flags: feedback?(jlal)
Comment 15•11 years ago
|
||
I think I should say that could you guys give me some feedback here.
Thanks.
Comment 16•11 years ago
|
||
Comment on attachment 8382901 [details]
Pull request
It looks like James left some feedback on github which I generally agree with. If I can think of anything else I will leave a comment. Thanks!
Attachment #8382901 -
Flags: feedback?(kgrandon)
Updated•11 years ago
|
Attachment #8382901 -
Flags: feedback?(jlal)
Comment 17•11 years ago
|
||
Hi James,
For the id things in https://github.com/mozilla-b2g/gaia/pull/16702/files#diff-dc01c7982a21f4e3a531d2c8574a05b5R154,
I think we could generate the id from at the `getAccount` in https://github.com/mozilla-b2g/gaia/blob/master/apps/calendar/js/provider/caldav.js#L175 and return the id to the function caller.
Then we could cancel the xhr request by the id.
How do you think?
Flags: needinfo?(jlal)
Comment 18•11 years ago
|
||
Hi James,
Sorry, and one more thing.
Why do we need to use worker thread for the CalDAV things?
Does it do a lot of heavy computing?
Thanks.
Comment 19•11 years ago
|
||
Hi James,
For the Comment 17, the implementation is like here https://github.com/mozilla-b2g/gaia/pull/16702/files#diff-bc1a6a7ca2a79166302cb3fad1ff0358R181.
How do you think?
Thanks. :)
Updated•11 years ago
|
Attachment #8382901 -
Flags: feedback?(kgrandon)
Updated•11 years ago
|
Attachment #8382901 -
Flags: feedback?(jlal)
Comment 20•11 years ago
|
||
Comment on attachment 8382901 [details]
Pull request
Hi James,
Could you help me review the patch.
Thanks. :)
Evan
Attachment #8382901 -
Flags: feedback?(jlal) → review?(jlal)
Comment 21•11 years ago
|
||
Comment on attachment 8382901 [details]
Pull request
I am happy to provide feedback, but I think Gareth or James should do the full review as they have more experience looking into this. Thanks for sticking with the patch!
Attachment #8382901 -
Flags: feedback?(kgrandon) → feedback+
Comment 22•11 years ago
|
||
Hi Kevin,
Thanks for your feedback.
I already updated the patch for your comments.
Comment 23•11 years ago
|
||
Comment on attachment 8382901 [details]
Pull request
I want to work toward a place where the calendar backend and frontend are less tightly coupled. In its current state, this patch adds request id generation and knowledge of the caldav backend to our frontend webapp. We also need integration tests including (but not limited to) the cases where
- When we abort before we get the entire propfind response, all of the xhr requests should be aborted and no account data should be written to idb.
- When we don't abort, the cancel ui should disappear once we finish the calendar home request and before we begin calendar sync
It seems as if, in its current state, there are times at which the user could press the cancel button, but their accounts would still be setup. Also in https://github.com/mozilla-b2g/caldav/blob/master/lib/caldav/request/abstract.js#L59, if you abort the xhr request, will the callback that closes the xml parser be issued? If not, I think we could get bad state in the xml parser perhaps?
Like I mentioned above, this is a small feature, but there are a lot of ways that this could go wrong and confuse users.
Attachment #8382901 -
Flags: feedback?(gaye) → feedback-
Flags: needinfo?(jlal)
Comment 24•11 years ago
|
||
Comment 25•11 years ago
|
||
Hi Gareth,
Let us focus the patch first, then we could do the little feature in Comment 23.
To abort request,
how do you think we do that with this way at https://github.com/mozilla-b2g/gaia/pull/16702/files#r10612182?
Actually, I don't understand all of you comments on GitHub,
and I also left some comments for that.
As you said, it is not an easy bug.
Some complex and risky things might happen in the patch.
So how about that we could do the simple and clear way to fix this bug?
(like the https://github.com/evanxd/gaia/commit/eb1b126d71f32844ef32e04b59cf42f954dfa569 patch)
Or we might need to discuss the details of you idea with vidyo.
I really would like do this bug well.
How do you think?
Hope hear your response.
Thanks.
Flags: needinfo?(gaye)
Comment 26•11 years ago
|
||
update the Comment 25:
To abort request,
how do you think we do that with this way at https://github.com/mozilla-b2g/gaia/pull/16702/files#diff-bc1a6a7ca2a79166302cb3fad1ff0358R211?
Comment 27•11 years ago
|
||
Comment on attachment 8382901 [details]
Pull request
Hi Gareth,
I add RequestGroup at https://github.com/mozilla-b2g/gaia/pull/16702/files#diff-bc1a6a7ca2a79166302cb3fad1ff0358R22.
Could you give me the feedback?
Thanks.
Evan
Attachment #8382901 -
Flags: feedback- → feedback?(gaye)
Comment 28•11 years ago
|
||
(In reply to Gareth Aye [:gaye] from comment #23)
> Comment on attachment 8382901 [details]
> Pull request
>
> I want to work toward a place where the calendar backend and frontend are
> less tightly coupled. In its current state, this patch adds request id
> generation and knowledge of the caldav backend to our frontend webapp. We
> also need integration tests including (but not limited to) the cases where
>
> - When we abort before we get the entire propfind response, all of the xhr
> requests should be aborted and no account data should be written to idb.
> - When we don't abort, the cancel ui should disappear once we finish the
> calendar home request and before we begin calendar sync
>
> It seems as if, in its current state, there are times at which the user
> could press the cancel button, but their accounts would still be setup. Also
> in
> https://github.com/mozilla-b2g/caldav/blob/master/lib/caldav/request/
> abstract.js#L59, if you abort the xhr request, will the callback that closes
> the xml parser be issued? If not, I think we could get bad state in the xml
> parser perhaps?
>
Sorry, what is the xml parser closed by the callback?
> Like I mentioned above, this is a small feature, but there are a lot of ways
> that this could go wrong and confuse users.
Updated•11 years ago
|
Target Milestone: 1.4 S2 (28feb) → 1.4 S4 (28mar)
Updated•11 years ago
|
Target Milestone: 1.4 S4 (28mar) → ---
Updated•11 years ago
|
Assignee: evanxd → nobody
Comment 30•11 years ago
|
||
Comment on attachment 8382901 [details]
Pull request
:( I missed this when it was important clearing my requests up so I am better in the future
Attachment #8382901 -
Flags: review?(jlal)
Updated•10 years ago
|
Whiteboard: ux-tracking [priority][p=13] → ux-tracking [priority][p=13], ux-most-wanted
Updated•10 years ago
|
Blocks: 994991
ux-b2g: --- → 2.2
Whiteboard: ux-tracking [priority][p=13], ux-most-wanted → ux-tracking [priority][p=13], ux-most-wanted-nov2014
Updated•10 years ago
|
Whiteboard: ux-tracking [priority][p=13], ux-most-wanted-nov2014 → ux-tracking [priority][p=13], ux-most-wanted-nov2014, 2x-uxnom
Assignee | ||
Updated•10 years ago
|
blocking-b2g: backlog → ---
Comment 32•9 years ago
|
||
Harly - is this still needed? Are the specs still relevant and ready?
Flags: needinfo?(hhsu)
Whiteboard: ux-tracking [priority][p=13], ux-most-wanted-nov2014, 2x-uxnom → ux-tracking [priority][p=13],
Comment 33•9 years ago
|
||
The spec is ready; however, as gaye has mentioned, it seems that we need to do a lot of works for this to happen.
Flags: needinfo?(hhsu)
Updated•9 years ago
|
Flags: needinfo?(gaye)
Updated•9 years ago
|
Attachment #8382901 -
Flags: feedback?(gaye)
Comment 34•7 years ago
|
||
Firefox OS is not being worked on
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•