Skip to content

(scroll-to-text) Allow limiting the number of scroll fragments #11968

@vmpstr

Description

@vmpstr

What is the issue with the HTML Standard?

(The PR for this feature is being upstreamed here #11895)

Currently the number of specified scroll fragments could be theoretically unbounded (limited I guess only by the length of the url string).

Similar to #11938, in order to limit the amount of work that a user-agent has to do in response, I propose we allow the user-agent to limit the number of fragments processed. I don't know if there's any particular specific number that works best, so perhaps leaving this up to user-agent discretion. In practice, in Chromium we'd like to try and limit this to something like 100 which should be plenty for most cases (famous last words, I know).

@domfarolino @annevk @bokand

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions