Closed H3rnand3zzz closed 10 months ago
id
from DB (I am not sure if it's correct, probably stanza-id should be passed, but also we should consider LMC case)PAD_SIZE
from 1000
to 10000
, it helps rendering in the background, as well as with lines amount calculationstanza_id
from the DB (changes are highly interconnected)Pass id from DB (I am not sure if it's correct, probably stanza-id should be passed, but also we should consider LMC case)
What were your thoughts here exactly? I think id that you used is correct.
Addressed the issues outlined in the review.
addressed
Fix a problem: extremely big message (e.g. 3k lines) causes profanity to jump back once scrolled on top
Was this already the case before your change? I'm not even sure 3k lines fit on a screen? :D
it might affect users who don't use history, the approach has a good idea, but requires more careful implementation
Affect how? Should we wait with merging/reviewing the code before this is solved? I would prefer to not include something "wrong" in master because several of our users use master to help us find bugs. So this might annoy them or make them report something that we are aware of.
it might affect users who don't use history, the approach has a good idea, but requires more careful implementation
Affect how? Should we wait with merging/reviewing the code before this is solved? I would prefer to not include something "wrong" in master because several of our users use master to help us find bugs. So this might annoy them or make them report something that we are aware of.
It might've affected in a previous version, currently it was removed, hence no one should be affected in any negative way (at least I don't see a problem currently, I might've missed something obviously).
Current state:
Currently it's full of debugging lines with some issues which are to be fixed before release:
This line is for github CI/CD system to link the issue
Fix https://github.com/profanity-im/profanity/issues/1934