-
Notifications
You must be signed in to change notification settings - Fork 297
Open
Labels
Description
I'm currently in the progress of upgrading from WR 58.0 to 60.0 - and I've noticed that there is a new parameter called SpaceAndClipInfo
that is now needed almost everywhere. However, there doesn't seem to be a SpatialId::new()
and most examples however just generate a SpaceAndClipInfo::root_scroll()
and then copy the root_info.spatial_id
to all the nodes. So what's the point?
- How is a
SpatialId
different from aPipelineId
? - Do scroll frames need a new scroll ID?
- Is it wrong if every node has a distinct
SpatialId
? - Why is a
SpatialId
required to define a new clip? - Can there be an example of when / how to generate a new
SpatialId
?
Also I've noticed that the scrolling
example doesn't actually scroll anymore (at least on Windows), maybe it's because the spatial IDs of the scrolling and non-scrolling content are the same?
PS: A CHANGELOG.md or something like that would be great to have.
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
kvark commentedon Jul 15, 2019
Spatial IDs are here to identify unique spatial nodes, i.e. elements that affect positioning. These are:
Pipeline Id are entirely different things - they define the scopes of display lists. On the HTML level, they correspond to iframes.
Yes. Scrolling is changing positions.
Only the nodes that affect positions would have distinct spatial Ids.
A clip has a position somewhere. SpatialID defines what this position is relative to.
Any use of reference/sticky/scroll frames involve new spatial IDs. Do you see them not covered by existing examples?
I checked on Linux and also can see no scrolling. This is a bug.
Agreed!