Process Want #722: Comprehensive scrolling API

[Copilot]

Processes Want submission from issue #722 requesting enhancements to the scrollIntoView API including configurable spacing, partial element scrolling, Promise-based completion, and sticky element handling.

Changes

• Created wants/348f7c4c-c41c-49da-8c84-9213b02db8c6.md with:
  • UUID: 348f7c4c-c41c-49da-8c84-9213b02db8c6
  • Tags: javascript, dom, api
  • Discussion URL: https://github.com/WebWeWant/webwewant.fyi/discussions/722
  • Related specs: CSSWG issues #9836 (scrollIntoView enhancements) and #3104 (scroll-margin/sticky positioning)

Validation

• ✅ No duplicates found
• ✅ All required fields validated
• ✅ Frontmatter structure correct

Closes #722

Original prompt

---

This section details on the original issue you should resolve

<issue_title>A comprehensive scrolling API</issue_title>
<issue_description>---
title: A comprehensive scrolling API
date: 2025-03-21T05:45:54.403Z
submitter: ExtAnimal
number: 67dcfd12c70e2900a37d771d
tags: [ ]
discussion: https://github.com/WebWeWant/webwewant.fyi/discussions/
status: [ discussing || in-progress || complete ]
related:

• title:
  url:
  type: [ article || explainer || draft || spec || note || discussion ]

---

The scrollIntoView API has the block and inline settings which tell it where in the scrolling viewport the target element should be scrolled, 'start', 'center' etc. And has behavior smooth. But that is not enough for real world use cases.

You may want "space" round the target element rather than when scrolling to block : 'start' having the top touch the top of the viewport.

If the target is extremely large, you may need to ask for just the top 200 pixels of it to move into view.

And finally... Of course it should yield a Promise which resolves when the smooth scrolling has settled and the layout is in its final shape.

I have an issue outstanding: w3c/csswg-drafts#9836

Also, it does not handle sticky elements which occlude the target part of the viewport.

w3c/csswg-drafts#3104

---

If posted, this will appear at https://webwewant.fyi/wants/67dcfd12c70e2900a37d771d/</issue_description>

<agent_instructions>🤖 Approved and ready for processing.

Follow ALL instructions in .github/instructions/wants-processing.instructions.md section "Step 5: Want File Creation" - this is your ONLY source of truth.

Key steps:

1. Run npm run create-want to generate UUID and markdown template
2. Fill in the markdown file with data from this issue (ensure the discussion URL ends with this issue number)
3. Add any related links and update the original issue body to match the cleaned want content (no frontmatter)
4. Run npm run validate-want wants/<UUID>.md to validate
5. Create branch and PR with markdown file
6. Reference this issue number in the PR description

Do not look at any other documentation files for processing guidance.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@aarongustafson /process

• Fixes A comprehensive scrolling API #722

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.