[GH-ISSUE #1493] Auto sync toggle does not stick #982

Closed
opened 2026-02-25 22:38:38 +03:00 by kerem · 7 comments
Owner

Originally created by @thatso on GitHub (Dec 22, 2023).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1493

Which version of floccus are you using?

5.0.5

Sync method

Nextcloud Bookmarks

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Android 13

Describe the Bug

As already mentioned by @kolinger here: if I switch on auto sync in the options, confirm with save, leave options and enter them again, the auto sync switch is displayed as off.

Expected Behavior

The switch state should display the real setting.

To Reproduce

As stated in the bug description.

Originally created by @thatso on GitHub (Dec 22, 2023). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1493 ### Which version of floccus are you using? 5.0.5 ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Android 13 ### Describe the Bug As already mentioned by @kolinger [here](https://github.com/floccusaddon/floccus/issues/1465#issuecomment-1853359616_): if I switch on auto sync in the options, confirm with `save`, leave options and enter them again, the auto sync switch is displayed as off. ### Expected Behavior The switch state should display the real setting. ### To Reproduce As stated in the bug description.
kerem 2026-02-25 22:38:38 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Dec 22, 2023):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

I look forward to working with you on this issue
Cheers 💙

<!-- gh-comment-id:1867884632 --> @github-actions[bot] commented on GitHub (Dec 22, 2023): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. I'm Marcel and I created floccus and have been maintaining it ever since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. Note also that GitHub is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. I look forward to working with you on this issue Cheers :blue_heart:
Author
Owner

@marcelklehr commented on GitHub (Dec 23, 2023):

Indeed, it's broken again :(

<!-- gh-comment-id:1868265661 --> @marcelklehr commented on GitHub (Dec 23, 2023): Indeed, it's broken again :(
Author
Owner

@kolinger commented on GitHub (Dec 23, 2023):

86a97ce246 works! Vue is confusing tho... why this isn't documented? They just talking about some v-model value, no input-value...

<!-- gh-comment-id:1868272035 --> @kolinger commented on GitHub (Dec 23, 2023): 86a97ce2466d485529a7164afc0ac1ee3710cf27 works! Vue is confusing tho... why this [isn't documented](https://vuetifyjs.com/en/api/v-switch/#links)? They just talking about some v-model value, no input-value...
Author
Owner

@marcelklehr commented on GitHub (Dec 23, 2023):

I'm not using vuetify v3 but vuetify v2 but yeah, the docs there aren't much more explicit either. Usually you will want to use v-model anyway, what I'm doing is a bit of a hack, because it's bad form to manipulate a components props from within.

<!-- gh-comment-id:1868272636 --> @marcelklehr commented on GitHub (Dec 23, 2023): I'm not using vuetify v3 but [vuetify v2](https://v2.vuetifyjs.com/en/api/v-switch/#props) but yeah, the docs there aren't much more explicit either. Usually you will want to use v-model anyway, what I'm doing is a bit of a hack, because it's bad form to manipulate a components props from within.
Author
Owner

@kolinger commented on GitHub (Dec 23, 2023):

Thanks! Correct documentation explains a lot of my confusion of where you get these non-existing attributes from. Since previous fix 0aa47fed2e with @change event isn't a thing in v3 also. The new Vuetify changed everything!

<!-- gh-comment-id:1868274202 --> @kolinger commented on GitHub (Dec 23, 2023): Thanks! Correct documentation explains a lot of my confusion of where you get these non-existing attributes from. Since previous fix 0aa47fed2e3210b848f571beb62e4ef78e7e206a with @change event isn't a thing in v3 also. The new Vuetify changed everything!
Author
Owner

@marcelklehr commented on GitHub (Dec 23, 2023):

@kolinger Also, note there's a difference between 'vue' and 'vuetify' ;)

<!-- gh-comment-id:1868308039 --> @marcelklehr commented on GitHub (Dec 23, 2023): @kolinger Also, note there's a difference between 'vue' and 'vuetify' ;)
Author
Owner

@github-actions[bot] commented on GitHub (Dec 23, 2024):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:2558682459 --> @github-actions[bot] commented on GitHub (Dec 23, 2024): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#982
No description provided.