Leading slash in link fields and views has different UX

Open on Drupal.org →

Created on 11 February 2015, over 9 years ago

Updated 3 July 2024, 2 months ago

Problem/Motivation

When adding/editing a node, you can define a path (alias) for it (e.g., about-us). In D8 HEAD, as in D7, you do this without a leading slash.
When adding/editing a Page Display for a View, you can define a path for it (e.g., admin/content/node). In D8 HEAD, as in D7 Views, you do this without a leading slash.
In 📌 Implement autocomplete UI for the link widget Fixed , the Link widget UI is changed such that when you then want to link to these paths in the value of a link field, you need to start with a leading slash. This is to disambiguate linking by path from linking by an autocompleted node title (node titles don't usually start with a slash).
This might confuse users.

Proposed resolution

Option 1:

This isn't a problem: defining a path is different from linking to it, so no UX problem.

Option 2:

This is a problem, so change the node and View forms to require a leading slash as well.

Option 3:

This is a problem, so change the Link widget to not require a leading slash. Doing so would mean that the autocompletion would keep giving you choices you're not interested in, so we should usability test whether that is a bigger problem.

Remaining tasks

Either share anecdotal opinions or conduct a usability test to determine which option to proceed with.

User interface changes

API changes

🐛 Bug report

Status

Active

Version

11.0 🔥

Component

Views →

Last updated about 11 hours ago

Maintained by
🇩🇪Germany @dawehner
🇺🇸United States @tim.plunkett
🇬🇧United Kingdom @damiankloip
🇺🇸United States @xjm
🇳🇱Netherlands @Lendude

Created by

🇺🇸United States effulgentsia

Live updates comments and jobs are added and updated live.

Usability
Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Needs subsystem maintainer review
It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.

Bug Smash Initiative

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 2 months ago →
🇳🇱Netherlands Lendude Amsterdam
Didn't realise this got closed, I don't think it should be.

#3065720: When creating a Page View in the wizard and setting a path with leading slash (/) the created View display ends up with a double-slash (//) → was about things going wrong if you added a leading slash, so we strip any leading slash now. But the problem here is that the rest of Drupal actually wants you to add a leading slash when you set a path (menu items, aliases), so the UX in Views is reversed from the rest of core. So this issue is about getting Views in line with other parts of core. And I don't think that has been addressed, so it shouldn't be closed.

The questions in the IS remain, are we ok with Views doing it in another way than the rest of core or do we want to get it in line.
Comment 2 months ago →
🇳🇿New Zealand quietone New Zealand

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024