Scrolling jellypotatoe
-
In your first testing sandbox, I did notice a small jump when the image un loaded from the dom. I wonder if multiple images loading and unloading would cause the issue? Like, one unloads, causing another to load, causing another to unload, et cetera?
-
@RaceProUK said in Scrolling jellypotatoe:
I just managed to scroll a thread down by pushing the scroll wheel up.
"Natural" scrolling can DIAF
-
@Yamikuronue
It's possible. I figured out midway through sandbox #2 that the infiniscroll page size was larger than I thought, but I didn't really want to go back through another 100 posts at 10+ seconds per post to rebuild the test case with image loading. :p
-
@izzion Oops, I had it set at 50 posts per page. Just changed it to 20, and can repro every time.
-
Proposed fix: set page size to
Int32.MaxValue
-
@boomzilla, or someone else with a GH account they can access, can you please update the GH issue report with the fact that the replication case is confirmed sensitive to the "posts per page" setting?
-
@izzion Done
-
@izzion said in Scrolling jellypotatoe:
@ben_lubar @boomzilla
Can we please test disabling our custom CSS for blockquotes? https://github.com/boomzillawtf/tdwtf/search?utf8=✓&q=blockquote&type=I disabled that whole plugin (tdwtf-customizations) and still got the problems.
Let's test the blockquote theory here:
That's in their "Testing Ground" category.
-
@izzion said in Scrolling jellypotatoe:
@boomzilla, or someone else with a GH account they can access, can you please update the GH issue report with the fact that the replication case is confirmed sensitive to the "posts per page" setting?
I think that probably depends on the size of the subject. I believe I was able to repro when jumping into post 60,000 in the Status Thread with 20 and 50 page sizes. It just takes more scrolling to get to the page boundaries.
-
@boomzilla said in Scrolling jellypotatoe:
@boomzilla A "Restart" seemed to do the trick.
Reload doesn't call
./nodebb build
but restart does. That's the only difference.So if you used restart at some point after iframely was disabled, its templates wouldn't be "built".
-
@ben_lubar I don't think I did. It was reloads all the way until that last one.
-
@boomzilla said in Scrolling jellypotatoe:
Let's test the blockquote theory here:
I can't reproduce it there at all, so I'm starting to wonder if it's something we have here that they don't there, and it's interfering with the batch loading in some weird way we haven't tracked down yet.
-
@RaceProUK said in Scrolling jellypotatoe:
I can't reproduce it there at all, so I'm starting to wonder if it's something we have here that they don't there, and it's interfering with the batch loading in some weird way we haven't tracked down yet.
So, on my local instance I don't have any "weird" or custom things installed. I also don't have any of our images, so stuff looks weird. But I definitely get the bad scrolling behavior.
-
After the update, I can make it through my test thread #2 on mobile without any jumps.
-
Glad to hear it. You guys were very thorough in your debugging...
-
@julianlam
It's always nice to have a chance to use my powers of OCD for good
-
@julianlam said in Scrolling jellypotatoe:
Glad to hear it. You guys were very thorough in your debugging...
This community is full of very hardcore programming + QA people. And a number of said people also consider pendantry a sport, so thoroughness is practically assured.
Ironically it was exactly this that led to our unceremonious departure from our previous forum software...
-
@Arantor
Well, I would stipulate that the reason had more to do with the mutual hostility that built up between several members here and specific members of the Discourse dev team, and the fact that very few people were interested in communicating in a professional manner :P
-
@izzion We started off civil. We tried to help them.
-
@izzion To be fair, things got off to a bad start when Atwood decided to appoint himself a moderator here, and started moderating in a very heavy-handed way
-
@RaceProUK
to me, I try to apply the same mentality I use in my League of Legends games - assigning blame to other people for their mistakes or poor choices is not very useful, because I can't modify someone else's behavior. If I focus on areas where I could have done something differently or better, then I'll get more net benefit, and possibly a positive change for the next occurrence.
-
@izzion I wasn't active during that period (which I think was actually quite short), but I've heard enough from those who were active to know it was extremely unwelcome
-
@RaceProUK That's OK, we can just say that, to at least the type of community we have here, “ was a fucking asshole, and not in a good way”.
-
@Luhmann said in Scrolling jellypotatoe:
@boomzilla said in Scrolling jellypotatoe:
now you've ruined it for everyone
You're welcome
Dwayne Johnson - You're Welcome (from Moana/Official Video) – 02:49
— DisneyMusicVEVO
-
@izzion said in Scrolling jellypotatoe:
@Arantor
Well, I would stipulate that the reason had more to do with the mutual hostility that built up between several members here and specific members of the Discourse dev team, and the fact that very few people were interested in communicating in a professional manner :PThat's not entirely accurate. We were uncivil here, but attempted to follow their rules over on meta.d.
It didn't get us very far, especially when we asked questions about why a bug was closed, or questioned their ing.
-
@abarker said in Scrolling jellypotatoe:
It didn't get us very far
I do find it somewhat ironic that you getting banned for trying to get a bug resolved exposed another bug