Collections not displaying on Add books page [Chrome]

DiscussieBug Collectors

Sluit je aan bij LibraryThing om te posten.

Collections not displaying on Add books page [Chrome]

1szarka
jun 11, 2021, 3:21 pm

Been seeing this bug for a few days now (?) on Chrome (but not on Brave). After adding a new item on the Add books page, the Collections don't display in the show quick edit dropdown for that item. Collections *have* been set properly on adding; they just don't display. Collections display properly for the other items on the page, and they also display for the newest item if the page is reloaded or loaded in another browser. So it seems specific to the code that's updating the DOM, not whatever generates the initial view of the page. Happy hunting!

2kristilabrie
Bewerkt: jun 13, 2021, 11:30 am

Good catch! I'm getting this across all my browsers (Chrome, FF, Safari).

For developers to reproduce:
1. Go to the "Add books" page using Chrome, Firefox, and/or Safari (I'm testing on my Mac OS Big Sur, 11.3)
2. Make sure you have at least one Collection checked in the "Add to collections" list.
3. Add any book from any data source. Book gets added to "Recently added" list on the page. (I added "The Smallest Girl in the Smallest Grade" to my Wishlist Collection.)
4. Click to "show quick edit" for that newly added book, and also another book already showing on the list, from another session.

Bug: Note that the "Collections" folder does not list the Collection/s for the book you just added, but it does show them for previously added books.

NB: Refreshing the page and clicking to "show quick edit" for the newly added book does show the Collections.

On Chrome: I'm also noting this warning when loading the page, not sure if related in any way: "DOM Found 10 elements with non-unique id #tagedit: (More info: https://goo.gl/9p2vKq)"

On FF: I'm noting this warning, unsure if related in any way: "unreachable code after return statement e9f2029e47b9644a7f36b851b9c38acf.js:940:215"

3conceptDawg
mrt 2, 2023, 3:07 pm

This looks to be fixed.