On applying new link annotation, place cursor outside of the link
Open, NormalPublic

Description

Would it be possible to have the cursor default to outside the link, after inserting it?
Because: With the Current/updated behaviour, I have to add a [right-arrow] keypress, in order to keep typing, after entering a link. This is complicated, non-intuitive, and not consistent with other richtext editors (afaik).
It's especially a concern here, given the previous link continuation bug behaviour, where I'm accustomed to an erroneous display, and I've learned to ignore link text continuing past where it was meant to end (until I hit [enter] or otherwise trigger a re-render).


Current behaviour (post-update):

  • I type foo bar
  • [ctrl-k]test
  • [enter]
  • zow This results in

foo bar [[test zow]]


My desired behaviour: (identical to gmail, etc)

  • I type foo bar
  • [ctrl-k]test
  • [enter]
  • zow This results in

foo bar [[test]] zow

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 18 2015, 6:55 PM

The problem with this is that the cursor being outside the link means no context, so no feedback that the link was created and is going to the right place.

The problem with this is that the cursor being outside the link means no context, so no feedback that the link was created and is going to the right place.

The text would be blue/purple/red, so that's feedback that a link was created. The user would've established that it was going to the right place, whilst entering the link using the handydandy link inspector. :-)

Other websites with editing interfaces - Quora comes most readily to mind - don't provide a URL as feedback after making a link (in the sense of showing both the external link and the clickable text that leads to it), they just show the text that, when clicked, will lead somewhere. So leaving the cursor inside the link is counter to what editors experience elsewhere.

More importantly, people adding information to a Wikipedia page, using VE, can't (currently) make a link and then continue typing text, because what they type gets incorporated into the link. Rather, they have to use a right-arrow to escape the link, then start typing. That again is counter to what they experience in other websites with WYSIWYG editing - make a link, and when they keep typing, what they type is plain text.

The problem with this is that the cursor being outside the link means no context, so no feedback that the link was created and is going to the right place.

The text would be blue/purple/red, so that's feedback that a link was created.

Sure, though in testing we've seen that most users don't notice such things as obviously.

The user would've established that it was going to the right place, whilst entering the link using the handydandy link inspector. :-)

The point about after-action feedback is that it confirms for people who aren't as confident as you that it'd worked. :-)

Other websites with editing interfaces - Quora comes most readily to mind - don't provide a URL as feedback after making a link (in the sense of showing both the external link and the clickable text that leads to it), they just show the text that, when clicked, will lead somewhere. So leaving the cursor inside the link is counter to what editors experience elsewhere.

"Other people have terrible interfaces" is not the best argument, but I appreciate that providing a similar editing tool to that which users may have experience of elsewhere is not a bad thought.

More importantly, people adding information to a Wikipedia page, using VE, can't (currently) make a link and then continue typing text, because what they type gets incorporated into the link. Rather, they have to use a right-arrow to escape the link, then start typing. That again is counter to what they experience in other websites with WYSIWYG editing - make a link, and when they keep typing, what they type is plain text.

True. Remember that VisualEditor is not a WYSIWYG editor, despite the consistent disinformation spread by people outside the development team that that's the objective. :-)

Elitre added a subscriber: Elitre.Oct 23 2015, 4:49 PM

I don't understand why it's important to capture the user in link-label editing just so they know there is a link there. They would have just hit Insert, and the dialog would have gone away, so I would hope they would expect a link to be there. If they're not sure, they could always click back on it. Can you point to those user tests results, since they sound counter-intuitive?

Or, if it's really necessary to keep the user captured, could we at least let the space bar escape the link-label editing? The most common case, I think, would be to say "blah blah [[whatever]] and more text". Having the normal/common case work smoothly would be awesome, even if it makes other cases slightly more difficult.

Showing the link context after insertion means we don't need a confirmation stage in the link inspector. If we moved out of the link after insertion we'd need another way to tell the user which link they just inserted as its easy to make mistakes with autocomplete widgets.