Skip to content

Commit 63d7fd2

Browse files
svgeesussvgeesus
committed
for publication
2 parents 6bd20a4 + bb45c6c commit 63d7fd2

File tree

6 files changed

+242
-27
lines changed

6 files changed

+242
-27
lines changed

‎css-paint-api/README_V2.md‎

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
```js
2+
registerPainter('something', class extends ElementPainter {
3+
visualOverflow(geometry, styleMap) {
4+
return {
5+
// Size of overflow.
6+
};
7+
}
8+
9+
drawBackground(ctx, geometry, styleMap) {
10+
ctx.save();
11+
ctx.globalAlpha = 0.5; // Local to just the background layer, are there other canvas ctx params which
12+
super(ctx, geom, styleMap);
13+
ctx.restore();
14+
ctx.draw(styleMap.get('--other-background-image'));
15+
}
16+
17+
configureBackgroundContext(ctx, geometry, styleMap) {
18+
ctx.clipPath = new Path2D(); // ctx here would be subset that could be describing imperitively.
19+
}
20+
21+
drawBorder(ctx, geometry, styleMap) {
22+
23+
}
24+
25+
configureBorderContext(ctx, geometry, styleMap) {
26+
ctx.clipPath = new Path2D(); // ctx here would be subset that could be describing imperitively.
27+
}
28+
29+
drawForeground(ctx, geometry, styleMap) { // TODO add issue for this callback, use cases.
30+
ctx.drawImage(styleMap.get('--something-in-content-layer'));
31+
32+
super(ctx, geometry, styleMap);
33+
34+
ctx.drawImage(styleMap.get('--something-in-content-layer'));
35+
}
36+
37+
configureForegroundContext(ctx, geometry, styleMap) {
38+
ctx.clipPath = new Path2D(); // ctx here would be subset that could be describing imperitively.
39+
}
40+
41+
// still need this as creates stacking context.
42+
configureContext(ctx, geometry, styleMap) {
43+
ctx.clipPath = new Path2D(); // ctx here would be subset that could be describing imperitively.
44+
}
45+
});
46+
```
47+
48+
```css
49+
.class {
50+
painter: something; // implies this creates a stacking context.
51+
}
52+
```
53+
54+
55+
```js
56+
PaintV2RenderingContext.drawImage(styleMap.get('background-image'), ....);
57+
PaintV2RenderingContext.opacity
58+
PaintV2RenderingContext.clipPath = Path2D
59+
PaintV2RenderingContext.filter = styleMap.get('--filter-type'); or 'blur(2px)';
60+
61+
```

‎css-parser-api/Overview.bs‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,10 @@ Group: houdini
55
ED: https://drafts.css-houdini.org/css-parser-api-1/
66
Shortname: css-parser-api
77
Level: 1
8-
Abstract:
8+
Abstract: This specification is not currently being worked on in the Houdini TF. Instead, it will be worked on in a WICG repository. This document will link to that repository once it exists.
99
Editor: Tab Atkins, jackalmage@gmail.com
1010
Editor: Shane Stephens, shanestephens@google.com
1111
Editor: Daniel Glazman, danie.glazman@disruptiveinnovations.com
1212
Editor: Brian Kardell, bkardell@gmail.com
13+
Warning: Replaced by http://example.com/filler-url
1314
</pre>

‎css-parser-api/readme.md‎

Lines changed: 3 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,5 @@
11
CSS Parser Explainer
2-
==============================
2+
====================
33

