Skip to content

[css-overflow-5] Should nested scroll-marker generating elements result in nested ::scroll-marker pseudo-elements? #11601

@flackr

Description

@flackr

Consider the following demo also prototyped at https://codepen.io/flackr/pen/JoPxZmV:

<style>
section::scroll-marker {
  content: attr(data-title);
}
</style>
<section data-title="About">
  <section data-title="Who">
  </section>
  <section data-title="What we do">
  </section>
</section>
  1. This could generate a flat list of markers:

    • About
    • Who
    • What we do
  2. Or, should the generated ::scroll-marker pseudo-element for About contain the markers established by descendant elements, e.g.

    • About
      • Who
      • What we do

I've written up an example of what this might look like for both table of contents like scenarios and dot-like scenarios. This does affect how you would have to handle dots to have them render nicely. E.g you'd probably need the dots containing other dots to render their dot as a ::before so that it doesn't wrap all of its descendants.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions