selfie // eye contact
@TheLizardQueen your hair is glorious, as is your whole general scene
vaguely lewd shitpost
@jackofallEves this sure has some earthy terroir
You ever just put on a hat with ear flaps and pull your hood over the hat because things are too loud?
@lyliawisteria @steviemcfly The one where Ross cuddled a duck and thought it was Rachel
Do you like some Street Fighter III 3rd Strike? Some fellas here in Detroit are playing https://www.twitch.tv/detroitarcadeclub
you know sometimes computers are poop
@flugennock @Gargron A few more questions, if you don't mind:
On what instance is this happening? And, do you know what version that instance runs?
I contributed a change that affects column scrolling. But, it shouldn't be part of a release yet. I'm wondering if the instance on which you see this issue is running the latest pre-release master?
I can't reproduce this issue now, but it *was* an issue on master a couple of days ago and I submitted what I thought was a fix for it.
@Gargron @flugennock Oof, I didn't realize mastodon.social was deployed from master.
In that case, if it helps, I can submit a PR to revert the change ASAP. I don't think I have a quick fix off the top of my head and wouldn't like to see this linger as a bug in the wild.
@Gargron The problem is that the scroll event fires for *both* manual scrolling *and* programmatic scrolling via setting scrollTop. The wheel event is independent of that, at least.
That means there's not an easy way to distinguish between intentional scrolling or the scroll that happens when the column is held in place (e.g. either because the user previously scrolled down or because my mouse-moved logic kicked in)
@Gargron As far as I can tell from docs and inspecting events, the events from manual & programmatic scroll are identical.
The one workaround I've seen is to set a variable just before an automatic scroll, then use that variable to decide in the event handler that the scroll was not manual.
Hmm, I might give that a quick try, actually.
@flugennock @Gargron Sorry for the trouble, you shouldn't have to work around anything :)
@Gargron Okay, I think this is the last idea I've got for a fix. If it still causes issues after this, then... sorry for the trouble and thanks for humoring me 😅
Firing up the stream. Thinking I'm going to try setting up my machine to build Firefox today. This will probably be a mistake and kill my stream bandwidth. Fun! https://www.twitch.tv/lmorchard
Stream complete! I managed to get Firefox building and it was easier than the last time I tried it. Also, I'm glad I got a much more powerful PC on which to try this. https://www.twitch.tv/videos/333714826
