Permalink edit field is too small for long domains

[9808us]

have a look at this screenshot

The edit field is too small

[karmatosed]

If there was a way to check if an input box was under a certain width and then force it to go to the next line, I think this would be a good solution. If that's not case maybe we could explore putting the URL and save on a different line to the title Permalink. I would love to have a more adaptive solution though if possible.

[karmatosed]

[ edit ] in testing this is still an issue, I thought it wasn't. Let's get this wrapping around when longer if possible. I am removing design feedback as this is my suggestion:

This design though is a sticky plaster not a longer term solution. We should iterate and review this going forward.

[DeveloperWil]

Hovering over the block title to change the permalink is very unintuitive. Pretty much all of my clients when I created a staging site with Gutenberg installed asked me why the new editor doesn't allow them to edit the permalink.

They didn't realize the needed to hover over the block title. It's not very obvious. I had to Google it myself when I first used the new editor.

Bring back the old static permalink at the top of the page or have some option to display/hide it in the UI

[georgestephanis]

It gets even worse on smaller screens.

[georgestephanis]

I wonder if the easiest answer would be to right-align the permalink and just cut off the path leading to the input field more willingly to avoid shrinking the field.

[earnjam]

One thing to keep in mind here is a permalink structure that doesn't have postname last. Probably rare, but still possible.

Example of that on an iPhone 5 sized screen

I wonder if on smaller screens we could only show the input field to edit the slug when editing, then go back to the full permalink on save.

[earnjam]

Along the lines of what @georgestephanis suggested, we could solve the original issue reported here with a larger or fixed min-width on the input field (currently 10%) and a justify-content: flex-end on the container span for the full permalink.

Not positive about IE support for justify-content though, so would have to test that a bit.

[DeveloperWil]

Should the permalink be in the document properties area? It's not content so shouldn't really be in the block content area.

[mtias]

Should the permalink be in the document properties area? It's not content so shouldn't really be in the block content area.

Should be closed after #11874

[mtias]

Not wanting to remove this UI just yet, but it should be gone soon. Closing as the alternative placement in the document is in place.