Direct Transfer GUI: Improvement needed when the user has no Read permission on /

What
A user without Read permission on "/" has no way to enter the direct path or Document UUID to the folderish document where he has Write permission in Direct Transfer GUI on the Drive client side

How to reproduce

• create a server or use nightly.nuxeo.com
• create a simple user testwrr/testwrr (not a member of members) with no right on "/"
• create a Folder and assign the Write permission to testwrr e.g. in WebUI
  https://nightly.nuxeo.com/nuxeo/ui/#!/browse/default-domain/workspaces/Start%20Creating%20Your%20Cont/For%20teswrr
• launch Drive and target the server and allow Direct Transfer and login as testwrr
• see that you have no way to enter the path /default-domain/workspaces/Start%20Creating%20Your%20Cont/For%20teswrr although you have Write permission there

Notice that this is not limited to "/". If the user has no Read permission on an ancestor of the target directory, the same issue arise for the unreadable sub-branch

Short Term "workaround" as an improvement
Being able to give a full path to Drive client in the Direct Transfer GUI either as a "new root document" under which one can select other documents OR directly as a target folderish document (as is done in WebUI with a browser)