Cascading Style Sheets (CSS) Working Group - Activity in 2015
No matches.
TR publications
-
3 documents published.
-
CSS Writing Modes Level 3 published as a Candidate Recommendation Snapshot. History of CSS Writing Modes Level 3
-
CSS Custom Properties for Cascading Variables Module Level 1 published as a Candidate Recommendation Snapshot. History of CSS Custom Properties for Cascading Variables Module Level 1
-
CSS Will Change Module Level 1 published as a Candidate Recommendation Snapshot. History of CSS Will Change Module Level 1
-
Participants
-
1 participant joined.
-
Thierry Michel (W3C) joined.
-
-
1 organization joined.
-
HP Inc. joined.
-
GitHub
w3c/csswg-drafts
-
2 issues opened.
-
[css-syntax][selectors] Clarify handling of invalid selectors in css-syntax. w3c/csswg-drafts#85, by @Ms2ger.
-
Pardon (about CSS4 images `element`) w3c/csswg-drafts#84, by @ghost.
-
-
1 issue closed.
-
Pardon (about CSS4 images `element`) w3c/csswg-drafts#84.
-
-
2 issues received 3 new comments.
-
[css-syntax][selectors] Clarify handling of invalid selectors in css-syntax. w3c/csswg-drafts#85 (2 comments by @SimonSapin, @tabatkins)
-
-
4 pull requests opened.
-
[css-page-floats] synchronize 3.2 with 8.2 w3c/csswg-drafts#83, by @johanneswilm.
-
[css-device-adapt] Add missing closing curly-brace to UA stylesheet w3c/csswg-drafts#82, by @cvrebert.
-
[cssom-view] Add more positioning control to scrollIntoView w3c/csswg-drafts#81, by @zcorpan.
-
Fix Bikeshed linkification w3c/csswg-drafts#80, by @mathiasbynens.
-
-
3 pull requests merged.
-
[css-page-floats] synchronize 3.2 with 8.2 w3c/csswg-drafts#83.
-
[cssom-view] Add more positioning control to scrollIntoView w3c/csswg-drafts#81.
-
[css-device-adapt] Add missing closing curly-brace to UA stylesheet w3c/csswg-drafts#82.
-
-
1 pull request closed.
-
Fix Bikeshed linkification w3c/csswg-drafts#80.
-
-
3 pull requests received 3 new comments.
-
[cssom-view] Add more positioning control to scrollIntoView w3c/csswg-drafts#81 (1 comment by @zcorpan)
-
[css-device-adapt] Add missing closing curly-brace to UA stylesheet w3c/csswg-drafts#82 (1 comment by @frivoal)
-
w3c/IntersectionObserver
-
2 issues opened.
-
rootBounds when root is cross-origin w3c/IntersectionObserver#79, by @szager-chromium.
-
intersectionObserver.observe() edge cases w3c/IntersectionObserver#78, by @zetafunction.
-
-
5 issues closed.
-
Natural viewport is a confusing name. w3c/IntersectionObserver#17.
-
intersectionObserver.observe() edge cases w3c/IntersectionObserver#78.
-
Explainer is out of date w3c/IntersectionObserver#49.
-
Queueing intersection observer tasks is pretty underdefined w3c/IntersectionObserver#54.
-
IntersectionObserver needs accessors for the IntersectionObserverInit values with which it was constructed w3c/IntersectionObserver#63.
-
-
4 issues received 8 new comments.
-
What happens when an observation is started for a target which is already intersecting? w3c/IntersectionObserver#73 (4 comments by @mpb, @ojanvafai, @tabatkins)
-
Define the document scope of an observer w3c/IntersectionObserver#74 (2 comments by @mpb, @tabatkins)
-
intersectionObserver.observe() edge cases w3c/IntersectionObserver#78 (1 comment by @szager-chromium)
-
-
3 pull requests opened.
-
Bring explainer up to date. w3c/IntersectionObserver#77, by @szager-chromium.
-
Fix some typos in explainer.md w3c/IntersectionObserver#76, by @cpeterso.
-
grammar typo fix (Changes...is --> Changes...are) w3c/IntersectionObserver#75, by @dholbert.
-
-
4 pull requests merged.
-
Bring explainer up to date. w3c/IntersectionObserver#77.
-
Fix some typos in explainer.md w3c/IntersectionObserver#76.
-
Support multiple IntersectionObservers for a single target Element, add attributes and update algorithm. w3c/IntersectionObserver#71.
-
grammar typo fix (Changes...is --> Changes...are) w3c/IntersectionObserver#75.
-
-
2 pull requests received 4 new comments.
-
Support multiple IntersectionObservers for a single target Element, add attributes and update algorithm. w3c/IntersectionObserver#71 (1 comment by @mpb)
w3c/css-houdini-drafts
-
11 issues opened.
-
Worklets: Security considerations? w3c/css-houdini-drafts#92, by @mikewest.
-
[unofficial] Reconstruction of advanced CSS Houdini example w3c/css-houdini-drafts#91, by @ghost.
-
[questions] Right or Lie about CSS Houdini? w3c/css-houdini-drafts#90, by @ghost.
-
Questions about CSS Houdini? w3c/css-houdini-drafts#89, by @ghost.
-
[isolated-workers] JavaScript context and communication w3c/css-houdini-drafts#88, by @ghost.
-
Thinking about... w3c/css-houdini-drafts#87, by @ghost.
-
Why is CSS extended in JavaScript files instead of in CSS files? w3c/css-houdini-drafts#86, by @chriseppstein.
-
StyleValue.parse() should also allow no validation w3c/css-houdini-drafts#85, by @therealglazou.
-
Sequence<StyleValue> misses information about comma w3c/css-houdini-drafts#84, by @therealglazou.
-
CompoundStyleValue needed w3c/css-houdini-drafts#83, by @therealglazou.
-
Why is getImageData not allowed? w3c/css-houdini-drafts#82, by @cabanier.
-
-
4 issues closed.
-
[unofficial] Reconstruction of advanced CSS Houdini example w3c/css-houdini-drafts#91.
-
Questions about CSS Houdini? w3c/css-houdini-drafts#89.
-
[isolated-workers] JavaScript context and communication w3c/css-houdini-drafts#88.
-
Thinking about... w3c/css-houdini-drafts#87.
-
-
13 issues received 36 new comments.
-
Why is getImageData not allowed? w3c/css-houdini-drafts#82 (8 comments by @bfgeek, @cabanier, @ghost, @tabatkins)
-
[isolated-workers] Add console API to IsolatedWorkerGlobalScope w3c/css-houdini-drafts#15 (4 comments by @domenic, @robertkowalski, @terinjokes)
-
Why is CSS extended in JavaScript files instead of in CSS files? w3c/css-houdini-drafts#86 (4 comments by @FremyCompany, @tabatkins, @therealglazou)
-
[questions] Right or Lie about CSS Houdini? w3c/css-houdini-drafts#90 (3 comments by @FremyCompany, @ghost, @myakura)
-
[css-paint-api] Allow authors to create additional CanvasRenderingContexts to allow for caching. w3c/css-houdini-drafts#34 (3 comments by @bfgeek, @tabatkins)
-
StyleValue.parse() should also allow no validation w3c/css-houdini-drafts#85 (3 comments by @FremyCompany, @tabatkins)
-
[css-paint-api] Create PaintRenderingContext2D which is a subset of the CanvasRenderingContext2D. w3c/css-houdini-drafts#20 (2 comments by @bfgeek)
-
[isolated-workers] JavaScript context and communication w3c/css-houdini-drafts#88 (2 comments by @ghost, @tabatkins)
-
[unofficial] Reconstruction of advanced CSS Houdini example w3c/css-houdini-drafts#91 (1 comment by @ghost)
-
Sequence<StyleValue> misses information about comma w3c/css-houdini-drafts#84 (1 comment by @tabatkins)
-
TR publications
-
1 document published.
-
CSS Device Adaptation Module Level 1 published as a Working Draft. History of CSS Device Adaptation Module Level 1
-
Participants
-
1 organization left.
-
Cox Communications, Inc. left.
-
GitHub
w3c/css-houdini-drafts
-
2 issues opened.
-
getComputedStyleMap is on document, but getComputedStyle is on window w3c/css-houdini-drafts#81, by @wilddamon.
-
Rotation components take a double angle w3c/css-houdini-drafts#80, by @shans.
-
-
5 issues closed.
-
[css-properties-values-api] StyleWorklet should inherit from WorkletGlobalContext w3c/css-houdini-drafts#71.
-
[css-properties-values-api] Need a <length-percentage> syntax. w3c/css-houdini-drafts#70.
-
[css-properties-values-api] Syntax strings referencing existing properties using incorrect grammar. w3c/css-houdini-drafts#68.
-
[css-properties-values-api] <number> and <percentage> should indicate that calcs get computed out. w3c/css-houdini-drafts#69.
-
-
1 issue received 1 new comment.
-
[css-properties-values-api] Calls to registerProperty() and unregisterProperty() should not trigger a CSS reparse w3c/css-houdini-drafts#63 (1 comment by @shans)
-
w3c/IntersectionObserver
-
8 issues opened.
-
Define the document scope of an observer w3c/IntersectionObserver#74, by @szager-chromium.
-
What happens when an observation is started for a target which is already intersecting? w3c/IntersectionObserver#73, by @mpb.
-
Need to define actual syntax for rootMargin w3c/IntersectionObserver#72, by @mpb.
-
Clarify how clipping is computed when rootMargin is set w3c/IntersectionObserver#70, by @szager-chromium.
-
How should zero-dimension targets be handled? w3c/IntersectionObserver#69, by @szager-chromium.
-
Require root and target to be Elements (no text nodes) w3c/IntersectionObserver#68, by @szager-chromium.
-
Can observer root and target span different frames that are same-origin? w3c/IntersectionObserver#66, by @szager-chromium.
-
If a root is removed from the DOM and reinserted, should its observations remain intact? w3c/IntersectionObserver#65, by @szager-chromium.
-
-
12 issues closed.
-
viewport rect should be the intersection of ancestor scrollers w3c/IntersectionObserver#22.
-
Figure out how to enforce that observed element is a descendant of the viewport element w3c/IntersectionObserver#16.
-
Support multiple observers on a single target Element w3c/IntersectionObserver#57.
-
spec needs to be clear on the timing of the callback w3c/IntersectionObserver#23.
-
viewportmodifier should allow negative values w3c/IntersectionObserver#27.
-
If a root is removed from the DOM and reinserted, should its observations remain intact? w3c/IntersectionObserver#65.
-
Require root and target to be Elements (no text nodes) w3c/IntersectionObserver#68.
-
Need to define handling of relative units for `threshold` w3c/IntersectionObserver#53.
-
Add a link to the spec to the GitHub repo w3c/IntersectionObserver#41.
-
The requirement for target to be a descendant of [[root]] seems to ignore mutations w3c/IntersectionObserver#50.
-
The observer object is passed twice to callbacks w3c/IntersectionObserver#61.
-
Nit: use <var> for variables, not <i> w3c/IntersectionObserver#48.
-
-
1 issue reopened.
-
Specify ownership and lifetime of IntersectionObservers w3c/IntersectionObserver#64, by @ojanvafai.
-
-
21 issues received 34 new comments.
-
What should happen if the viewport-defining element is an inline? w3c/IntersectionObserver#13 (4 comments by @ojanvafai, @szager-chromium, @tabatkins)
-
Don't call public API methods; instead call their backing algorithms w3c/IntersectionObserver#55 (3 comments by @mpb, @ojanvafai)
-
IntersectionObserver needs accessors for the IntersectionObserverInit values with which it was constructed w3c/IntersectionObserver#63 (3 comments by @mpb, @ojanvafai, @szager-chromium)
-
Remove auto-unobserving. Instead have active and inactive observations. w3c/IntersectionObserver#58 (3 comments by @mpb, @ojanvafai, @szager-chromium)
-
Need to define actual syntax for rootMargin w3c/IntersectionObserver#72 (2 comments by @mpb, @szager-chromium)
-
Queueing intersection observer tasks is pretty underdefined w3c/IntersectionObserver#54 (2 comments by @mpb, @ojanvafai)
-
Clarify how clipping is computed when rootMargin is set w3c/IntersectionObserver#70 (2 comments by @ojanvafai, @szager-chromium)
-
Specify ownership and lifetime of IntersectionObservers w3c/IntersectionObserver#64 (2 comments by @ojanvafai, @szager-chromium)
-
What happens when an observation is started for a target which is already intersecting? w3c/IntersectionObserver#73 (1 comment by @ojanvafai)
-
viewport rect should be the intersection of ancestor scrollers w3c/IntersectionObserver#22 (1 comment by @szager-chromium)
-
Figure out how to enforce that observed element is a descendant of the viewport element w3c/IntersectionObserver#16 (1 comment by @szager-chromium)
-
spec needs to be clear on the timing of the callback w3c/IntersectionObserver#23 (1 comment by @mpb)
-
rootBounds leaks information in the cross-origin case w3c/IntersectionObserver#52 (1 comment by @szager-chromium)
-
If a root is removed from the DOM and reinserted, should its observations remain intact? w3c/IntersectionObserver#65 (1 comment by @ojanvafai)
-
Can observer root and target span different frames that are same-origin? w3c/IntersectionObserver#66 (1 comment by @ojanvafai)
-
Require root and target to be Elements (no text nodes) w3c/IntersectionObserver#68 (1 comment by @ojanvafai)
-
Support multiple observers on a single target Element w3c/IntersectionObserver#57 (1 comment by @mpb)
-
Need to define handling of relative units for `threshold` w3c/IntersectionObserver#53 (1 comment by @mpb)
-
The requirement for target to be a descendant of [[root]] seems to ignore mutations w3c/IntersectionObserver#50 (1 comment by @mpb)
-
-
2 pull requests opened.
-
Support multiple IntersectionObservers for a single target Element, add attributes and update algorithm. w3c/IntersectionObserver#71, by @mpb.
-
-
2 pull requests merged.
-
s/i/var/g w3c/IntersectionObserver#67.
-
Update 'Threshold' to be a (double or sqeuence<double>) w3c/IntersectionObserver#60.
-
-
1 pull request received 1 new comment.
-
Update 'Threshold' to be a (double or sqeuence<double>) w3c/IntersectionObserver#60 (1 comment by @ojanvafai)
-
w3c/csswg-drafts
-
3 pull requests opened.
-
[css-page-floats] add names to input list w3c/csswg-drafts#79, by @johanneswilm.
-
-
3 pull requests merged.
-
[css-page-floats] add names to input list w3c/csswg-drafts#79.
-
TR publications
-
2 documents published.
-
CSS Display Module Level 3 published as a Working Draft. History of CSS Display Module Level 3
-
CSS Snapshot 2015 published as a Note. History of CSS Snapshot 2015
-
Participants
-
1 participant left.
-
Florian Rivoal (W3C Invited Experts) left.
-
GitHub
w3c/IntersectionObserver
-
28 issues opened.
-
Specify ownership and lifetime of IntersectionObservers w3c/IntersectionObserver#64, by @szager-chromium.
-
IntersectionObserver needs accessors for the IntersectionObserverInit values with which it was constructed w3c/IntersectionObserver#63, by @szager-chromium.
-
properly spec clip rect w3c/IntersectionObserver#62, by @ojanvafai.
-
The observer object is passed twice to callbacks w3c/IntersectionObserver#61, by @szager-chromium.
-
Make sure that time basis and types are lined up with Frame Timing w3c/IntersectionObserver#59, by @slightlyoff.
-
Remove auto-unobserving. Instead have active and inactive observations. w3c/IntersectionObserver#58, by @szager-chromium.
-
Support multiple observers on a single target Element w3c/IntersectionObserver#57, by @szager-chromium.
-
setting rootMargin when root is null should throw w3c/IntersectionObserver#56, by @ojanvafai.
-
Don't call public API methods; instead call their backing algorithms w3c/IntersectionObserver#55, by @domenic.
-
Queueing intersection observer tasks is pretty underdefined w3c/IntersectionObserver#54, by @bzbarsky.
-
Need to define handling of relative units for `threshold` w3c/IntersectionObserver#53, by @bzbarsky.
-
rootBounds leaks information in the cross-origin case w3c/IntersectionObserver#52, by @bzbarsky.
-
Definition of `IntersectionObserverEntry.time` needs to say what the zero time is w3c/IntersectionObserver#51, by @bzbarsky.
-
The requirement for target to be a descendant of [[root]] seems to ignore mutations w3c/IntersectionObserver#50, by @bzbarsky.
-
Explainer is out of date w3c/IntersectionObserver#49, by @AdamTReineke.
-
Nit: use <var> for variables, not <i> w3c/IntersectionObserver#48, by @domenic.
-
[[RegisteredIntersectionObservers]] setup is broken w3c/IntersectionObserver#43, by @domenic.
-
Add a link to the spec to the GitHub repo w3c/IntersectionObserver#41, by @domenic.
-
The properties installed on other objects are named too generically w3c/IntersectionObserver#39, by @domenic.
-
The IntersectionObserverEntryList typedef serves to obfuscate and indirect, not clarify w3c/IntersectionObserver#38, by @domenic.
-
Why the slight differences from MutationObserver? w3c/IntersectionObserver#37, by @domenic.
-
Why is this Exposed=(Window,Worker) when Elements aren't exposed to Workers? w3c/IntersectionObserver#36, by @domenic.
-
Use of undefined variable "Document" throughout w3c/IntersectionObserver#35, by @domenic.
-
Use of dot notation is a bit confusing w3c/IntersectionObserver#34, by @domenic.
-
IntersectionObserverEntry should have a constructor w3c/IntersectionObserver#33, by @domenic.
-
DOMRectReadOnly is probably more appropriate than DOMRect w3c/IntersectionObserver#32, by @domenic.
-
IntersectionObserver's second argument must be optional w3c/IntersectionObserver#31, by @domenic.
-
Clicking on "Element" goes to a javadoc, not the DOM spec w3c/IntersectionObserver#30, by @domenic.
-
-
13 issues closed.
-
Make sure that time basis and types are lined up with Frame Timing w3c/IntersectionObserver#59.
-
setting rootMargin when root is null should throw w3c/IntersectionObserver#56.
-
Use of undefined variable "Document" throughout w3c/IntersectionObserver#35.
-
[[RegisteredIntersectionObservers]] setup is broken w3c/IntersectionObserver#43.
-
Why the slight differences from MutationObserver? w3c/IntersectionObserver#37.
-
The IntersectionObserverEntryList typedef serves to obfuscate and indirect, not clarify w3c/IntersectionObserver#38.
-
IntersectionObserverEntry should have a constructor w3c/IntersectionObserver#33.
-
DOMRectReadOnly is probably more appropriate than DOMRect w3c/IntersectionObserver#32.
-
Why is this Exposed=(Window,Worker) when Elements aren't exposed to Workers? w3c/IntersectionObserver#36.
-
IntersectionObserver's second argument must be optional w3c/IntersectionObserver#31.
-
The properties installed on other objects are named too generically w3c/IntersectionObserver#39.
-
Use of dot notation is a bit confusing w3c/IntersectionObserver#34.
-
Clicking on "Element" goes to a javadoc, not the DOM spec w3c/IntersectionObserver#30.
-
-
24 issues received 93 new comments.
-
rootBounds leaks information in the cross-origin case w3c/IntersectionObserver#52 (26 comments by @bzbarsky, @mpb, @ojanvafai, @tabatkins)
-
Need to define handling of relative units for `threshold` w3c/IntersectionObserver#53 (11 comments by @bzbarsky, @mpb, @ojanvafai, @tabatkins)
-
DOMRectReadOnly is probably more appropriate than DOMRect w3c/IntersectionObserver#32 (6 comments by @domenic, @mpb, @ojanvafai)
-
Definition of `IntersectionObserverEntry.time` needs to say what the zero time is w3c/IntersectionObserver#51 (5 comments by @bzbarsky, @domenic, @igrigorik, @ojanvafai)
-
The requirement for target to be a descendant of [[root]] seems to ignore mutations w3c/IntersectionObserver#50 (5 comments by @bzbarsky, @domenic, @mpb)
-
IntersectionObserverEntry should have a constructor w3c/IntersectionObserver#33 (5 comments by @domenic, @mpb)
-
Clicking on "Element" goes to a javadoc, not the DOM spec w3c/IntersectionObserver#30 (5 comments by @domenic, @mpb)
-
[[RegisteredIntersectionObservers]] setup is broken w3c/IntersectionObserver#43 (4 comments by @annevk, @domenic, @mpb)
-
Why the slight differences from MutationObserver? w3c/IntersectionObserver#37 (4 comments by @domenic, @mpb)
-
Queueing intersection observer tasks is pretty underdefined w3c/IntersectionObserver#54 (3 comments by @bzbarsky, @ojanvafai)
-
Remove auto-unobserving. Instead have active and inactive observations. w3c/IntersectionObserver#58 (2 comments by @ojanvafai, @szager-chromium)
-
Make sure that time basis and types are lined up with Frame Timing w3c/IntersectionObserver#59 (2 comments by @ojanvafai)
-
Use of undefined variable "Document" throughout w3c/IntersectionObserver#35 (2 comments by @domenic, @mpb)
-
Support multiple observers on a single target Element w3c/IntersectionObserver#57 (1 comment by @mpb)
-
The IntersectionObserverEntryList typedef serves to obfuscate and indirect, not clarify w3c/IntersectionObserver#38 (1 comment by @mpb)
-
Why is this Exposed=(Window,Worker) when Elements aren't exposed to Workers? w3c/IntersectionObserver#36 (1 comment by @mpb)
-
IntersectionObserver's second argument must be optional w3c/IntersectionObserver#31 (1 comment by @mpb)
-
The properties installed on other objects are named too generically w3c/IntersectionObserver#39 (1 comment by @domenic)
-
-
7 pull requests opened.
-
Update 'Threshold' to be a (double or sqeuence<double>) w3c/IntersectionObserver#60, by @mpb.
-
Processing model re-write based on MutationObserver. w3c/IntersectionObserver#47, by @mpb.
-
added notes for MutationObserver differences w3c/IntersectionObserver#46, by @mpb.
-
IntersectionObserverEntryList -> sequence<IntersectionObserverEntry> w3c/IntersectionObserver#45, by @mpb.
-
Add constructor for IntersectionObserverEntry w3c/IntersectionObserver#44, by @mpb.
-
Update 'exposed' attribute for IntersectionObserver w3c/IntersectionObserver#42, by @mpb.
-
Make Bikeshed version of spec primary w3c/IntersectionObserver#40, by @mpb.
-
-
6 pull requests merged.
-
Processing model re-write based on MutationObserver. w3c/IntersectionObserver#47.
-
added notes for MutationObserver differences w3c/IntersectionObserver#46.
-
IntersectionObserverEntryList -> sequence<IntersectionObserverEntry> w3c/IntersectionObserver#45.
-
Add constructor for IntersectionObserverEntry w3c/IntersectionObserver#44.
-
Update 'exposed' attribute for IntersectionObserver w3c/IntersectionObserver#42.
-
Make Bikeshed version of spec primary w3c/IntersectionObserver#40.
-
-
3 pull requests received 58 new comments.
-
Processing model re-write based on MutationObserver. w3c/IntersectionObserver#47 (53 comments by @domenic, @mpb, @tabatkins)
-
Update 'Threshold' to be a (double or sqeuence<double>) w3c/IntersectionObserver#60 (2 comments by @mpb, @ojanvafai)
-
w3c/css-houdini-drafts
-
33 issues opened.
-
[css-properties-values-api] Need to resolve computation/animation/substitution order for typed properties w3c/css-houdini-drafts#79, by @shans.
-
[css-properties-values-api] Ensure there's informative note about parallel nature of processing apply hooks. w3c/css-houdini-drafts#78, by @shans.
-
[css-properties-values-api] Fix example and add a new one. w3c/css-houdini-drafts#77, by @shans.
-
[css-properties-values-api] Add recommendation to use var() where possible to introduction w3c/css-houdini-drafts#76, by @shans.
-
[css-properties-values-api] Add note to indicate that it's conformant to memoize. w3c/css-houdini-drafts#75, by @shans.
-
[css-properties-values-api] ElementProxy needs a better name. w3c/css-houdini-drafts#74, by @shans.
-
[css-properties-values-api] Not sure whether there should be a pseudo reference on ElementProxy. w3c/css-houdini-drafts#73, by @shans.
-
[css-properties-values-api] ElementProxy shouldn't reference tagName, classList, id. w3c/css-houdini-drafts#72, by @shans.
-
[css-properties-values-api] StyleWorklet should inherit from WorkletGlobalContext w3c/css-houdini-drafts#71, by @shans.
-
[css-properties-values-api] Need a <length-percentage> syntax. w3c/css-houdini-drafts#70, by @shans.
-
[css-properties-values-api] <number> and <percentage> should indicate that calcs get computed out. w3c/css-houdini-drafts#69, by @shans.
-
[css-properties-values-api] Syntax strings referencing existing properties using incorrect grammar. w3c/css-houdini-drafts#68, by @shans.
-
[css-properties-values-api] More formal description of registerProperty required w3c/css-houdini-drafts#67, by @shans.
-
Need to prefix the Translate, Scale, etc. constructors w3c/css-houdini-drafts#66, by @shans.
-
Matrix components should not be called a,b,c,d,e... w3c/css-houdini-drafts#65, by @shans.
-
[css-paint-api] Add that you can't be killed within a frame. w3c/css-houdini-drafts#64, by @bfgeek.
-
[css-properties-values-api] Calls to registerProperty() and unregisterProperty() should not trigger a CSS reparse w3c/css-houdini-drafts#63, by @astearns.
-
[css-properties-values-api] Draft should be explicit that a property-name syntax definition allows custom properties w3c/css-houdini-drafts#62, by @astearns.
-
[isolated-workers] Fix throwing error in #importScripts, instead reject. w3c/css-houdini-drafts#61, by @bfgeek.
-
[isolated-workers] Fix settingsObject passing into "create an isolated script". w3c/css-houdini-drafts#60, by @bfgeek.
-
[isolated-workers] Fix "get a fetch result". w3c/css-houdini-drafts#59, by @bfgeek.
-
[css-typed-om] CalcLength isn't sufficient to represent css-values-4 calc() w3c/css-houdini-drafts#57, by @dbaron.
-
[isolated-workers] The event loop infrastructure of HTML is too tied to a normal processing model w3c/css-houdini-drafts#56, by @padenot.
-
[isolated-workers] Base 64 functions ? w3c/css-houdini-drafts#55, by @padenot.
-
[isolated-workers] Code Idempotency w3c/css-houdini-drafts#54, by @padenot.
-
[isolated-workers] Have ability to call dispose on classes when destroyed for v1? w3c/css-houdini-drafts#53, by @bfgeek.
-
[isolated-workers] Do we need the ability of importScripts (plural) should it just be importScript? w3c/css-houdini-drafts#52, by @bfgeek.
-
[isolated-workers] What should happen when a script throws an error upon first run? w3c/css-houdini-drafts#51, by @bfgeek.
-
Should registerProperty/unregisterProperty be on CSS or Document? w3c/css-houdini-drafts#50, by @shans.
-
Consider supporting existing CSS Property parsings w3c/css-houdini-drafts#48, by @shans.
-
[worklets] Create ability for code to be loaded into worklets declaratively. w3c/css-houdini-drafts#47, by @bfgeek.
-
[css-async-style] CompositorWorker use cases w3c/css-houdini-drafts#46, by @ianvollick.
-
-
18 issues closed.
-
[css-properties-values-api] ElementProxy shouldn't reference tagName, classList, id. w3c/css-houdini-drafts#72.
-
[css-properties-values-api] Add note to indicate that it's conformant to memoize. w3c/css-houdini-drafts#75.
-
[css-properties-values-api] Add recommendation to use var() where possible to introduction w3c/css-houdini-drafts#76.
-
[css-paint-api] Add function to paint class which computes the overflow for the element. w3c/css-houdini-drafts#28.
-
[css-paint-api] Add to spec if fragment has available overflow where rendering context places 0x0. w3c/css-houdini-drafts#29.
-
[css-paint-api] Add note to spec that 3d effects will be in lvl2. w3c/css-houdini-drafts#30.
-
[css-paint-api] Add ability for custom paint class to run an "initialization" step. w3c/css-houdini-drafts#25.
-
[css-paint-api] Add note of what UA behavior should be for long running paint functions. w3c/css-houdini-drafts#36.
-
[css-paint-api] Ed Issue: Make note that the contents of custom paint are not accessible. w3c/css-houdini-drafts#21.
-
[css-paint-api] Need to define the initial state of the canvas in the spec. w3c/css-houdini-drafts#13.
-
Specify what happens when an exception is throw during a paint callback. w3c/css-houdini-drafts#9.
-
Calling registerPaint with the same name more than once should throw. w3c/css-houdini-drafts#7.
-
[css-paint-api] Add note that setting global alpha, clip, etc may be in a future level of the spec. w3c/css-houdini-drafts#37.
-
Can property names be a type accepted by the syntax for custom properties? w3c/css-houdini-drafts#10.
-
Should registerProperty/unregisterProperty be on CSS or Document? w3c/css-houdini-drafts#50.
-
Should define the pre-apply computed value for each type that is supported. w3c/css-houdini-drafts#1.
-
[isolated-workers] Add isolated worker ED to repository. w3c/css-houdini-drafts#14.
-
-
27 issues received 44 new comments.
-
Should registerProperty/unregisterProperty be on CSS or Document? w3c/css-houdini-drafts#50 (4 comments by @frivoal, @shans)
-
[scrolling] Examples of interesting Scroll Effects w3c/css-houdini-drafts#45 (4 comments by @grorg, @RByers)
-
[isolated-workers] Specify what happens when a script in an isolated worker throws an error. w3c/css-houdini-drafts#16 (4 comments by @bfgeek, @padenot)
-
[isolated-workers] Have ability to call dispose on classes when destroyed for v1? w3c/css-houdini-drafts#53 (3 comments by @bfgeek, @domenic, @esprehn)
-
[isolated-workers] The event loop infrastructure of HTML is too tied to a normal processing model w3c/css-houdini-drafts#56 (3 comments by @domenic, @FremyCompany, @rocallahan)
-
[isolated-workers] Add console API to IsolatedWorkerGlobalScope w3c/css-houdini-drafts#15 (3 comments by @bfgeek, @domenic, @terinjokes)
-
[css-properties-values-api] Calls to registerProperty() and unregisterProperty() should not trigger a CSS reparse w3c/css-houdini-drafts#63 (2 comments by @astearns, @shans)
-
[css-properties-values-api] Need to resolve computation/animation/substitution order for typed properties w3c/css-houdini-drafts#79 (1 comment by @shans)
-
[css-properties-values-api] Add note to indicate that it's conformant to memoize. w3c/css-houdini-drafts#75 (1 comment by @shans)
-
[css-paint-api] Add function to paint class which computes the overflow for the element. w3c/css-houdini-drafts#28 (1 comment by @bfgeek)
-
[css-paint-api] Add to spec if fragment has available overflow where rendering context places 0x0. w3c/css-houdini-drafts#29 (1 comment by @bfgeek)
-
[css-paint-api] Add note to spec that 3d effects will be in lvl2. w3c/css-houdini-drafts#30 (1 comment by @bfgeek)
-
[css-paint-api] Add ability for custom paint class to run an "initialization" step. w3c/css-houdini-drafts#25 (1 comment by @bfgeek)
-
[css-paint-api] Add note in spec that partial invalidation of a fragment may be added in a future version of the spec. w3c/css-houdini-drafts#35 (1 comment by @bfgeek)
-
[css-paint-api] Add note of what UA behavior should be for long running paint functions. w3c/css-houdini-drafts#36 (1 comment by @bfgeek)
-
[css-properties-values-api] Flag access to parent computed style w3c/css-houdini-drafts#2 (1 comment by @astearns)
-
[css-properties-values-api] Allow access to parent/ancestor elements w3c/css-houdini-drafts#4 (1 comment by @astearns)
-
[css-paint-api] Ed Issue: Make note that the contents of custom paint are not accessible. w3c/css-houdini-drafts#21 (1 comment by @bfgeek)
-
[css-paint-api] Need to define the initial state of the canvas in the spec. w3c/css-houdini-drafts#13 (1 comment by @bfgeek)
-
Specify what happens when an exception is throw during a paint callback. w3c/css-houdini-drafts#9 (1 comment by @bfgeek)
-
Calling registerPaint with the same name more than once should throw. w3c/css-houdini-drafts#7 (1 comment by @bfgeek)
-
[css-paint-api] Add note that setting global alpha, clip, etc may be in a future level of the spec. w3c/css-houdini-drafts#37 (1 comment by @bfgeek)
-
Can property names be a type accepted by the syntax for custom properties? w3c/css-houdini-drafts#10 (1 comment by @shans)
-
[css-properties-values-api] Consider moving output property conflict resolution to apply time rather than at register time. w3c/css-houdini-drafts#49 (1 comment by @FremyCompany)
-
-
1 pull request opened.
-
Add scroll-api use cases w3c/css-houdini-drafts#58, by @RByers.
-
-
1 pull request merged.
-
Add scroll-api use cases w3c/css-houdini-drafts#58.
-
w3c/csswg-drafts
-
11 issues opened.
-
[css-animations] Check that all edits from 2012 TPAC have been made w3c/csswg-drafts#75, by @birtles.
-
[css-animations-1] Check that ambiguities around animation shorthand have all been edited in w3c/csswg-drafts#74, by @birtles.
-
Incorporate Estelle's changes w3c/csswg-drafts#73, by @birtles.
-
Replace "Animatable" with "Animation type" w3c/csswg-drafts#72, by @birtles.
-
Clarify how @keyframes rules cascade, particularly with regard to timing functions w3c/csswg-drafts#71, by @birtles.
-
[css-animations] Add a feature for reusing @keyframes rules and triggering new animations w3c/csswg-drafts#70, by @birtles.
-
Specify how repeated references to a @keyframes rule are resolved w3c/csswg-drafts#69, by @birtles.
-
[css-animations] Clarify or remove elapsedTime w3c/csswg-drafts#68, by @birtles.
-
Make animation-delay live w3c/csswg-drafts#67, by @birtles.
-
[css-animations] Specify base value liveness w3c/csswg-drafts#66, by @birtles.
-
9 pull requests opened.
-
More consistent monospace styling w3c/csswg-drafts#65, by @zcorpan.
-
Adding a description about what is a 'pole'. w3c/csswg-drafts#64, by @Adenilson.
-
Doing the changes in the bikeshed file. w3c/csswg-drafts#63, by @Adenilson.
-
Quite a few misc fixes plus rephrasing 2 paragraphs w3c/csswg-drafts#62, by @Adenilson.
-
Rephrasing note about shape diversity. w3c/csswg-drafts#61, by @Adenilson.
-
Fixing use of preposition (of -> for). w3c/csswg-drafts#60, by @Adenilson.
-
Adding periods at the end figure's descriptions. w3c/csswg-drafts#59, by @Adenilson.
-
Fixes pre-wrap, pre-wrap-auto and preserve-auto w3c/csswg-drafts#58, by @frivoal.
-
Make img alt text visible w3c/csswg-drafts#57, by @zcorpan.
-
-
7 pull requests merged.
-
Doing the changes in the bikeshed file. w3c/csswg-drafts#63.
-
Adding a description about what is a 'pole'. w3c/csswg-drafts#64.
-
More consistent monospace styling w3c/csswg-drafts#65.
-
Quite a few misc fixes plus rephrasing 2 paragraphs w3c/csswg-drafts#62.
-
Rephrasing note about shape diversity. w3c/csswg-drafts#61.
-
Fixing use of preposition (of -> for). w3c/csswg-drafts#60.
-
Make img alt text visible w3c/csswg-drafts#57.
-
-
1 pull request closed.
-
Adding periods at the end figure's descriptions. w3c/csswg-drafts#59.
-
-
5 pull requests received 14 new comments.
-
Doing the changes in the bikeshed file. w3c/csswg-drafts#63 (5 comments by @Adenilson, @anawhj, @frivoal)
-
Quite a few misc fixes plus rephrasing 2 paragraphs w3c/csswg-drafts#62 (4 comments by @Adenilson, @anawhj, @tabatkins)
-
Adding a description about what is a 'pole'. w3c/csswg-drafts#64 (2 comments by @frivoal, @jihyerish)
-
TR publications
-
7 documents published.
-
CSS Grid Layout Module Level 1 published as a Working Draft. History of CSS Grid Layout Module Level 1
-
CSS Inline Layout Module Level 3 published as a Working Draft. History of CSS Inline Layout Module Level 3
-
CSS Cascading and Inheritance Level 4 published as a Working Draft. History of CSS Cascading and Inheritance Level 4
-
CSS Basic User Interface Module Level 4 published as a First Public Working Draft. History of CSS Basic User Interface Module Level 4
-
CSS Round Display Level 1 published as a First Public Working Draft. History of CSS Round Display Level 1
-
CSS Text Module Level 4 published as a First Public Working Draft. History of CSS Text Module Level 4
-
CSS Page Floats published as a First Public Working Draft. History of CSS Page Floats
-
GitHub
w3c/css-houdini-drafts
-
8 issues opened.
-
[scrolling] Examples of interesting Scroll Effects w3c/css-houdini-drafts#45, by @grorg.
-
[other] We should create a CSS Dependencies spec w3c/css-houdini-drafts#44, by @FremyCompany.
-
[css-paint][isolated-workers] What happens if a script throws? w3c/css-houdini-drafts#43, by @FremyCompany.
-
[css-properties-values] Apply hook triggering new style resolution? w3c/css-houdini-drafts#42, by @FremyCompany.
-
[css-typed-om] Calc representation not compatible with Custom Properties + var() w3c/css-houdini-drafts#41, by @FremyCompany.
-
[css-properties-values-api] Apply hook limits use of custom property value on the same element w3c/css-houdini-drafts#39, by @gregwhitworth.
-
[css-properties-values] Example 1 seems to do the same thing twice w3c/css-houdini-drafts#38, by @jakearchibald.
-
-
4 issues closed.
-
[css-paint][isolated-workers] What happens if a script throws? w3c/css-houdini-drafts#43.
-
[css-properties-values] Apply hook triggering new style resolution? w3c/css-houdini-drafts#42.
-
[css-properties-values] Example 1 seems to do the same thing twice w3c/css-houdini-drafts#38.
-
-
11 issues received 46 new comments.
-
[scrolling] Examples of interesting Scroll Effects w3c/css-houdini-drafts#45 (17 comments by @frivoal, @grorg, @RByers, @tdresser)
-
[other] We should create a CSS Dependencies spec w3c/css-houdini-drafts#44 (7 comments by @FremyCompany, @tabatkins)
-
[css-paint][isolated-workers] What happens if a script throws? w3c/css-houdini-drafts#43 (4 comments by @FremyCompany, @tabatkins)
-
[css-paint-api] Decide what to do about cursor. w3c/css-houdini-drafts#33 (4 comments by @frivoal, @tabatkins)
-
[css-typed-om] Calc representation not compatible with Custom Properties + var() w3c/css-houdini-drafts#41 (3 comments by @FremyCompany, @tabatkins)
-
[css-paint-api] Allow custom paint to optionally declare an intrinsic size. w3c/css-houdini-drafts#31 (3 comments by @frivoal, @tabatkins)
-
[css-paint-api] Add to spec how many times a paint function is able to be called if its inputs don't change w3c/css-houdini-drafts#26 (3 comments by @bfgeek, @frivoal, @tabatkins)
-
[css-properties-values] Apply hook triggering new style resolution? w3c/css-houdini-drafts#42 (2 comments by @FremyCompany, @tabatkins)
-
https://github.com/w3c/css-houdini-drafts/ still says "Specification issues are discussed on the public public-houdini mailing list." w3c/css-houdini-drafts#40 (1 comment by @tabatkins)
-
[css-paint-api] Change <image-or-paint> to just <image> w3c/css-houdini-drafts#32 (1 comment by @frivoal)
-
[css-properties-values] Example 1 seems to do the same thing twice w3c/css-houdini-drafts#38 (1 comment by @gregwhitworth)
-
w3c/csswg-drafts
-
9 pull requests opened.
-
[css-ui] Avoid unnecessary cascading in default HTML stylesheet w3c/csswg-drafts#56, by @cvrebert.
-
[css-ui] Add !important to input[type=hidden] portion of default stylesheet to align with HTML w3c/csswg-drafts#55, by @cvrebert.
-
[css-ui] Avoid unnecessary redundancy in HTML default stylesheet w3c/csswg-drafts#54, by @cvrebert.
-
[css-ui-4] Fix typo w3c/csswg-drafts#53, by @jwdallas.
-
Adding a description to address the case of a Grooved black border w3c/csswg-drafts#52, by @Adenilson.
-
[css-2015] Fix typo w3c/csswg-drafts#51, by @simevidas.
-
[css-2015] Clarify why unstable features should be released both prefixed and unprefixed w3c/csswg-drafts#50, by @frivoal.
-
Florian/pre wrap auto trim w3c/csswg-drafts#49, by @frivoal.
-
[css-page-floats] HTML errors checked w3c/csswg-drafts#48, by @johanneswilm.
-
-
8 pull requests merged.
-
[css-ui] Avoid unnecessary cascading in default HTML stylesheet w3c/csswg-drafts#56.
-
[css-ui] Avoid unnecessary redundancy in HTML default stylesheet w3c/csswg-drafts#54.
-
[css-ui-4] Fix typo w3c/csswg-drafts#53.
-
[css-2015] Fix typo w3c/csswg-drafts#51.
-
Florian/pre wrap auto trim w3c/csswg-drafts#49.
-
[css-page-floats] HTML errors checked w3c/csswg-drafts#48.
-
-
4 pull requests received 12 new comments.
-
[css-ui] Add !important to input[type=hidden] portion of default stylesheet to align with HTML w3c/csswg-drafts#55 (4 comments by @cvrebert, @frivoal)
-
Adding a description to address the case of a Grooved black border w3c/csswg-drafts#52 (4 comments by @Adenilson, @SimonSapin, @tabatkins)
-
[css-2015] Clarify why unstable features should be released both prefixed and unprefixed w3c/csswg-drafts#50 (1 comment by @frivoal)
-
w3c/IntersectionObserver
-
1 issue opened.
-
figure out type of changerecord.quads w3c/IntersectionObserver#29, by @ojanvafai.
-
-
17 issues closed.
-
MS Feedback: Is the PositionObserver intended for Inline elements? w3c/IntersectionObserver#10.
-
getComputedOpacity is insufficient w3c/IntersectionObserver#14.
-
Provide Microsoft Edge-team feedback on PositionObserver w3c/IntersectionObserver#2.
-
MS Feedback: Data scrollers (List view) scenario likely not in scope w3c/IntersectionObserver#3.
-
MS Feedback: Alternative Idea: imperative and event-based w3c/IntersectionObserver#4.
-
MS Feedback: Delay loading scenario applicability questioned w3c/IntersectionObserver#5.
-
MS Feedback: Usage for Ad Impression Usage Scenario (what is importance for into/out-of view)? w3c/IntersectionObserver#6.
-
MS Feedback: Avoiding layout goal seems problematic w3c/IntersectionObserver#9.
-
MS Feedback: Define the callback rate (min/max?) w3c/IntersectionObserver#11.
-
MS Feedback: viewportModifier calc magic too tricky w3c/IntersectionObserver#7.
-
It's not clear what the use-case is for thresholdCallbacks: false w3c/IntersectionObserver#18.
-
Sanity check that knowing cross-domain iframes' position doesn't leak security information w3c/IntersectionObserver#19.
-
Rename PositionObserver to IntersectionObserver w3c/IntersectionObserver#21.
-
viewportModifier should be distance and need a boolean for predictive callbacks w3c/IntersectionObserver#25.
-
Need to rename the viewport fields in the config and change records w3c/IntersectionObserver#26.
-
`viewportModifierTime` should use ms? w3c/IntersectionObserver#12.
-
figure out type of changerecord.quads w3c/IntersectionObserver#29.
-
-
22 issues received 25 new comments.
-
MS Feedback: Is the PositionObserver intended for Inline elements? w3c/IntersectionObserver#10 (2 comments by @ojanvafai)
-
viewport rect should be the intersection of ancestor scrollers w3c/IntersectionObserver#22 (2 comments by @ojanvafai, @slightlyoff)
-
viewportmodifier should allow negative values w3c/IntersectionObserver#27 (2 comments by @esprehn, @ojanvafai)
-
What should happen if the viewport-defining element is an inline? w3c/IntersectionObserver#13 (1 comment by @esprehn)
-
Provide Microsoft Edge-team feedback on PositionObserver w3c/IntersectionObserver#2 (1 comment by @ojanvafai)
-
MS Feedback: Data scrollers (List view) scenario likely not in scope w3c/IntersectionObserver#3 (1 comment by @ojanvafai)
-
MS Feedback: Alternative Idea: imperative and event-based w3c/IntersectionObserver#4 (1 comment by @ojanvafai)
-
MS Feedback: Delay loading scenario applicability questioned w3c/IntersectionObserver#5 (1 comment by @ojanvafai)
-
Figure out how to enforce that observed element is a descendant of the viewport element w3c/IntersectionObserver#16 (1 comment by @esprehn)
-
MS Feedback: Usage for Ad Impression Usage Scenario (what is importance for into/out-of view)? w3c/IntersectionObserver#6 (1 comment by @ojanvafai)
-
MS Feedback: Avoiding layout goal seems problematic w3c/IntersectionObserver#9 (1 comment by @ojanvafai)
-
MS Feedback: Define the callback rate (min/max?) w3c/IntersectionObserver#11 (1 comment by @ojanvafai)
-
What should the viewport rect be with pinch zoom w3c/IntersectionObserver#20 (1 comment by @esprehn)
-
MS Feedback: viewportModifier calc magic too tricky w3c/IntersectionObserver#7 (1 comment by @ojanvafai)
-
It's not clear what the use-case is for thresholdCallbacks: false w3c/IntersectionObserver#18 (1 comment by @ojanvafai)
-
spec needs to be clear on the timing of the callback w3c/IntersectionObserver#23 (1 comment by @ojanvafai)
-
spec needs to be clear about the coordinate space of the rects in the change record w3c/IntersectionObserver#24 (1 comment by @ojanvafai)
-
viewportModifier should be distance and need a boolean for predictive callbacks w3c/IntersectionObserver#25 (1 comment by @ojanvafai)
-
Need to rename the viewport fields in the config and change records w3c/IntersectionObserver#26 (1 comment by @ojanvafai)
-
TR publications
-
1 document published.
-
CSS Grid Layout Module Level 1 published as a Working Draft. History of CSS Grid Layout Module Level 1
-
Participants
-
1 organization joined.
-
Pearson plc joined.
-
GitHub
w3c/css-houdini-drafts
-
31 issues opened.
-
[css-paint-api] Add note that setting global alpha, clip, etc may be in a future level of the spec. w3c/css-houdini-drafts#37, by @bfgeek.
-
[css-paint-api] Add note of what UA behavior should be for long running paint functions. w3c/css-houdini-drafts#36, by @bfgeek.
-
[css-paint-api] Add note in spec that partial invalidation of a fragment may be added in a future version of the spec. w3c/css-houdini-drafts#35, by @bfgeek.
-
[css-paint-api] Allow authors to create additional CanvasRenderingContexts to allow for caching. w3c/css-houdini-drafts#34, by @bfgeek.
-
[css-paint-api] Decide what to do about cursor. w3c/css-houdini-drafts#33, by @bfgeek.
-
[css-paint-api] Change <image-or-paint> to just <image> w3c/css-houdini-drafts#32, by @bfgeek.
-
[css-paint-api] Allow custom paint to optionally declare an intrinsic size. w3c/css-houdini-drafts#31, by @bfgeek.
-
[css-paint-api] Add note to spec that 3d effects will be in lvl2. w3c/css-houdini-drafts#30, by @bfgeek.
-
[css-paint-api] Add to spec if fragment has available overflow where rendering context places 0x0. w3c/css-houdini-drafts#29, by @bfgeek.
-
[css-paint-api] Add function to paint class which computes the overflow for the element. w3c/css-houdini-drafts#28, by @bfgeek.
-
[css-paint-api] Add example to the spec of a different heading being painted down the page. w3c/css-houdini-drafts#27, by @bfgeek.
-
[css-paint-api] Add to spec how many times a paint function is able to be called if its inputs don't change w3c/css-houdini-drafts#26, by @bfgeek.
-
[css-paint-api] Add ability for custom paint class to run an "initialization" step. w3c/css-houdini-drafts#25, by @bfgeek.
-
[css-paint-api] Try and find a way to access images w/o using a custom property w3c/css-houdini-drafts#24, by @bfgeek.
-
[css-paint-api] Decide how much information is in the "Geometry" passed into a paint function w3c/css-houdini-drafts#23, by @bfgeek.
-
[css-paint-api] Add note that script in a RAF which invalidates a custom paint should update in the same frame. w3c/css-houdini-drafts#22, by @bfgeek.
-
[css-paint-api] Ed Issue: Make note that the contents of custom paint are not accessible. w3c/css-houdini-drafts#21, by @bfgeek.
-
[css-paint-api] Create PaintRenderingContext2D which is a subset of the CanvasRenderingContext2D. w3c/css-houdini-drafts#20, by @bfgeek.
-
[css-paint-api] Add to spec what happens with Font resolution on rendering context. w3c/css-houdini-drafts#19, by @bfgeek.
-
[css-paint-api] Add to spec that a canvas is effectively "neutered" after the callback is complete. w3c/css-houdini-drafts#18, by @bfgeek.
-
[css-paint-api] Should partial invalidation of a paint function be part of Level 1 of spec? w3c/css-houdini-drafts#17, by @bfgeek.
-
[isolated-workers] Specify what happens when a script in an isolated worker throws an error. w3c/css-houdini-drafts#16, by @bfgeek.
-
[isolated-workers] Add console API to IsolatedWorkerGlobalScope w3c/css-houdini-drafts#15, by @bfgeek.
-
[isolated-workers] Add isolated worker ED to repository. w3c/css-houdini-drafts#14, by @bfgeek.
-
[css-paint-api] Need to define the initial state of the canvas in the spec. w3c/css-houdini-drafts#13, by @bfgeek.
-
Add roadmap for houdini w3c/css-houdini-drafts#12, by @gregwhitworth.
-
Possible mistake in example 1 w3c/css-houdini-drafts#11, by @gregwhitworth.
-
Can property names be a type accepted by the syntax for custom properties? w3c/css-houdini-drafts#10, by @shans.
-
Specify what happens when an exception is throw during a paint callback. w3c/css-houdini-drafts#9, by @bfgeek.
-
Nit: Change hookID to cssPaintRequestHandle or similar. w3c/css-houdini-drafts#8, by @bfgeek.
-
Calling registerPaint with the same name more than once should throw. w3c/css-houdini-drafts#7, by @bfgeek.
-
-
6 issues closed.
-
[css-paint-api] Should partial invalidation of a paint function be part of Level 1 of spec? w3c/css-houdini-drafts#17.
-
Possible mistake in example 1 w3c/css-houdini-drafts#11.
-
Nit: Change hookID to cssPaintRequestHandle or similar. w3c/css-houdini-drafts#8.
-
Clarify when apply function gets called. w3c/css-houdini-drafts#3.
-
initialValue must match given syntax w3c/css-houdini-drafts#6.
-
Add some additional types to specification. w3c/css-houdini-drafts#5.
-
-
5 issues received 5 new comments.
-
Specify what happens when an exception is throw during a paint callback. w3c/css-houdini-drafts#9 (1 comment by @bfgeek)
-
[css-paint-api] Add to spec what happens with Font resolution on rendering context. w3c/css-houdini-drafts#19 (1 comment by @tabatkins)
-
[css-paint-api] Should partial invalidation of a paint function be part of Level 1 of spec? w3c/css-houdini-drafts#17 (1 comment by @bfgeek)
-
[isolated-workers] Specify what happens when a script in an isolated worker throws an error. w3c/css-houdini-drafts#16 (1 comment by @bfgeek)
-
w3c/IntersectionObserver
-
26 issues opened.
-
Some assorted V2 features w3c/IntersectionObserver#28, by @ojanvafai.
-
viewportmodifier should allow negative values w3c/IntersectionObserver#27, by @ojanvafai.
-
Need to rename the viewport fields in the config and change records w3c/IntersectionObserver#26, by @ojanvafai.
-
viewportModifier should be distance and need a boolean for predictive callbacks w3c/IntersectionObserver#25, by @ojanvafai.
-
spec needs to be clear about the coordinate space of the rects in the change record w3c/IntersectionObserver#24, by @ojanvafai.
-
spec needs to be clear on the timing of the callback w3c/IntersectionObserver#23, by @ojanvafai.
-
viewport rect should be the intersection of ancestor scrollers w3c/IntersectionObserver#22, by @ojanvafai.
-
Rename PositionObserver to IntersectionObserver w3c/IntersectionObserver#21, by @ojanvafai.
-
What should the viewport rect be with pinch zoom w3c/IntersectionObserver#20, by @ojanvafai.
-
Sanity check that knowing cross-domain iframes' position doesn't leak security information w3c/IntersectionObserver#19, by @ojanvafai.
-
It's not clear what the use-case is for thresholdCallbacks: false w3c/IntersectionObserver#18, by @ojanvafai.
-
Natural viewport is a confusing name. w3c/IntersectionObserver#17, by @ojanvafai.
-
Figure out how to enforce that observed element is a descendant of the viewport element w3c/IntersectionObserver#16, by @ojanvafai.
-
Data Scrollers example should not observe each scrolled item w3c/IntersectionObserver#15, by @ojanvafai.
-
getComputedOpacity is insufficient w3c/IntersectionObserver#14, by @ojanvafai.
-
What should happen if the viewport-defining element is an inline? w3c/IntersectionObserver#13, by @ojanvafai.
-
`viewportModifierTime` should use ms? w3c/IntersectionObserver#12, by @slightlyoff.
-
MS Feedback: Define the callback rate (min/max?) w3c/IntersectionObserver#11, by @travisleithead.
-
MS Feedback: Is the PositionObserver intended for Inline elements? w3c/IntersectionObserver#10, by @travisleithead.
-
MS Feedback: Avoiding layout goal seems problematic w3c/IntersectionObserver#9, by @travisleithead.
-
MS Feedback: Please don't expose the paint-rect (viewportPaintRect) w3c/IntersectionObserver#8, by @travisleithead.
-
MS Feedback: viewportModifier calc magic too tricky w3c/IntersectionObserver#7, by @travisleithead.
-
MS Feedback: Usage for Ad Impression Usage Scenario (what is importance for into/out-of view)? w3c/IntersectionObserver#6, by @travisleithead.
-
MS Feedback: Delay loading scenario applicability questioned w3c/IntersectionObserver#5, by @travisleithead.
-
MS Feedback: Alternative Idea: imperative and event-based w3c/IntersectionObserver#4, by @travisleithead.
-
MS Feedback: Data scrollers (List view) scenario likely not in scope w3c/IntersectionObserver#3, by @travisleithead.
-
-
2 issues closed.
-
viewportPaintRect needs to be explained w3c/IntersectionObserver#1.
-
MS Feedback: Please don't expose the paint-rect (viewportPaintRect) w3c/IntersectionObserver#8.
-
-
12 issues received 16 new comments.
-
MS Feedback: viewportModifier calc magic too tricky w3c/IntersectionObserver#7 (2 comments by @rocallahan, @slightlyoff)
-
MS Feedback: Usage for Ad Impression Usage Scenario (what is importance for into/out-of view)? w3c/IntersectionObserver#6 (2 comments by @ojanvafai)
-
MS Feedback: Alternative Idea: imperative and event-based w3c/IntersectionObserver#4 (2 comments by @esprehn, @slightlyoff)
-
MS Feedback: Data scrollers (List view) scenario likely not in scope w3c/IntersectionObserver#3 (2 comments by @ojanvafai, @slightlyoff)
-
Sanity check that knowing cross-domain iframes' position doesn't leak security information w3c/IntersectionObserver#19 (1 comment by @ojanvafai)
-
MS Feedback: Avoiding layout goal seems problematic w3c/IntersectionObserver#9 (1 comment by @ojanvafai)
-
MS Feedback: Define the callback rate (min/max?) w3c/IntersectionObserver#11 (1 comment by @ojanvafai)
-
MS Feedback: Delay loading scenario applicability questioned w3c/IntersectionObserver#5 (1 comment by @esprehn)
-
MS Feedback: Please don't expose the paint-rect (viewportPaintRect) w3c/IntersectionObserver#8 (1 comment by @slightlyoff)
-
Provide Microsoft Edge-team feedback on PositionObserver w3c/IntersectionObserver#2 (1 comment by @travisleithead)
-
w3c/csswg-drafts
-
3 pull requests opened.
-
[css-page-floats] minor syntax fix w3c/csswg-drafts#47, by @johanneswilm.
-
[css-page-floats] minor language fixes, after comments from Liam w3c/csswg-drafts#46, by @johanneswilm.
-
[css-page-floats] small language fixes, add definition of not overlap… w3c/csswg-drafts#45, by @johanneswilm.
-
-
3 pull requests merged.
-
[css-page-floats] minor syntax fix w3c/csswg-drafts#47.
-
[css-page-floats] minor language fixes, after comments from Liam w3c/csswg-drafts#46.
-
[css-page-floats] small language fixes, add definition of not overlap… w3c/csswg-drafts#45.
-
TR publications
-
3 documents published.
-
CSS Basic User Interface Module Level 3 (CSS3 UI) published as a Candidate Recommendation Snapshot. History of CSS Basic User Interface Module Level 3 (CSS3 UI)
-
CSS Display Module Level 3 published as a Working Draft. History of CSS Display Module Level 3
-
Web Animations published as a Working Draft. History of Web Animations
-
GitHub
w3c/IntersectionObserver
-
2 issues opened.
-
Provide Microsoft Edge-team feedback on PositionObserver w3c/IntersectionObserver#2, by @travisleithead.
-
viewportPaintRect needs to be explained w3c/IntersectionObserver#1, by @rocallahan.
-
-
1 issue received 2 new comments.
-
Provide Microsoft Edge-team feedback on PositionObserver w3c/IntersectionObserver#2 (2 comments by @travisleithead)
-
w3c/csswg-drafts
-
12 pull requests opened.
-
Non normative edits. w3c/csswg-drafts#41, by @estelle.
-
Minor fixes of the example for `grid-auto-flow` section w3c/csswg-drafts#40, by @SelenIT.
-
[css-variables] The dependency graph should be directed w3c/csswg-drafts#39, by @SimonSapin.
-
fonts.ready is a property not a function w3c/csswg-drafts#38, by @jakearchibald.
-
fix typo in css-snappoints doc w3c/csswg-drafts#37, by @mikehenrty.
-
Fix for consistency with other uses of `bar` w3c/csswg-drafts#36, by @ebruchez.
-
Florian/regions bikeshed w3c/csswg-drafts#35, by @frivoal.
-
[css-containment] Fix layout containment and fragmentainer interaction w3c/csswg-drafts#34, by @frivoal.
-
Florian/contain and clip w3c/csswg-drafts#33, by @frivoal.
-
10 pull requests merged.
-
Minor fixes of the example for `grid-auto-flow` section w3c/csswg-drafts#40.
-
fonts.ready is a property not a function w3c/csswg-drafts#38.
-
[css-variables] The dependency graph should be directed w3c/csswg-drafts#39.
-
fix typo in css-snappoints doc w3c/csswg-drafts#37.
-
Fix for consistency with other uses of `bar` w3c/csswg-drafts#36.
-
[css-containment] Fix layout containment and fragmentainer interaction w3c/csswg-drafts#34.
-
Florian/regions bikeshed w3c/csswg-drafts#35.
-
Florian/contain and clip w3c/csswg-drafts#33.
-
3 pull requests closed.
-
Clarification for an example w3c/csswg-drafts#4.
-
Non normative edits. w3c/csswg-drafts#41.
-
animations override !important w3c/csswg-drafts#20.
-
-
7 pull requests received 24 new comments.
-
[css-containment] Fix layout containment and fragmentainer interaction w3c/csswg-drafts#34 (12 comments by @frivoal, @plinss, @tabatkins)
-
TR publications
-
2 documents published.
-
CSS Counter Styles Level 3 published as a Candidate Recommendation Snapshot. History of CSS Counter Styles Level 3
-
CSS Values and Units Module Level 3 published as a Candidate Recommendation Snapshot. History of CSS Values and Units Module Level 3
-
GitHub
w3c/csswg-drafts
-
7 pull requests opened.
-
[css-page-floats] Add details on process of page float placement. w3c/csswg-drafts#32, by @johanneswilm.
-
[css-page-floats] Remove parts about column spanning concerned under … w3c/csswg-drafts#31, by @johanneswilm.
-
[css-page-floats] add work status w3c/csswg-drafts#30, by @johanneswilm.
-
[css-align] Fix typo in Baseline Self-Alignment definition for Grids. w3c/csswg-drafts#28, by @javifernandez.
-
Florian/pre wrap w3c/csswg-drafts#27, by @frivoal.
-
Florian/text decor skip w3c/csswg-drafts#26, by @frivoal.
-
-
7 pull requests merged.
-
[css-page-floats] Add details on process of page float placement. w3c/csswg-drafts#32.
-
[css-page-floats] Remove parts about column spanning concerned under … w3c/csswg-drafts#31.
-
[css-page-floats] add work status w3c/csswg-drafts#30.
-
Florian/pre wrap w3c/csswg-drafts#27.
-
[css-align] Fix typo in Baseline Self-Alignment definition for Grids. w3c/csswg-drafts#28.
-
Florian/text decor skip w3c/csswg-drafts#26.
-
-
1 pull request closed.
-
Remove shadow piercing and multiple shadow roots w3c/csswg-drafts#21.
-
-
3 pull requests received 5 new comments.
-
[css-align] Fix typo in Baseline Self-Alignment definition for Grids. w3c/csswg-drafts#28 (2 comments by @atanassov, @tabatkins)
w3c/css-houdini-drafts
-
6 issues opened.
-
initialValue must match given syntax w3c/css-houdini-drafts#6, by @shans.
-
Add some additional types to specification. w3c/css-houdini-drafts#5, by @shans.
-
[css-properties-values-api] Allow access to parent/ancestor elements w3c/css-houdini-drafts#4, by @shans.
-
Clarify when apply function gets called. w3c/css-houdini-drafts#3, by @shans.
-
[css-properties-values-api] Flag access to parent computed style w3c/css-houdini-drafts#2, by @shans.
-
Should define the pre-apply computed value for each type that is supported. w3c/css-houdini-drafts#1, by @shans.
-
TR publications
-
2 documents published.
-
CSS Flexible Box Layout Module Level 1 published as a Last Call Working Draft. History of CSS Flexible Box Layout Module Level 1
-
CSS Basic User Interface Module Level 3 (CSS3 UI) published as a Working Draft. History of CSS Basic User Interface Module Level 3 (CSS3 UI)
-
Participants
-
1 participant joined.
-
Rachel Nabors (Microsoft Corporation) joined.
-
GitHub
w3c/csswg-drafts
-
4 pull requests opened.
-
[css-text-decor-4] Add trailing-spaces to text-decoration-skip w3c/csswg-drafts#22, by @frivoal.
-
4 pull requests merged.
-
[css-text-decor-4] Add trailing-spaces to text-decoration-skip w3c/csswg-drafts#22.
TR publications
-
4 documents published.
-
CSS Cascading and Inheritance Level 3 published as a Candidate Recommendation Snapshot. History of CSS Cascading and Inheritance Level 3
-
CSS Basic User Interface Module Level 3 (CSS3 UI) published as a Working Draft. History of CSS Basic User Interface Module Level 3 (CSS3 UI)
-
CSS Cascading and Inheritance Level 4 published as a First Public Working Draft. History of CSS Cascading and Inheritance Level 4
-
Motion Path Module Level 1 published as a First Public Working Draft. History of Motion Path Module Level 1
-
Participants
-
1 organization joined.
-
Mitsubishi Electric Corporation joined.
-
GitHub
w3c/csswg-drafts
-
7 pull requests opened.
-
Remove shadow piercing and multiple shadow roots w3c/csswg-drafts#21, by @kojiishi.
-
animations override !important w3c/csswg-drafts#20, by @estelle.
-
[css-images-4] Mandate support for PNG and SVG in <image> w3c/csswg-drafts#19, by @frivoal.
-
[css3-ui] Explicit file format requirements for 'cursor' w3c/csswg-drafts#18, by @frivoal.
-
[css-ui] Fix all current bikeshed warnings w3c/csswg-drafts#17, by @frivoal.
-
Florian/box sizing w3c/csswg-drafts#16, by @frivoal.
-
Fix capitalization. w3c/csswg-drafts#15, by @SimonSapin.
-
-
5 pull requests merged.
-
[css3-ui] Explicit file format requirements for 'cursor' w3c/csswg-drafts#18.
-
[css-images-4] Mandate support for PNG and SVG in <image> w3c/csswg-drafts#19.
-
[css-ui] Fix all current bikeshed warnings w3c/csswg-drafts#17.
-
Florian/box sizing w3c/csswg-drafts#16.
-
Fix capitalization. w3c/csswg-drafts#15.
-
-
1 pull request closed.
-
[css3-ui] Clean up minor leftover from nav-index removal w3c/csswg-drafts#14.
-
-
3 pull requests received 11 new comments.
-
[css-ui] Fix all current bikeshed warnings w3c/csswg-drafts#17 (8 comments by @frivoal, @plinss, @tabatkins, @tantek)
-
[css3-ui] Explicit file format requirements for 'cursor' w3c/csswg-drafts#18 (2 comments by @frivoal, @tantek)
-
[css3-ui] Clean up minor leftover from nav-index removal w3c/csswg-drafts#14 (1 comment by @frivoal)
-
TR publications
-
4 documents published.
-
CSS Grid Layout Module Level 1 published as a Working Draft. History of CSS Grid Layout Module Level 1
-
CSS Basic User Interface Module Level 3 (CSS3 UI) published as a Working Draft. History of CSS Basic User Interface Module Level 3 (CSS3 UI)
-
CSS Scroll Snap Points Module Level 1 published as a First Public Working Draft. History of CSS Scroll Snap Points Module Level 1
-
CSS Template Layout Module published as a Note. History of CSS Template Layout Module
-
Participants
-
1 organization joined.
-
Electronics and Telecommunications Research Institute (ETRI) joined.
-
-
1 organization left.
-
MIRAE WEB Inc. left.
-
GitHub
w3c/csswg-drafts
-
2 pull requests opened.
-
[css3-ui] Clean up minor leftover from nav-index removal w3c/csswg-drafts#14, by @frivoal.
-
[css-text-decor] Add trailing-spaces to text-decoration-skip w3c/csswg-drafts#13, by @frivoal.
-
-
1 pull request closed.
-
[css-text-decor] Add trailing-spaces to text-decoration-skip w3c/csswg-drafts#13.
-
-
1 pull request received 1 new comment.
-
[css-text-decor] Add trailing-spaces to text-decoration-skip w3c/csswg-drafts#13 (1 comment by @fantasai)
-
TR publications
-
3 documents published.
-
CSS Counter Styles Level 3 published as a Candidate Recommendation Snapshot. History of CSS Counter Styles Level 3
-
CSS Basic User Interface Module Level 3 (CSS3 UI) published as a Working Draft. History of CSS Basic User Interface Module Level 3 (CSS3 UI)
-
CSS Positioned Layout Module Level 3 published as a Working Draft. History of CSS Positioned Layout Module Level 3
-
Participants
-
2 organizations joined.
-
HTML5 Converged Technology Forum joined.
-
LG Electronics joined.
-
GitHub
w3c/csswg-drafts
-
5 pull requests opened.
-
[css-grid] Fix typo in the grid item placement algorithm w3c/csswg-drafts#12, by @mrego.
-
fix multi-prop dfn-for w3c/csswg-drafts#11, by @astearns.
-
new wrap-* properties w3c/csswg-drafts#10, by @astearns.
-
remove .html for auto-generation w3c/csswg-drafts#9, by @astearns.
-
[css-color] Fix typo in HexColor constructor with HexColorInit w3c/csswg-drafts#8, by @merih.
-
-
5 pull requests merged.
-
[css-grid] Fix typo in the grid item placement algorithm w3c/csswg-drafts#12.
-
fix multi-prop dfn-for w3c/csswg-drafts#11.
-
new wrap-* properties w3c/csswg-drafts#10.
-
remove .html for auto-generation w3c/csswg-drafts#9.
-
[css-color] Fix typo in HexColor constructor with HexColorInit w3c/csswg-drafts#8.
-
-
2 pull requests received 2 new comments.
TR publications
-
4 documents published.
-
Compositing and Blending Level 1 published as a Candidate Recommendation Snapshot. History of Compositing and Blending Level 1
-
CSS Fragmentation Module Level 3 published as a Working Draft. History of CSS Fragmentation Module Level 3
-
CSS Exclusions Module Level 1 published as a Working Draft. History of CSS Exclusions Module Level 1
-
CSS Pseudo-Elements Module Level 4 published as a First Public Working Draft. History of CSS Pseudo-Elements Module Level 4
-
Participants
-
1 participant left.
-
Arron Eicholz (Microsoft Corporation) left.
-
-
1 organization joined.
-
Vivliostyle Inc. joined.
-
GitHub
w3c/csswg-drafts
-
2 pull requests opened.
-
[css-grid] Fix typo: gridDefinitionColumns vs gridTemplateColumns w3c/csswg-drafts#7, by @mrego.
-
[css-syntax] Fix a typo in tokenization algorithm of <column-token>. w3c/csswg-drafts#6, by @SimonSapin.
-
-
2 pull requests merged.
-
[css-grid] Fix typo: gridDefinitionColumns vs gridTemplateColumns w3c/csswg-drafts#7.
-
[css-syntax] Fix a typo in tokenization algorithm of <column-token>. w3c/csswg-drafts#6.
-