Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path is not taken from the suggestions when naming the folder first #1876

Open
shanks1337 opened this issue Dec 31, 2022 · 3 comments
Open

Comments

@shanks1337
Copy link

Path is not taken from the suggestions when naming the folder first

  1. When in web view -> Add folder -> Change folder name to "abc".

  2. If you now select the folder path and delete "abc", the suggestions are shown, but they are not taken over when you select them. When you tap on them, the suggestions simply disappear again without the path changing.

    App Version: 1.22.2
    Syncthing Version: v1.22.2
    Android Version: Android 13

@tomasz1986
Copy link
Contributor

tomasz1986 commented Dec 31, 2022

I have the same suggestion as in #1877 (comment). If the separate issue is to stay, it should probably be transferred to the main Syncthing repo because the problem affects the Web GUI in general (and not only when using the WebView through the app either as you can reproduce these problems when accessing the GUI through a Web browser too).

@shanks1337
Copy link
Author

I had the assumption that the path suggestions were android specific hence I posted it here. I'm new to github, Is there a way to move this issue or cross link it? I don't want to double post it and cause confusion.

@tomasz1986
Copy link
Contributor

The path suggestions are present in all OSs. The particular problem may be Android-specific but it's not app-specific (e.g. if you access Syncthing running on a different device remotely from Android using a browser like Chromium, you will still experience this problem), so that's why I think it belongs to the main Syncthing repo as something affecting the Web GUI in general. You don't need to do anything yourself, if needed one of the maintainers will transfer the issue there.

Please keep in mind though that not many people work on GUI-specific issues, so it may take a while for something like this one to get fixed (if ever), especially since this doesn't break any core functionality, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants