@webref/css 6.12.6 → 6.12.8
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/css-anchor-position.json +48 -2
- package/css-text-4.json +6 -6
- package/css-values-5.json +1 -8
- package/css-view-transitions-2.json +1 -1
- package/mediaqueries-5.json +38 -1
- package/package.json +1 -1
package/css-anchor-position.json
CHANGED
|
@@ -191,6 +191,52 @@
|
|
|
191
191
|
"alignItems"
|
|
192
192
|
]
|
|
193
193
|
},
|
|
194
|
+
{
|
|
195
|
+
"name": "position-visibility",
|
|
196
|
+
"href": "https://drafts.csswg.org/css-anchor-position-1/#propdef-position-visibility",
|
|
197
|
+
"value": "always | [ anchors-valid || anchors-visible || no-overflow ]",
|
|
198
|
+
"initial": "anchors-visible",
|
|
199
|
+
"appliesTo": "absolutely-positioned elements",
|
|
200
|
+
"inherited": "no",
|
|
201
|
+
"percentages": "n/a",
|
|
202
|
+
"computedValue": "as specified",
|
|
203
|
+
"canonicalOrder": "per grammar",
|
|
204
|
+
"animationType": "discrete",
|
|
205
|
+
"values": [
|
|
206
|
+
{
|
|
207
|
+
"name": "always",
|
|
208
|
+
"prose": "This property has no effect. (The element is displayed without regard for its anchors or its overflowing status.)",
|
|
209
|
+
"href": "https://drafts.csswg.org/css-anchor-position-1/#valdef-position-visibility-always",
|
|
210
|
+
"type": "value",
|
|
211
|
+
"value": "always"
|
|
212
|
+
},
|
|
213
|
+
{
|
|
214
|
+
"name": "anchors-valid",
|
|
215
|
+
"prose": "If any of the element’s required anchor references do not resolve to a target anchor element, the element is strongly hidden. What is a required anchor reference? anchor() functions that don’t have a fallback value; the default anchor *sometimes*? Need more detail here. Any anchors are missing, or all anchors are missing? I can see use-cases for either, potentially. Do we want to make a decision here, or make it controllable somehow?",
|
|
216
|
+
"href": "https://drafts.csswg.org/css-anchor-position-1/#valdef-position-visibility-anchors-valid",
|
|
217
|
+
"type": "value",
|
|
218
|
+
"value": "anchors-valid"
|
|
219
|
+
},
|
|
220
|
+
{
|
|
221
|
+
"name": "anchors-visible",
|
|
222
|
+
"prose": "If the element has a default anchor element but the anchor element is clipped by intervening elements, this element is also strongly hidden.",
|
|
223
|
+
"href": "https://drafts.csswg.org/css-anchor-position-1/#valdef-position-visibility-anchors-visible",
|
|
224
|
+
"type": "value",
|
|
225
|
+
"value": "anchors-visible"
|
|
226
|
+
},
|
|
227
|
+
{
|
|
228
|
+
"name": "no-overflow",
|
|
229
|
+
"prose": "If the element overflows its inset-modified containing block, even after applying position-try, then the element is strongly hidden.",
|
|
230
|
+
"href": "https://drafts.csswg.org/css-anchor-position-1/#valdef-position-visibility-no-overflow",
|
|
231
|
+
"type": "value",
|
|
232
|
+
"value": "no-overflow"
|
|
233
|
+
}
|
|
234
|
+
],
|
|
235
|
+
"styleDeclaration": [
|
|
236
|
+
"position-visibility",
|
|
237
|
+
"positionVisibility"
|
|
238
|
+
]
|
|
239
|
+
},
|
|
194
240
|
{
|
|
195
241
|
"name": "position-try-options",
|
|
196
242
|
"href": "https://drafts.csswg.org/css-anchor-position-1/#propdef-position-try-options",
|
|
@@ -626,7 +672,7 @@
|
|
|
626
672
|
},
|
|
627
673
|
{
|
|
628
674
|
"name": "anchor()",
|
|
629
|
-
"prose": "An absolutely-positioned element can use the anchor() function as a value in its inset properties to refer to the position of one or more anchor elements. The anchor() function resolves to a <length>.",
|
|
675
|
+
"prose": "An absolutely-positioned element can use the anchor() function as a value in its inset properties to refer to the position of one or more anchor elements. The anchor() function resolves to a <length>. It is only valid to be used in the inset properties.",
|
|
630
676
|
"href": "https://drafts.csswg.org/css-anchor-position-1/#funcdef-anchor",
|
|
631
677
|
"type": "function",
|
|
632
678
|
"value": "anchor( <anchor-element>? <anchor-side>, <length-percentage>? )",
|
|
@@ -745,7 +791,7 @@
|
|
|
745
791
|
},
|
|
746
792
|
{
|
|
747
793
|
"name": "anchor-size()",
|
|
748
|
-
"prose": "An absolutely-positioned element can use the anchor-size() function in its sizing properties to refer to the size of one or more anchor elements. The anchor-size() function resolves to a <length>.",
|
|
794
|
+
"prose": "An absolutely-positioned element can use the anchor-size() function in its sizing properties to refer to the size of one or more anchor elements. The anchor-size() function resolves to a <length>. It is only valid to be used in the sizing properties.",
|
|
749
795
|
"href": "https://drafts.csswg.org/css-anchor-position-1/#funcdef-anchor-size",
|
|
750
796
|
"type": "function",
|
|
751
797
|
"value": "anchor-size( <anchor-element>? <anchor-size>, <length-percentage>? )",
|
package/css-text-4.json
CHANGED
|
@@ -472,7 +472,7 @@
|
|
|
472
472
|
},
|
|
473
473
|
{
|
|
474
474
|
"name": "balance",
|
|
475
|
-
"prose": "Line breaks are chosen to balance the remaining (empty) space in each line box, if better balance than auto is possible. This must not change the number of line boxes the block would contain if text-wrap were set to auto. The remaining space to consider is that which remains after placing floats and inline content, but before any adjustments due to text justification. Line boxes are balanced when the standard deviation from the average inline-size of the remaining space in each line box is reduced over the block (including lines that end in a forced break). The exact algorithm is UA-defined. UAs may treat this value as auto if there are more than ten lines to balance.",
|
|
475
|
+
"prose": "Line breaks are chosen to balance the remaining (empty) space in each line box, if better balance than auto is possible. This must not change the number of line boxes the block would contain if text-wrap were set to auto. The remaining space to consider is that which remains after placing floats and inline content, but before any adjustments due to text justification. Line boxes are balanced when the standard deviation from the average inline-size of the remaining space in each line box is reduced over the block (including lines that end in a forced break). Groups of lines separated by a forced line break are processed separately. The exact algorithm is UA-defined. UAs may treat this value as auto if there are more than ten lines to balance.",
|
|
476
476
|
"href": "https://drafts.csswg.org/css-text-4/#valdef-text-wrap-style-balance",
|
|
477
477
|
"type": "value",
|
|
478
478
|
"value": "balance"
|
|
@@ -1297,11 +1297,11 @@
|
|
|
1297
1297
|
"value": "normal"
|
|
1298
1298
|
},
|
|
1299
1299
|
{
|
|
1300
|
-
"name": "trim-
|
|
1300
|
+
"name": "trim-both",
|
|
1301
1301
|
"prose": "Set fullwidth opening punctuation with half-width glyphs (flush) at the start of each line; set fullwidth closing punctuation with half-width glyphs (flush) at the end of each line; and collapse spacing between punctuation glyphs as described below.",
|
|
1302
|
-
"href": "https://drafts.csswg.org/css-text-4/#valdef-text-spacing-trim-trim-
|
|
1302
|
+
"href": "https://drafts.csswg.org/css-text-4/#valdef-text-spacing-trim-trim-both",
|
|
1303
1303
|
"type": "value",
|
|
1304
|
-
"value": "trim-
|
|
1304
|
+
"value": "trim-both"
|
|
1305
1305
|
},
|
|
1306
1306
|
{
|
|
1307
1307
|
"name": "space-first",
|
|
@@ -1326,7 +1326,7 @@
|
|
|
1326
1326
|
},
|
|
1327
1327
|
{
|
|
1328
1328
|
"name": "auto",
|
|
1329
|
-
"prose": "The user agent chooses a set of typographically high quality spacing values. Different user agents running on different platforms may pick different values. Do we need auto? It would be weird for the author to choose platform-dependent behavior at the start of the first line, and it should otherwise use trim-
|
|
1329
|
+
"prose": "The user agent chooses a set of typographically high quality spacing values. Different user agents running on different platforms may pick different values. Do we need auto? It would be weird for the author to choose platform-dependent behavior at the start of the first line, and it should otherwise use trim-both.",
|
|
1330
1330
|
"href": "https://drafts.csswg.org/css-text-4/#valdef-text-spacing-trim-auto",
|
|
1331
1331
|
"type": "value",
|
|
1332
1332
|
"value": "auto"
|
|
@@ -1496,7 +1496,7 @@
|
|
|
1496
1496
|
"name": "<spacing-trim>",
|
|
1497
1497
|
"href": "https://drafts.csswg.org/css-text-4/#typedef-spacing-trim",
|
|
1498
1498
|
"type": "type",
|
|
1499
|
-
"value": "space-all | normal |
|
|
1499
|
+
"value": "space-all | normal | space-first | trim-start | trim-both | trim-all"
|
|
1500
1500
|
}
|
|
1501
1501
|
]
|
|
1502
1502
|
}
|
package/css-values-5.json
CHANGED
|
@@ -269,13 +269,6 @@
|
|
|
269
269
|
"type": "value",
|
|
270
270
|
"value": "string"
|
|
271
271
|
},
|
|
272
|
-
{
|
|
273
|
-
"name": "url",
|
|
274
|
-
"prose": "The substitution value is a CSS <url> value, whose url is the literal value of the attribute. (No CSS parsing or \"cleanup\" of the value is performed.) No value triggers fallback.",
|
|
275
|
-
"href": "https://drafts.csswg.org/css-values-5/#valdef-attr-url",
|
|
276
|
-
"type": "value",
|
|
277
|
-
"value": "url"
|
|
278
|
-
},
|
|
279
272
|
{
|
|
280
273
|
"name": "ident",
|
|
281
274
|
"prose": "The substitution value is a CSS <custom-ident>, whose value is the literal value of the attribute, with leading and trailing ASCII whitespace stripped. (No CSS parsing of the value is performed.) If the attribute value, after trimming, is the empty string, there is instead no substitution value. If the <custom-ident>’s value is a CSS-wide keyword or default, there is instead no substitution value.",
|
|
@@ -358,7 +351,7 @@
|
|
|
358
351
|
"name": "<attr-type>",
|
|
359
352
|
"href": "https://drafts.csswg.org/css-values-5/#typedef-attr-type",
|
|
360
353
|
"type": "type",
|
|
361
|
-
"value": "string |
|
|
354
|
+
"value": "string | ident | color | number | percentage | length | angle | time | frequency | flex | <dimension-unit>"
|
|
362
355
|
},
|
|
363
356
|
{
|
|
364
357
|
"name": "<dimension-unit>",
|
|
@@ -93,7 +93,7 @@
|
|
|
93
93
|
"name": "<pt-name-and-class-selector>",
|
|
94
94
|
"href": "https://drafts.csswg.org/css-view-transitions-2/#typedef-pt-name-and-class-selector",
|
|
95
95
|
"type": "type",
|
|
96
|
-
"value": "<pt-name-selector
|
|
96
|
+
"value": "<pt-name-selector> <pt-class-selector>? | <pt-class-selector>"
|
|
97
97
|
},
|
|
98
98
|
{
|
|
99
99
|
"name": "<pt-class-selector>",
|
package/mediaqueries-5.json
CHANGED
|
@@ -146,7 +146,44 @@
|
|
|
146
146
|
"href": "https://drafts.csswg.org/mediaqueries-5/#descdef-media-display-mode",
|
|
147
147
|
"for": "@media",
|
|
148
148
|
"value": "fullscreen | standalone | minimal-ui | browser | picture-in-picture",
|
|
149
|
-
"type": "discrete"
|
|
149
|
+
"type": "discrete",
|
|
150
|
+
"values": [
|
|
151
|
+
{
|
|
152
|
+
"name": "fullscreen",
|
|
153
|
+
"prose": "The browsing context is displayed with browser UI elements hidden and takes up the entirety of the available display area. The fullscreen context may have been caused by the fullscreen display mode in the application manifest, by the requestFullscreen() method of the Fullscreen API, or through some other means (such as the user manually activating fullscreen mode using the user agent’s built-in controls). Corresponds to the fullscreen display mode.",
|
|
154
|
+
"href": "https://drafts.csswg.org/mediaqueries-5/#valdef-media-display-mode-fullscreen",
|
|
155
|
+
"type": "value",
|
|
156
|
+
"value": "fullscreen"
|
|
157
|
+
},
|
|
158
|
+
{
|
|
159
|
+
"name": "standalone",
|
|
160
|
+
"prose": "The standalone display mode is in use. Only applicable in an application context.",
|
|
161
|
+
"href": "https://drafts.csswg.org/mediaqueries-5/#valdef-media-display-mode-standalone",
|
|
162
|
+
"type": "value",
|
|
163
|
+
"value": "standalone"
|
|
164
|
+
},
|
|
165
|
+
{
|
|
166
|
+
"name": "minimal-ui",
|
|
167
|
+
"prose": "The minimal-ui display mode is in use. Only applicable in an application context.",
|
|
168
|
+
"href": "https://drafts.csswg.org/mediaqueries-5/#valdef-media-display-mode-minimal-ui",
|
|
169
|
+
"type": "value",
|
|
170
|
+
"value": "minimal-ui"
|
|
171
|
+
},
|
|
172
|
+
{
|
|
173
|
+
"name": "browser",
|
|
174
|
+
"prose": "The browsing context is displayed using the platform-specific convention for opening hyperlinks in the user agent (e.g., in a browser tab or web browser window with controls such as an address bar). This should be used for non-application contexts where no other display mode is appropriate. Corresponds to the browser display mode.",
|
|
175
|
+
"href": "https://drafts.csswg.org/mediaqueries-5/#valdef-media-display-mode-browser",
|
|
176
|
+
"type": "value",
|
|
177
|
+
"value": "browser"
|
|
178
|
+
},
|
|
179
|
+
{
|
|
180
|
+
"name": "picture-in-picture",
|
|
181
|
+
"prose": "This mode allows users to continue consuming media while they interact with other sites or applications on their device. The browsing context is displayed in a floating and always-on-top window. A user agent may include other platform specific UI elements, such as \"back-to-tab\" and \"site information\" buttons or whatever is customary on the platform and user agent.",
|
|
182
|
+
"href": "https://drafts.csswg.org/mediaqueries-5/#valdef-media-display-mode-picture-in-picture",
|
|
183
|
+
"type": "value",
|
|
184
|
+
"value": "picture-in-picture"
|
|
185
|
+
}
|
|
186
|
+
]
|
|
150
187
|
},
|
|
151
188
|
{
|
|
152
189
|
"name": "resolution",
|