https://bugzilla.wikimedia.org/show_bug.cgi?id=67086

--- Comment #5 from Trevor Parscal <[email protected]> ---
The link inspector has long been our most concentrated area of bugs. UX changes
are coming in response to user testing, and many bug fixes are on their way as
well - more are needed obviously.

1. There is no universal link creation process, as every application differs
here, but I believe we are not totally off base in our initial design. As
usually, we have to solve this problem with the most difficult constraints
imaginable. Users are meant to be able to successfully navigate through a 3x3
matrix of options: link existing text, change linked text, create new link
text; link to an internal page, a fragment on the existing page or an external
page; produce an explicitly labeled link, an automatically labeled link or an
unlabeled (external) link. We need to map out all the use cases and come up
with a process that covers this matrix elegantly.

2. User testing has confirmed that, even though pressing enter, escape and
clicking away all serve to apply and close, users want a button, and the back
button doesn't make sense to them. The new design will do away with the back
button. It will move the remove button to the bottom left and drop the
confusing icon in favor of a destructive button labeled "Remove". On the bottom
right will be a primary button labeled "Done", which will behave the same as
pressing enter, escape or clicking away.

3. We need to use the transaction staging system to update the selected content
dynamically as you type, making the link appear to be internal, external, red,
auto-numbered, auto-labeled, etc.

4. The bug you experienced needs to be addressed, and I will see if it is
resolved (or can be resolved) by my context and window refactoring work. The
whole system has suffered from having a narrow entry point with too many poorly
mapped forks in the road producing unreliable results with any given path at
any given time.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to