Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I had something different in mind, coming from Angular: There would be a list of comment objects associated with DOM nodes, then the comment list would get updated, and Angular would associate the DOM nodes with the wrong list entries.
How would a bad cache mess up the association between a comment and its ID?
I used to do AngularJS and I've done some react... maybe something like that could happen. I'd wager it's unlikely though (bordering on Angular/Inferno itself having a bug).
I've seen some other things that seem like caching issues (e.g., seeing the wrong counts when switching between posts).
A cache could literally report the wrong ID for a comment to the front end in the JSON if the caching isn't right (and bad input = bad output).
Granted, in both cases I'd wonder why we're not seeing this all the time, it's got to be something niche, possible something already fixed but not on all instances.