fix status index approxmiation in timeline rendering for dynamically changing viewport geometries #3543
No reviewers
Labels
No labels
BE Request
Backlog
Better behavior
Blocked by deps
Bug
Code Review
Discussion
Doing
Feature Request / Enhancement
In the shining bright future maybe
It's complicated
MS Edge
Mememoon (or other niche browsers)
Missing API
Missing feature
Missing l10n/i18n
NL1
NL2
NL4
Need to verify on develop
RELEASE BLOCKER
Reassign or Close
Refactor
Regression
Safari
To Do
User story
Waiting on godot
accessibility
better documentation
chore
confirmed
easy ticket
incident
l10n update
mastoapi
mobile
needs design
needs-info
needs-review
stupid
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pleroma/pleroma-fe!3543
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "iamtakingiteasy/pleroma-fe:fix-timeline-rendering-status-index-approx"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Checklist
changelog.ddirectory, create a file named<code>.<type>.Currently dynamically changing viewport geometry can result in estimated indices outside the
statusesarray boundaries due to race betweenconst height = Math.max(document.body.offsetHeight, window.pageYOffset)andconst centerOfScreen = window.pageYOffset + window.innerHeight * 0.5in timeline.js as underlying window properties change their values between two expressions (at very least in firefox, window properties are not captured for the entirety of function execution unless bound to local variables and do reflect native updates immediately), this MR adds capping toapproxIndexsimilar tocappedScrollIndex.