You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I go to a geeklist subscription with multiple updated items on the same page, it goes to the oldest update, and is not lined up properly. I think a better behaviour would be to always jump to the top subscription list item.
For example, if item 5 was updated first, but then item 1 and item 10 are updated, the subscription takes me to item 5 and isn't lined up right. I have to go up and then down to see all the updates. If it went to item 1 in that scenario instead, I could just go down through all the updates.
The text was updated successfully, but these errors were encountered:
That's a good idea, but it means fighting against BGG's linking system. You see, the link you click on in the subscriptions page links directly to a single item chosen by BGG.
My concern is that it will cause the browser jump around on the page, first showing BGG's choice, and then showing the extension's choice. Or even worse, doing the opposite, which would be much more frustrating.
Right you are...I was thinking you could just pull the anchor off the URL, but I hadn't looked at it. Probably the two approaches would either be to scroll up the appropriate number of items, or scroll to the top of the page and then scroll to the next item - either way, potentially distracting
When I go to a geeklist subscription with multiple updated items on the same page, it goes to the oldest update, and is not lined up properly. I think a better behaviour would be to always jump to the top subscription list item.
For example, if item 5 was updated first, but then item 1 and item 10 are updated, the subscription takes me to item 5 and isn't lined up right. I have to go up and then down to see all the updates. If it went to item 1 in that scenario instead, I could just go down through all the updates.
The text was updated successfully, but these errors were encountered: