Define user experience for when it is ambiguous what page permalink should lead you to
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	ppelberg
	Mar 24 2022, 12:56 AM

Description

This task involves the work with defining what people will experience when the permalink they click tap refers to a content that does not currently exist on one page.

Cases

This section contains the list of cases we will need to design the user experience for...

Case #1: Topic/Comment was deleted
Description: A topic/comment was deleted at some point in between the URL for said comment being generated and someone clicking/tapping on it.

Do we tell you the comment was deleted and NOT show it?
Do we tell you the comment was deleted and show it?
Do we tell you the comment was deleted and expose a way for you to view the comment if you explicitly decide to?

Case #2: Topic/Comment was duplicated
Description: A topic/comment was duplicated/moved at some point in between the URL for said comment being generated and someone clicking/tapping on it.

Requirements

Open Questions

1. What are all of the cases we need to consider as part of this task?

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Open		None	T302011 Introduce permalinks on wikitext talk pages
		Open		None	T304579 Define user experience for when it is ambiguous what page permalink should lead you to

Event Timeline

ppelberg created this task.Mar 24 2022, 12:56 AM

ppelberg moved this task from Backlog to Triaged on the DiscussionTools board.

ppelberg updated the task description. (Show Details)Mar 24 2022, 12:58 AM

@matmarex: can you think of any cases that are missing from the task description? If so, can you please add them?

ppelberg mentioned this in T304647: Better communicate to people when a comment has been deleted after reloading the page.Mar 29 2022, 11:23 PM

How about "topic is renamed"?

Define user experience for when it is ambiguous what page permalink should lead you toOpen, Needs TriagePublicActions