- Issue created by @charles belov
Very long paths and aliases cannot be displayed in full on the Add alias or Edit alias screens. This creates cognitive load (accessibility issue) and makes it harder to proofread (usability issue). It would be better if the full path and alias could be displayed, or at least as much real estate as is available be taken up by the entry fields.
Based on the add-alias-page examples, I'm guessing this is probably not a big issue for the System Path field, but fixing this for that field would prevent any possible issues that might occur. It is definitely an issue for the URL Alias field.
1. Login as someone with permission to add and edit aliases
2. Go to /admin/config/search/path/add
3. In the System Path field, paste /node/17722
4. In the URL alias field, paste /about-us/contact-us/your-regulated-and-emerging-mobility-comments-have-been-submitted-to-the-sfmta
Desired result option one, if feasible: The field expands to accommodate the full URL in the visible field, including increasing the number of visible rows and wrapping the text if necessary.
Desired result option two, if option one is not feasible: The field occupies the full width of the available page area. The System Path and URL Alias fields are moved down to a line by themselves to accommodate this.
Undesirable result: The text shrinks to accommodate the full URL in the visible field.
Actual result: The visible portion of the file name is truncated to the field width, as shown in the following screen print:
This is also an issue on the edit alias page. While the full URL alias does appear at the top of the page, it is not fully visible in the edit field where the user actually has to do the work.
Update styling for the Add alias and Edit alias screens as follows:
Implement a self-growing field area for the System Path and URL Alias fields if at all feasible. If that is not feasible, move the fields to a row by themselves (two separate rows) and expand both the System Path and URL Alias fields to take up the full width of the page.
Active
11.0 π₯
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Makes Drupal easier to use. Preferred over UX, D7UX, etc.