Well, of course [orange and black], as I said, I also want to know if you have any leads for fixing this at all or if it’s a total bust.
it does seem to just be some kind of quirk of deloading, and I believe I’ve seen this on several occasions myself. however i cant seem to find exactly the case that causes such a particular flicker. discourse is uh, messy to say the least, and because its such a dynamic blob of javascript its rather hard to track down. below is the scss responsible
//Add color to even-numbered posts plus 60px
div.topic-post:nth-child(2n) > .boxed > .row:last-of-type,
div.small-action:nth-child(2n), div.gap:nth-child(2n)
{
background: linear-gradient(90deg, var(--background_color_2) calc(#{$topic-body-width} + (#{$topic-body-width-padding} * 2) + #{60px}), var(--secondary) calc(#{$topic-body-width} + (#{$topic-body-width-padding} * 2) + #{60px}));
}
//Add color to odd-numbered posts plus 60px
div.topic-post:nth-child(2n+1) > .boxed > .row:last-of-type,
div.small-action:nth-child(2n+1) , div.gap:nth-child(2n+1)
{
background: linear-gradient(90deg, var(--background_color_1) calc(#{$topic-body-width} + (#{$topic-body-width-padding} * 2) + #{60px}), var(--secondary) calc(#{$topic-body-width} + (#{$topic-body-width-padding} * 2) + #{60px}));
}
funnily enough, when looking into anyone else experiencing this issue:
hi orange!
hi orange!!! it turns out this isnt the first time we’ve had this exact issue! and we didnt solve it then! hooray!
i personally think the best solution would be to not rely on css and just have javascript/processing/whatever to check if a post number is even rather than if its the nth post. because the nth post relies so heavily on discourse’s whims while the actual post number is rather stable. someone suggested it in the thread over on discourse meta too!
ive already been in contact with you about some other niche site additives so assuming orange isnt willing to use a non-css solution (lol) i can maybe rig something up for you in that regard too
1 Like
lmao shoutout past me
at some point between 2022 and 2026 I have completely forgotten ever having this happen
1 Like
haven’t seen it in ages ig
guess its the last visited thing which you know what makes sense
fwiw we try to avoid js as much as possible just to keep everything as lightweight as possible but we aren’t entirely unwilling to use it
im helping a friend move this weekend so i wont really be available to look at what it would take but i can’t imagine it would be impossible to use js instead of css to accomplish the same task xdd
1 Like
i do suppose that does cause some weirdness with locks/x posts later because theyre kind of posts and in the post tree but not in the post count? thanks discord love you discord
1 Like
discourse*
ye and the issue is that the last visited thing is in the tree but then falls out of it when you scroll
its probably not just the last visited one but also locks and maybe some cross-posts and anything else that is like Kind of a post but not really a post. if it was last visited only it shouldnt be triggering in the places it is repeatedly
nono it does seem to be only last visited. also it turns out if you put another div next to last visited in any circumstance it completely fucks the site beyond repair and you have to reload thats fun
1 Like
right
now that you found me talking about it i remember the issue and yeah none of the other stuff just vanishes lel
#vaporwavenumberone
3 Likes
also, least important thing about this problem (and please allow for how bad my image editing is)
Doesn’t The Second Image Look More Like How It’s Meant To Look?
this is ALSO to do with how the last visit thing works in the post tree. i wonder if it was doubled up to prevent this if it would flicker twice or not flicker at all
frankly I like how the last visit makes it not flip palettes but maybe thats just because i noticed it early on and got used to it
1 Like
yeah and trying to fix that (couldn’t find an easy way) was what brought my attention to this in the first place back in the day