Page MenuHomePhabricator

Design: Determine WWT Exit Functionality
Closed, ResolvedPublic

Description

As a PM, I want to know if we should update the current methods of exiting WWT, so that we can implement an intuitive user experience.

Acceptance Criteria:
• Evaluate the current methods of exiting via information bar (click on "x" when the bar is loaded or when there is an API error), and determine if it's sensical to implement an "x" in the loading state as well
• Evaluate the current mode of exiting WWT via toggle off (i.e. the user can exit by clicking on the "Who Wrote That?" link below tools, if WWT is already enabled/toggled on). Will this be confusing to users who may experience longer load times, so they then click on the link (assuming it will reload or refresh the tool, rather than toggling it off?).

Event Timeline

ifried created this task.Fri, Aug 23, 7:50 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFri, Aug 23, 7:50 PM
ifried assigned this task to Prtksxna.Mon, Aug 26, 2:36 AM

Yeah, so the current loading state doesn't have the close icon. If we suspect that the tool can be in this mode longer than a few seconds we should definitely add a close button here as well.


Once the tool is active, my understanding was that the page wont behave like it usually does, that is, the links in the article itself will stop working, and that the tool wont work for images, tables, templates etc. Also, in this mode the focus is just on the content, so the idea was to dim the rest of the chrome and even the content that we don't have information for. One can exit the tool by either clicking on the close icon in the bar or by clicking on the dimmed chrome (not the dimmed content, since I suspect they might click on it by accident).

If we do want to do it through the tools sidebar as well we need to make sure that the text of the link changes based on the state. So, normally it could be Who Wrote That, and when its switched on—Close Who Wrote That.

ifried added a comment.EditedWed, Aug 28, 12:10 AM

Yup, there may be times when the tool does not immediately load (and takes a few seconds). In that case, I agree that the information bar should have an exit "x" for the loading state. I have created a ticket to implement this behavior: T231359.

Regarding the chrome idea: I'm inclined to think that we shouldn't dim the rest of the chrome. Users may prefer to fully access all links and content on the page, without having to first disable Who Wrote That. What do you think? We can discuss it tomorrow in our meeting.

Regarding the messaging under tools: Is it necessary or useful to have more than one way to exit WWT? On the one hand, it may be intuitive for certain users to have both modes. Also, I'm not sure if this is ever technically possible/true, but could there ever be cases when the information bar is acting up, so the sidebar exit would be more helpful to users? On the other hand, we can perhaps simplify the implementation by focusing on one exit method rather than two, if we deem only one actually necessary. Curious to hear your thoughts on this as well.

If we do implement toggle off via the sidebar: I agree that we should change the messaging, as you suggested. It provides some helpful information to the users, which they may not otherwise know.

Regarding the chrome idea: I'm inclined to think that we shouldn't dim the rest of the chrome. Users may prefer to fully access all links and content on the page, without having to first disable Who Wrote That. What do you think? We can discuss it tomorrow in our meeting.

Per our discussion, let us not dim the chrome and let it be accessible as usual.

Regarding the messaging under tools: Is it necessary or useful to have more than one way to exit WWT? On the one hand, it may be intuitive for certain users to have both modes. Also, I'm not sure if this is ever technically possible/true, but could there ever be cases when the information bar is acting up, so the sidebar exit would be more helpful to users? On the other hand, we can perhaps simplify the implementation by focusing on one exit method rather than two, if we deem only one actually necessary. Curious to hear your thoughts on this as well.

Let us take another look at this after T231612: WWT: Determine WWT Access Location?

ifried moved this task from Backlog to Done on the Who-Wrote-That board.Tue, Sep 10, 8:38 PM
ifried closed this task as Resolved.Tue, Sep 17, 3:55 PM