>>
|
3e9573.jpg
Tropical Posh
3e9573
>>/questdis/130607
>>/questdis/130622
Thanks for the feedback! I'd like you to be as picky as you can heh.
>it doesn't always keep track of which update you're on
Yeah, it doesn't detect scrolling when dragging the scrollbar or when using mousewheel autoscroll mode. I'm trying to fix it so that any scrolling would be detected, but using IntersectionObserver sentinels is some next-level fuckery, so that could take a while heh.
>if you don't click off of the menu
- Fixed so that navigation doesn't work while a dropdown menu is selected
That was definitely a bug.
>the text in the second post still wraps
I intentionally kept this original layout behavior. But as you say, it's quite annoying due to the inconsistency that it causes.
- Changed so that reply elements never wrap to the right of the OP post
There is another similar default layout inconsistency where a post's text sometimes wraps underneath the image instead of wrapping to the right.
- Changed so that text always wraps to the right of the images of update posts.
I accomplished this by forcing update posts to always stretch 100% of screen width. I tried many other approaches, but nothing managed to work perfectly. I should probably add some settings to control these layout changes in case they would be undesirable to the user.
>unexpand the images
- Fixed.
I've had this implemented but removed it because it was problematic if the user manually expanded the images where the extension would immediately contract them again. Well, I suppose I'll just enable it again.
>"last 50 posts"
This is intentional. The extension needs to "see" the whole thread to be able to properly determine which posts are updates. Also, if it doesn't see the whole thread, then it cannot navigate to the start, the position cannot be stored / restored properly, and various other bugs would be had. I could, in theory, make the extension load the whole thread in the background when opening the "last 50/100 posts" view, but that would kinda defeat the purpose. I have added a note in the documentation tho.
>mixed quests
How does one differentiate between author comments and text-only updates? ;)
>sometimes in sequence view navigating to the next update brings you to the middle
I think I know what the problem might be and I think I fixed it, but not sure. Does it happen when there are .gif files contained in the sequence?
>a setting to automatically go to the latest update when viewing active quests
You mean, when opening any thread in the /quest/ board, that stored position should be ignored, and instead always start at the last update?
I'm not sure if that would be useful. I mean, when opening a thread, the first thing you're usually interested in is whether there have been new updates, right? If it always displayed the last update, then you'd have to rely on your memory, rather than the extension showing you if and how many new updates there have been posted. I've added an explanation about this in the documentation. But do explain why this would help you.
>an ability to go to the next thread
I'd love to add this, but I don't have a database of which threads belong to which quests. As of this moment, the site hosts 3940 quest threads, so it would be quite a job to organize them all.
|