You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using the Link Dialogue, the link text will turn red as if the link is invalid if the link begins with a "#"
Since anchor links were introduced, this seems to be a case of left over outdated behavior or rather that the dialogue was not updated alongside it.
To Reproduce
Steps to reproduce the behavior:
Press CTRL+L on a page
Type a "#" and any other text
Expected behavior
The link text color should ideally not change to red so long as the syntax is valid
One suggestion I could make is displaying it in a slightly grayed color if the link target does not exist (much like the sort of 'ghost pages' in the side bar)
Additionally, in the case of "Prefer short link names for pages" being checked, the "#" should be probably be omitted from the resulting text.
The dialogue box also does not suggest any valid Headings or IDs to link to in the same way it suggests pages.
Describe the bug
When using the Link Dialogue, the link text will turn red as if the link is invalid if the link begins with a "#"
Since anchor links were introduced, this seems to be a case of left over outdated behavior or rather that the dialogue was not updated alongside it.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The link text color should ideally not change to red so long as the syntax is valid
One suggestion I could make is displaying it in a slightly grayed color if the link target does not exist (much like the sort of 'ghost pages' in the side bar)
Additionally, in the case of "Prefer short link names for pages" being checked, the "#" should be probably be omitted from the resulting text.
The dialogue box also does not suggest any valid Headings or IDs to link to in the same way it suggests pages.
Screenshots
Environment:
Additional context
N/a
The text was updated successfully, but these errors were encountered: