VisualEditor: Link input widget should suggest section links
OpenPublic

Description

When I edited an internal link and pasted in Work_breakdown_structure#Terminal_element as the new link target, the link editor widget thought that it was a new page, because it didn't understand that the # referenced an anchor within that page.

However, that was just a harmless warning - it did work. So I am classifying this as minor severity, because it is merely an incorrect warning message that could confuse editors.


Version: unspecified
Severity: enhancement

bzimport set Reference to bz50881.
Greenrd created this task.Via LegacyJul 7 2013, 5:05 AM
Jdforrester-WMF added a comment.Via ConduitJul 10 2013, 4:51 PM
  • The link inspector needs to understand that if Foo exists, linking to Foo#Bar isn't a red link
  • Ideally the link inspector should have introspection of articles' sections so that it can suggest which headings to link to
  • This should also work for naked (local) section links - i.e., linking to just #Bar on the local page.
Jdforrester-WMF added a comment.Via ConduitJul 10 2013, 4:52 PM
  • Bug 51118 has been marked as a duplicate of this bug. ***
Thryduulf added a comment.Via ConduitJul 10 2013, 5:12 PM

When reporting the duplicate bug (sorry, this one didn't come up in my search) I wondered whether this was related to Bug 33094

Jdforrester-WMF added a comment.Via ConduitJul 11 2013, 4:52 AM

(In reply to comment #3)

When reporting the duplicate bug (sorry, this one didn't come up in my
search)

Don't worry, it's my fault for not triaging earlier. :-)

I wondered whether this was related to Bug 33094

I don't believe so (though we should get that fixed soon too, of course).

Jdforrester-WMF added a comment.Via ConduitJul 11 2013, 5:23 AM
  • Bug 51121 has been marked as a duplicate of this bug. ***
Thryduulf added a comment.Via ConduitJul 11 2013, 7:08 AM

Worth noting here the comments on bug 50945 about cases where display text != link text (piped links)

John_Broughton added a comment.Via ConduitJul 16 2013, 4:20 PM

This isn't just a display problem, and it is NOT an enhancement - it's a real defect because editors are unlikely to take the time - as I did - to figure out how to make section links work.

Here's what happens now: The editor finds an article to link to (good UI; much better than the wikitext editor); then he/she starts typing the section link (#whatever). The link name turns red (that's the display issue), and it doesn't suggest section names (that would be a really slick enhancement; if you do this well, people are going to love you). Instead, when the editor is done typing the section information, one of four things can happen:

  • The editor presses Enter/Return (per the user guide), and the section information is REMOVED by VE. That is clearly a defect in the software.
  • The editor presses the close icon (<) (per the user guide), and the section information is REMOVED by VE. That is clearly a defect in the software.
  • The editor clicks somewhere else on the page, and the section information is REMOVED by VE. That is clearly a defect in the software.
  • The editor clicks on the area ABOVE the input box, the area containing the word "Hyperlink", and VE is happy, and saves the section information. (I'm going to add that to the user guide, but that wouldn't do nearly as much good as changing, in the software, what happens in the first three situations, above.
Keegan added a comment.Via ConduitJul 17 2013, 2:51 AM
  • Bug 51445 has been marked as a duplicate of this bug. ***
Elitre added a comment.Via ConduitAug 5 2013, 9:55 PM

The suggestion of the sections that can be linked are also requested at it.wp.

John_Broughton added a comment.Via ConduitAug 6 2013, 8:46 PM

The VE software has changed (at least a week ago, maybe longer) for this issue. Now pressing [Return] does not remove the "#Whatever" text that the user typed, for the section link. So this bug is now primarily a display issue.

(In reply to comment #7)

This isn't just a display problem, and it is NOT an enhancement - it's a real
defect because editors are unlikely to take the time - as I did - to figure
out
how to make section links work.

Here's what happens now: The editor finds an article to link to (good UI;
much
better than the wikitext editor); then he/she starts typing the section link
(#whatever). The link name turns red (that's the display issue), and it
doesn't
suggest section names (that would be a really slick enhancement; if you do
this
well, people are going to love you). Instead, when the editor is done typing
the section information, one of four things can happen:

  • The editor presses Enter/Return (per the user guide), and the section information is REMOVED by VE. That is clearly a defect in the software.
  • The editor presses the close icon (<) (per the user guide), and the section information is REMOVED by VE. That is clearly a defect in the software.
  • The editor clicks somewhere else on the page, and the section information is REMOVED by VE. That is clearly a defect in the software.
  • The editor clicks on the area ABOVE the input box, the area containing the word "Hyperlink", and VE is happy, and saves the section information. (I'm going to add that to the user guide, but that wouldn't do nearly as much good as changing, in the software, what happens in the first three situations, above.
Elitre added a comment.Via ConduitAug 22 2013, 11:23 AM

John reports today that "It used to be possible, in VE, to link to another section of a page (say, Bank#History). Now, when section information is added, in the Link/Hyperlink dialog box, VE just deletes it when the user presses [return] or exits (in any way) that dialog box."

Thryduulf added a comment.Via ConduitAug 26 2013, 2:34 PM

(In reply to comment #11)

John reports today that "It used to be possible, in VE, to link to another
section of a page (say, Bank#History). Now, when section information is
added,
in the Link/Hyperlink dialog box, VE just deletes it when the user presses
[return] or exits (in any way) that dialog box."

Noting for posterity that that was bug 53219, which has now been fixed.

Jdforrester-WMF added a comment.Via ConduitMay 30 2014, 2:34 AM
  • Bug 61428 has been marked as a duplicate of this bug. ***
Jdforrester-WMF moved this task to Backlog on the VisualEditor workboard.Via WebNov 24 2014, 1:29 AM
Jdforrester-WMF lowered the priority of this task from "High" to "Low".Via WebJan 15 2015, 12:36 AM
Jdforrester-WMF set Security to None.
Mattflaschen removed a subscriber: Mattflaschen.Via WebJan 15 2015, 5:37 AM

Add Comment

Column Prototype
This is a very early prototype of a persistent column. It is not expected to work yet, and leaving it open will activate other new features which will break things. Press "\" (backslash) on your keyboard to close it now.