bachirandClaude Sonnet 5
fa28783bcc
Root cause: the main table used auto layout, so every loadOlder()/ loadNewer() reflowed every column's width based on whatever was currently loaded -- visibly shifting the table, spilling past the viewport into a horizontal scrollbar, and corrupting loadOlder()'s scroll-position compensation (which assumes the scrollHeight delta after prepending rows is *only* the new rows' own height -- not true once existing rows also reflow). That's what made scrolling up feel like it kept snapping back down. - table-layout: fixed with explicit per-column widths (percentages throughout, not mixed with rem -- mixing meant the rem columns' width was added on top of the percentage budget instead of coming out of it), plus box-sizing: border-box so padding doesn't inflate columns beyond their declared width. - overflow-x: hidden instead of auto on the scroll container: with both x and y auto on the same element, the browser has to guess whether a vertical scrollbar will appear before laying out width: 100%, and a wrong guess understates available width by a scrollbar's worth -- exactly enough to tip a tightly-fitting table into needing horizontal scroll too. - Fixed a footer-row column count bug found along the way: it still had two actions-col cells and a colspan=5 label from before the link button was removed, leaving the label 6 columns short of Signalement and misaligning every footer cell after it. Verified with a 25-round scripted scroll-up stress test spanning 3 loadOlder() triggers: scroll position stays correctly anchored near where the user was looking, never jumps toward the bottom. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Drupal is an open source content management platform supporting a variety of websites ranging from personal weblogs to large community-driven websites. For more information, visit the Drupal website, Drupal.org, and join the Drupal community.
Contributing
Drupal is developed on Drupal.org, the home of the international Drupal community since 2001!
Drupal.org hosts Drupal's GitLab repository, its issue queue, and its documentation. Before you start working on code, be sure to search the issue queue and create an issue if your aren't able to find an existing issue.
Every issue on Drupal.org automatically creates a new community-accessible fork that you can contribute to. Learn more about the code contribution process on the Issue forks & merge requests page.
Usage
For a brief introduction, see USAGE.txt. You can also find guides, API references, and more by visiting Drupal's documentation page.
You can quickly extend Drupal's core feature set by installing any of its thousands of free and open source modules. With Drupal and its module ecosystem, you can often build most or all of what your project needs before writing a single line of code.
Changelog
Drupal keeps detailed change records. You can search Drupal's changes for a record of every notable breaking change and new feature since 2011.
Security
For a list of security announcements, see the Security advisories page (available as an RSS feed). This page also describes how to subscribe to these announcements via email.
For information about the Drupal security process, or to find out how to report a potential security issue to the Drupal security team, see the Security team page.
Need a helping hand?
Visit the Support page or browse over a thousand Drupal providers offering design, strategy, development, and hosting services.
Legal matters
Know your rights when using Drupal by reading Drupal core's license.
Learn about the Drupal trademark and logo policy here.