Skip to content

Fix content offset calculation for positioned layouts - #86

Merged
dhilt merged 3 commits into
mainfrom
issue-85--fix-content-offset
Oct 12, 2026
Merged

dhilt merged 3 commits into
mainfrom
issue-85--fix-content-offset

Conversation

@dhilt

@dhilt dhilt commented Oct 12, 2026 •

Copy link
Copy Markdown
Owner
  • Calculate content offsets from measured edges and scroll position instead of offsetParent-relative coordinates.
  • Restore correct initial loading and reload positioning for parent, external and window viewports.
  • Add e2e regressions for positioned layouts on both scrolling axes.
  • Update the Routines reference and replace the obsolete table example with a sticky-toolbar demo.

Fixes #85

dhilt added 3 commits October 12, 2026 13:21
Use measured edges and scroll position to keep offsets consistent for element and window viewports. Update the getOffset documentation.
Cover parent and external viewports on both axes, plus window mode.
Verify starting positions and stable offsets across scrolling and reload.
Update the Custom Routines guide and demo links.
Add visible-range tracking, scroll and reload controls.
@dhilt dhilt changed the title Fix content offset Fix content offset calculation for positioned layouts Oct 12, 2026
@dhilt
dhilt merged commit b597109 into main Oct 12, 2026
1 check passed
@dhilt
dhilt deleted the issue-85--fix-content-offset branch October 12, 2026 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Routines.getOffset() returns incorrect offsets with positioned ancestors

1 participant