Pathbar issues

[Eugene Pankov]

Pathbar is a place of pain. It's a custom widget so it lacks context menu, lacks context menu and Ctrl-Arrow word navigation.
If user clicks the pathbar, it's 99% probability that he wants to enter path. Currently, he has to sit and keep left arrow pressed only to get a fully editable path textbox. Please remove the "half-editable-half-breadcrumb" behavior for the focused pathbar

[Jaap Broekhuizen (jaapz-b)]

I agree, the pathbar needs rethinking. It does not behave like you would think it would, not very intuitive. I think a simple way to fix al these problems is to make the breadcrumbs go away when you click on the editable part, so you can edit the whole path. We can use a normal text area for that. This makes it more logical and accesible, while keeping the niceness of the breadcrumbs.

Also related: bug #1086926

[Danielle Foré (danrabbit)]

Hey Jaap, my original intention was definitely not have a mixed button and entry. This is something that ammonkey did.

In my original mockup, the ">" graphic was supposedly to seamlessly replace the "/" char. In this way, you should be able to select all the text, click anywhere to edit it (once in edit mode), etc.

Since this is most likely not trivial to implement, I'd be +1 to having the pathbar simply change to a standard entry once in edit mode.

However, I would like to retain "home" as the beginning of the breadcrumb. Since Files doesn't offer a way of performing administrative actions (via polickity for example) anyways, I think the current behavior of starting at ~/ makes sense.

[fatalGlory (fatalglory)]

+1 for feature request. This one has always bugged me.