issues
search
WICG
/
layout-instability
A proposal for a Layout Instability specification
https://wicg.github.io/layout-instability/
Other
158
stars
26
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Include per-frame scores and timestamps in example.
#70
skobes-chromium
closed
4 years ago
0
Add note to explain the choice of 5 members
#69
npm1
closed
4 years ago
0
CFC: adopt to WebPerfWG as a Working Draft
#68
yoavweiss
opened
4 years ago
0
Fix ambiguous language in section 2.2, "has not shifted in $X or $Y"
#67
dholbert
opened
4 years ago
4
The spec should make it clearer whether `transform` affects "visual representation" and layout shift
#66
dholbert
opened
4 years ago
3
layout instability spec doesn't account for paint-only effects that don't influence css box size (e.g. box-shadow)
#65
dholbert
closed
4 years ago
7
Add note suggesting computational algorithm for impact region area.
#64
skobes-chromium
closed
4 years ago
0
Adjust wording about precision.
#63
skobes-chromium
closed
4 years ago
0
The "move distance" metric imposes a strange penalty on extremely-offscreen content (depending on how far offscreen it was)
#62
dholbert
opened
4 years ago
22
layout instability spec needs to clarify whether (and which) unpainted nodes are considered or not
#61
dholbert
closed
3 years ago
23
Specify expected behavior for overflows and containment
#60
wangxianzhu
opened
4 years ago
4
Make transform behavior clearer in the spec
#59
npm1
closed
4 years ago
1
Rename section 1.1 "Cumulative Layout Shift".
#58
skobes-chromium
closed
4 years ago
1
The spec disagrees with developer documentation about whether precise layout-shift values/thresholds should be relied on
#57
dholbert
closed
4 years ago
4
s/MUST/must/
#56
dholbert
closed
4 years ago
1
Layout Instability Spec needs to define what happens, in cases where its prescribed algorithm would divide by zero
#55
dholbert
closed
4 years ago
0
s/or/and/ in "greater of X or Y" expressions
#54
dholbert
closed
4 years ago
8
Explain (and perhaps make configurable) the magic number 3 in "3 or more pixel units" (when determining which nodes are shifted)
#53
dholbert
closed
2 years ago
13
Define how much data should be buffered (also: does 'buffered' impose a substantial cost on the whole web here?)
#52
dholbert
opened
4 years ago
17
Spec's usage of the term "line box generated by N" might be imprecise/incorrect (where N is a text node)
#51
dholbert
closed
4 years ago
3
Is `visibilitychange` really the right signal for when to aggregate layout shift?
#50
dholbert
closed
4 years ago
4
The spec and explainer seem to disagree on what "Cumulative Layout Shift" means
#49
dholbert
closed
4 years ago
1
explicit calculation for impact fraction?
#48
fred-wang
closed
4 years ago
3
arbitrary constants in the spec?
#47
fred-wang
closed
4 years ago
2
"End of session signal" section should refer to the page visibility spec
#46
fred-wang
closed
4 years ago
1
Elements without content shouldn't affect LS
#45
patrickhulce
closed
3 years ago
3
Add possible GPU fingerprinting concerns to the "security & privacy" section
#44
amtunlimited
closed
4 years ago
3
Fix editor syntax
#43
npm1
closed
4 years ago
0
Update availability note.
#42
skobes-chromium
closed
4 years ago
0
Use FrozenArray instead of sequence.
#41
skobes-chromium
closed
4 years ago
0
Attributes cannot accept sequence types - 'sources'
#40
stephenmcgruer
closed
4 years ago
6
Set the realm of new objects
#39
npm1
closed
4 years ago
0
Fix type of LayoutShift value.
#38
skobes-chromium
closed
4 years ago
0
Update Python to 3.7
#37
npm1
closed
4 years ago
1
Add shifted element attribution (#11).
#36
skobes-chromium
closed
4 years ago
0
Add source attribution to explainer.
#35
skobes-chromium
closed
4 years ago
0
Fix links
#34
skobes-chromium
closed
4 years ago
0
Start explainer for shifted element surfacing.
#33
skobes-chromium
closed
4 years ago
0
Add shifted element attribution (#11).
#32
skobes-chromium
closed
4 years ago
3
Fix usage of takeRecords in example
#31
npm1
closed
4 years ago
0
Minor mistake in code example
#30
philipwalton
closed
4 years ago
0
Expand introduction in spec.
#29
skobes-chromium
closed
4 years ago
0
Expand introduction in spec
#28
npm1
closed
4 years ago
0
Add Limitations section to explainer.
#27
skobes-chromium
closed
5 years ago
0
Add limitations section in explainer
#26
npm1
closed
5 years ago
2
Add explicit [Exposed]
#25
saschanaz
closed
5 years ago
1
Granularity of measurement?
#24
alice
closed
5 years ago
5
explainer should perhaps explain how much the metric is intended to evolve over time and vary between implementations
#23
dbaron
closed
5 years ago
4
Refactor the Layout Instability API spec.
#22
skobes-chromium
closed
5 years ago
0
clarify treatment of scrolling
#21
skobes-chromium
closed
5 years ago
1
Previous
Next