4-
The CSS Parser API goal is to solve common use cases
5-
that web developers encounter where they want to parse
6-
a string that follows the syntax and grammar of CSS and
7-
utilize the browser's built in parser to return an object.
8-
9-
Current Use Cases
10-
------------------
11-
* Be able to pass the following in to the parser and get
12-
a representative object in return
13-
* property and value
14-
* selector (see [bug 24115](https://www.w3.org/Bugs/Public/show_bug.cgi?id=24115))
15-
* css rule
16-
* full stylesheet
17-
* Be able to turn off/on error handling which will enable
18-
the capability to use the parser for custom language needs
19-
or CSS polyfilling.
4+
This specification is not currently being worked on in the Houdini TF.
5+
Instead, it will be worked on in a [WICG repository](https://github.com/WICG/CSS-Parser-API).

‎css-properties-values-api/Overview.bs‎

Lines changed: 17 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Repository: w3c/css-houdini-drafts
3535

3636
<pre class='link-defaults'>
3737
spec:css-transforms-1; type:type; text:<transform-function>
38-
spec:css-conditional-3; type:method; text:supports(property, value)
38+
spec:cssom-1; type:interface; text:CSS
3939
</pre>
4040

4141
Introduction {#intro}
@@ -90,7 +90,7 @@ following members:
9090
:: True if this custom property should inherit down the DOM tree; False otherwise.
9191

9292
: <dfn dict-member for=PropertyDescriptor>initialValue</dfn>
93-
:: The initial value of this custom property.
93+
:: The initial value of this custom property.
9494

9595
The {{registerProperty()}} function {#the-registerproperty-function}
9696
--------------------------------------------------------------------
@@ -119,19 +119,19 @@ not parseable using the provided {{PropertyDescriptor/syntax}} must cause it to
119119
throw a {{SyntaxError}}. If no {{PropertyDescriptor/initialValue}} is provided and the
120120
{{PropertyDescriptor/syntax}} is '*', then a special initial value used. This initial
121121
value must be considered parseable by {{registerProperty()}} but invalid at computed
122-
value time. Initial values that are not computationally idempotent must also cause
122+
value time. Initial values that are not computationally idempotent must also cause
123123
{{registerProperty()}} to throw a {{SyntaxError}}.
124124

125125
<div class='example'>
126126
For example, "3cm" is a computationally idempotent length, and hence valid as an initial value.
127127
However, "3em" is not (depending on the environment, 3em could compute to
128-
multiple different values). Additionally, "var(--foo)" is not computationally idempotent.
128+
multiple different values). Additionally, "var(--foo)" is not computationally idempotent.
129129
</div>
130130

131131
Issue: define computational idempotency.
132132

133133
Issue(121): Is computational idempotency the right thing to do here? We could also just
134-
resolve any relative values once (against all the other initial values) and use
134+
resolve any relative values once (against all the other initial values) and use
135135
that. OR! We could allow specified values and just fix our engines...
136136

137137
When a custom property is registered with a given type, the process via which specified
@@ -160,7 +160,7 @@ are valid. Hence, the result of this stylesheet:
160160
<pre class='lang-css'>
161161
.thing {
162162
--my-color: green;
163-
--my-color: url("not-a-color");
163+
--my-color: url("not-a-color");
164164
color: var(--my-color);
165165
}
166166
</pre>
@@ -317,7 +317,7 @@ this is standard across implementations to avoid interop issues.
317317
Conditional Rules {#conditional-rules}
318318
--------------------------------------
319319

320-
@supports rules and the <a method for=CSS>supports()</a> method behave as specified
320+
''@supports'' rules and the {{CSS/supports(conditionText)}} method behave as specified
321321
in [[!css-variables]].
322322

323323
Note: In other words, for the purpose of determining whether a value is
@@ -357,3 +357,13 @@ CSS.registerProperty({
357357
&lt;/style&gt;
358358

359359
</pre>
360+
361+
Security Considerations {#security-considerations}
362+
==================================================
363+
364+
There are no known security issues introduced by these features.
365+
366+
Privacy Considerations {#privacy-considerations}
367+
==================================================
368+
369+
There are no known privacy issues introduced by these features.

‎css-typed-om/Overview.bs‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
<pre class='metadata'>
22
Title: CSS Typed OM Level 1
33
Status: FPWD
4-
Date: 2016-05-17
4+
Date: 2016-05-24
55
Group: houdini
66
ED: https://drafts.css-houdini.org/css-typed-om-1/
77
Shortname: css-typed-om
@@ -1259,7 +1259,7 @@ any sub-process referenced by this process fails, then normalization as a whole
12591259
1. if the provided value starts with a keyword followed by a length, percentage, or calc expression, then follow
12601260
the procedure outlined in <a section href="#from-keyword-and-length"></a> with <var>keyword</var> set to the
12611261
keyword, <var>length</var> set to the length, percentage, or calc expression, and auto <var>bias</var>.
1262-
1. otherwise, follow the procedure outlined in <a section href="from-single-keyword"></a> with <var>value</var>
1262+
1. otherwise, follow the procedure outlined in <a section href="#from-single-keyword"></a> with <var>value</var>
12631263
set to the first component of the provided value and an auto <var>bias</var>.
12641264
1. if <var>bias</var> is horizontal, set it to vertical. Otherwise, set it to horizontal.
12651265
1. if the remainder of the provided value is a single keyword, length, percentage or calc expression, follow

‎default.css‎

Lines changed: 157 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,157 @@
1+
/*
2+
* Style sheet for the CSS3 specification,
3+
* to be used in addition to https://www.w3.org/StyleSheets/TR/W3C-{WD,PR,REC}
4+
*/
5+
6+
@import "https://www.w3.org/StyleSheets/TR/2016/base.css";
7+
8+
/** Example Code **************************************************************/
9+
10+
div.html, div.xml,
11+
pre.html, pre.xml {
12+
padding: 0.5em;
13+
margin: 1em 0;
14+
position: relative;
15+
clear: both;
16+
color: #600;
17+
}
18+
pre.example,
19+
pre.html,
20+
pre.xml {
21+
padding-top: 1.5em;
22+
}
23+
24+
pre.illegal, .illegal pre
25+
pre.deprecated, .deprecated pre {
26+
color: red;
27+
}
28+
29+
/** Inline markup fragments ***************************************************/
30+
31+
code.html, code.xml {
32+
color: #660000;
33+
}
34+
35+
/******************************************************************************/
36+
/* Images */
37+
/******************************************************************************/
38+
39+
pre.ascii-art {
40+
display: table; /* shrinkwrap */
41+
margin: 1em auto;
42+
}
43+
44+
/* Displaying the output of text layout, particularly when
45+
line-breaking is being invoked, and thus having a
46+
visible width is good. */
47+
pre.output {
48+
margin: 1em;
49+
border: solid thin silver;
50+
padding: 0.25em;
51+
display: table;
52+
}
53+
54+
/******************************************************************************/
55+
/* Tables */
56+
/******************************************************************************/
57+
58+
/* XXX: Remove these once all specs are bikeshedded or Bert's processor generates .def/.index classes */
59+
60+
/** Property/Descriptor Definition Tables *************************************/
61+
62+
table.propdef, table.propdef-extra,
63+
table.descdef, table.definition-table {
64+
page-break-inside: avoid;
65+
width: 100%;
66+
margin: 1.2em 0;
67+
border-left: 0.5em solid #8CCBF2;
68+
padding: 0.5em 1em;
69+
background: #DEF;
70+
border-spacing: 0;
71+
}
72+
73+
table.propdef td, table.propdef-extra td,
74+
table.descdef td, table.definition-table td,
75+
table.propdef th, table.propdef-extra th,
76+
table.descdef th, table.definition-table th {
77+
padding: 0.5em;
78+
vertical-align: baseline;
79+
border-bottom: 1px solid #bbd7e9;
80+
}
81+
table.propdef > tbody > tr:last-child th,
82+
table.propdef-extra > tbody > tr:last-child th,
83+
table.descdef > tbody > tr:last-child th,
84+
table.definition-table > tbody > tr:last-child th,
85+
table.propdef > tbody > tr:last-child td,
86+
table.propdef-extra > tbody > tr:last-child td,
87+
table.descdef > tbody > tr:last-child td,
88+
table.definition-table > tbody > tr:last-child td {
89+
border-bottom: 0;
90+
}
91+
92+
table.propdef th,
93+
table.propdef-extra th,
94+
table.descdef th,
95+
table.definition-table th {
96+
font-style: italic;
97+
font-weight: normal;
98+
width: 8.3em;
99+
padding-left: 1em;
100+
}
101+
102+
/* For when values are extra-complex and need formatting for readability */
103+
table td.pre {
104+
white-space: pre-wrap;
105+
}
106+
107+
/* A footnote at the bottom of a propdef */
108+
table.propdef td.footnote,
109+
table.propdef-extra td.footnote,
110+
table.descdef td.footnote,
111+
table.definition-table td.footnote {
112+
padding-top: 0.6em;
113+
}
114+
table.propdef td.footnote::before,
115+
table.propdef-extra td.footnote::before,
116+
table.descdef td.footnote::before,
117+
table.definition-table td.footnote::before {
118+
content: " ";
119+
display: block;
120+
height: 0.6em;
121+
width: 4em;
122+
border-top: thin solid;
123+
}
124+
125+
/** Profile Tables ************************************************************/
126+
/* table of required features in a CSS profile */
127+
128+
table.features th {
129+
background: #00589f;
130+
color: #fff;
131+
text-align: left;
132+
padding: 0.2em 0.2em 0.2em 0.5em;
133+
}
134+
table.features td {
135+
vertical-align: top;
136+
border-bottom: 1px solid #ccc;
137+
padding: 0.3em 0.3em 0.3em 0.7em;
138+
}
139+
140+
/** At-risk List **************************************************************/
141+
/* Style for At Risk features (intended as editorial aid, not intended for publishing) */
142+
143+
.atrisk::before {
144+
float: right;
145+
margin-top: -0.25em;
146+
padding: 0.5em 1em 0.5em 0;
147+
text-indent: -0.9em;
148+
border: 1px solid;
149+
content: '\25C0 Not yet widely implemented';
150+
white-space: pre;
151+
font-size: small;
152+
background-color: white;
153+
color: gray;
154+
text-align: center;
155+
}
156+
157+
.toc .atrisk::before { content:none }

0 commit comments

Comments
 (0)