[GH-ISSUE #1161] Remove bob@example.com values from fields in Floccus #775

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

Originally created by @sunjam on GitHub (May 12, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1161

Which version of floccus are you using?

latest

Sync method

{"label"=>"Nextcloud Bookmarks"}

Which browser are you using? In case you are using the Android App, specify the Android version please.

latest

Which version of Nextcloud Bookmarks are you using? (if relevant)

latest

Which version of Nextcloud? (if relevant)

latest

What kind of WebDAV server are you using? (if relevant)

Please remove the values bob@example.com
Instead, just fail the entire account creation process or force the person to edit their entry as opposed to creating a fake account for the user.

Thank you for considering!

Describe the Bug

bob@example.com is not a real account, but is being treated as real entires

Expected Behavior

bob@example.com might be visible to explain what a user must enter, but please do not actually treat this as literal text entries in the fields.
Users should be required to properly fill out those fields just as I'm being required to fill out this field right now in reporting this issue

To Reproduce

  1. Create an account.
  2. Type anything you want
  3. Don't press the save button
  4. bob@example.com

Debug log provided

  • I have provided a debug log file
Originally created by @sunjam on GitHub (May 12, 2022). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1161 ### Which version of floccus are you using? latest ### Sync method {"label"=>"Nextcloud Bookmarks"} ### Which browser are you using? In case you are using the Android App, specify the Android version please. latest ### Which version of Nextcloud Bookmarks are you using? (if relevant) latest ### Which version of Nextcloud? (if relevant) latest ### What kind of WebDAV server are you using? (if relevant) Please remove the values bob@example.com Instead, just fail the entire account creation process or force the person to edit their entry as opposed to creating a fake account for the user. Thank you for considering! ### Describe the Bug bob@example.com is not a real account, but is being treated as real entires ### Expected Behavior bob@example.com might be visible to explain what a user must enter, but please do not actually treat this as literal text entries in the fields. Users should be required to properly fill out those fields just as I'm being required to fill out this field right now in reporting this issue ### To Reproduce 1. Create an account. 2. Type anything you want 3. Don't press the save button 4. bob@example.com ### Debug log provided - [ ] I have provided a debug log file
kerem 2026-02-25 22:38:04 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@marcelklehr commented on GitHub (May 13, 2022):

Thank you for the feedback! This is fixed in latest code, just not released yet

<!-- gh-comment-id:1125869676 --> @marcelklehr commented on GitHub (May 13, 2022): Thank you for the feedback! This is fixed in latest code, just not released yet
Author
Owner

@github-actions[bot] commented on GitHub (May 14, 2023):

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:1546784514 --> @github-actions[bot] commented on GitHub (May 14, 2023): 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#775
No description provided.