@ascribed/elements 0.1.1 → 0.1.2-next.4
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/CONTRACT.md +4 -4
- package/css/style.css +4 -1
- package/package.json +2 -1
package/CONTRACT.md
CHANGED
|
@@ -30,7 +30,7 @@ A change to this contract changes the site emitter (`crates/tessera-emit`), the
|
|
|
30
30
|
|
|
31
31
|
**Plain text of inline content.** Where an attribute holds a title or label written as inline markdown, its value is the inline content's text: phrases substituted (they already are, in the resolved page), code spans as their text, emphasis and links as their text, images as their alt text, raw inline HTML dropped, and line breaks as single spaces. So ``.Try the *new* `quill` CLI`` becomes `Try the new quill CLI`.
|
|
32
32
|
|
|
33
|
-
**Labels** come from the content model: note types' `label` (docs/contracts/content-model.md §11), dimensions' and dimension values' `labels` (§7), and lifecycle states' `label` (§9). A value without a declared label is shown as itself.
|
|
33
|
+
**Labels** come from the content model: note types' `label` (docs/content/contracts/content-model.md §11), dimensions' and dimension values' `labels` (§7), and lifecycle states' `label` (§9). A value without a declared label is shown as itself.
|
|
34
34
|
|
|
35
35
|
## 1. `<ascribe-note>`
|
|
36
36
|
|
|
@@ -198,7 +198,7 @@ The element library may style `details` and `summary`, and implements no element
|
|
|
198
198
|
|
|
199
199
|
## 6. Project widgets
|
|
200
200
|
|
|
201
|
-
A project widget (SPEC §6) becomes a custom element whose tag is the widget's name (SPEC §9.4). Widget names are valid custom-element names: they contain a hyphen, and docs/contracts/content-model.md §15 rejects names starting with `ascribe-` and HTML's reserved names. The project supplies the element's implementation; the element library doesn't.
|
|
201
|
+
A project widget (SPEC §6) becomes a custom element whose tag is the widget's name (SPEC §9.4). Widget names are valid custom-element names: they contain a hyphen, and docs/content/contracts/content-model.md §15 rejects names starting with `ascribe-` and HTML's reserved names. The project supplies the element's implementation; the element library doesn't.
|
|
202
202
|
|
|
203
203
|
**Attributes**, in this order:
|
|
204
204
|
|
|
@@ -206,7 +206,7 @@ A project widget (SPEC §6) becomes a custom element whose tag is the widget's n
|
|
|
206
206
|
2. `primary`: an identifier primary, if the widget takes one and it's given. A text primary is content instead (below).
|
|
207
207
|
3. Each attribute in the widget's declaration, in declared order, with the value given or, if absent, its declared default. A value set's members are joined by single spaces; booleans are `true` or `false`; other values are their text. An attribute with neither a value nor a default is left out. A declaration can't use `heading`, `primary`, or HTML's global or event-handler attribute names (SPEC §7.2; content-model.md, `model-attribute-reserved`), so these never clash.
|
|
208
208
|
|
|
209
|
-
**Children and placement**, by the widget's form and binding (docs/contracts/content-model.md §15):
|
|
209
|
+
**Children and placement**, by the widget's form and binding (docs/content/contracts/content-model.md §15):
|
|
210
210
|
|
|
211
211
|
| Widget | Element |
|
|
212
212
|
|---|---|
|
|
@@ -222,4 +222,4 @@ A wrapping widget follows §0's layout for elements that wrap markdown; an empty
|
|
|
222
222
|
|
|
223
223
|
## 7. Glossary terms
|
|
224
224
|
|
|
225
|
-
There's no element for glossary terms. In the site output, an occurrence the glossary links (docs/contracts/content-model.md §13) is an ordinary markdown link to the term's `link` target, as a route, with the term's definition as the link title: `[API key](/docs/reference/glossary/#api-key "A secret token that authenticates the Quill agent.")`. Terms without a `link` stay plain text (content-model.md Q7).
|
|
225
|
+
There's no element for glossary terms. In the site output, an occurrence the glossary links (docs/content/contracts/content-model.md §13) is an ordinary markdown link to the term's `link` target, as a route, with the term's definition as the link title: `[API key](/docs/reference/glossary/#api-key "A secret token that authenticates the Quill agent.")`. Terms without a `link` stay plain text (content-model.md Q7).
|
package/css/style.css
CHANGED
|
@@ -238,10 +238,12 @@ ascribe-tabs > [role="tablist"] > [role="tab"]:focus-visible {
|
|
|
238
238
|
|
|
239
239
|
/* <ascribe-availability> -------------------------------------------------- */
|
|
240
240
|
|
|
241
|
+
/* The `; ` between targets is for readers without CSS; as badges it would
|
|
242
|
+
read as a stray mark, so it's transparent here and only spaces them. */
|
|
241
243
|
ascribe-availability {
|
|
242
244
|
display: block;
|
|
243
245
|
margin-block: var(--ascribe-space-small);
|
|
244
|
-
color:
|
|
246
|
+
color: transparent;
|
|
245
247
|
font-family: var(--ascribe-font-family);
|
|
246
248
|
font-size: var(--ascribe-font-size-small);
|
|
247
249
|
}
|
|
@@ -249,6 +251,7 @@ ascribe-availability {
|
|
|
249
251
|
/* The lead-in is generated content, so a site can restyle or translate it. */
|
|
250
252
|
ascribe-availability::before {
|
|
251
253
|
content: "Available: ";
|
|
254
|
+
color: var(--ascribe-muted-color);
|
|
252
255
|
}
|
|
253
256
|
|
|
254
257
|
ascribe-availability-target {
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ascribed/elements",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2-next.4",
|
|
4
4
|
"description": "Ascribe's web component library for the site output.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MPL-2.0",
|
|
@@ -36,6 +36,7 @@
|
|
|
36
36
|
"publishConfig": {
|
|
37
37
|
"access": "public"
|
|
38
38
|
},
|
|
39
|
+
"gitHead": "7031f6b286142835855efa815a5c49a62cfff67d",
|
|
39
40
|
"scripts": {
|
|
40
41
|
"build": "tsc -p tsconfig.build.json",
|
|
41
42
|
"typecheck": "tsc --noEmit",
|