@qtoggle/qui 1.20.0-alpha.6 → 1.20.0-alpha.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/less/lists.less +6 -12
- package/package.json +1 -1
- package/pyproject.toml +1 -1
package/less/lists.less
CHANGED
|
@@ -43,18 +43,12 @@ div.qui-list-child.qui-list-item {
|
|
|
43
43
|
opacity: 0;
|
|
44
44
|
}
|
|
45
45
|
|
|
46
|
-
/*
|
|
47
|
-
*
|
|
48
|
-
*
|
|
49
|
-
*
|
|
50
|
-
*
|
|
51
|
-
*
|
|
52
|
-
* the declaration, collapsing a skipped view to nothing. */
|
|
53
|
-
& > div.qui-icon-label-view {
|
|
54
|
-
content-visibility: auto;
|
|
55
|
-
contain-intrinsic-size: 0 3em;
|
|
56
|
-
contain-intrinsic-size: auto 3em;
|
|
57
|
-
}
|
|
46
|
+
/* No `content-visibility: auto` on the icon-label view either, and it is not coming back without a different
|
|
47
|
+
* mechanism. Skipping the rendering of off-screen rows means the browser has to do that work when they scroll in,
|
|
48
|
+
* and it does not keep up with a fast flick: measured on a 300-row list, every row in the viewport was still in
|
|
49
|
+
* the skipped state two frames after a jump, and only rendered about 400ms later. Rows arrive blank and fill in
|
|
50
|
+
* afterwards, which is far more noticeable than the paint it saves. The relevance margin that decides when the
|
|
51
|
+
* browser starts rendering is not author-controllable, so there is no tuning short of removing it. */
|
|
58
52
|
|
|
59
53
|
}
|
|
60
54
|
|
package/package.json
CHANGED