Adam Argyle via GitHub
Adarsh Kumar via GitHub
Adrian Cochrane via GitHub
Ahmad Shadeed via GitHub
Alan Stearns via GitHub
Albert Marashi via GitHub
Alex Inkin via GitHub
Alison Maher via GitHub
Amelia Bellamy-Royds via GitHub
andreamorales via GitHub
Andreu Botella via GitHub
Andrew Bloyce via GitHub
andruud via GitHub
- Re: [csswg-drafts] [css-conditional] Unclear what is and isn't a descriptor for at-rule() (#11118) (Thursday, 31 October)
- Re: [csswg-drafts] [css-values-5] attr() and forwards compatible parsing (#11035) (Wednesday, 30 October)
- [csswg-drafts] [css-conditional] Unclear what is and isn't a descriptor for at-rule() (#11118) (Wednesday, 30 October)
- [csswg-drafts] [css-conditional] Nested at-rules within at-rule() (#11117) (Wednesday, 30 October)
- [csswg-drafts] [css-conditional] Behavior of @supports(at-rule(@import)) (#11116) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Wednesday, 23 October)
- [csswg-drafts] [css-variables-1] Expose pending substitution value? (#11055) (Monday, 21 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Thursday, 10 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Thursday, 10 October)
- [csswg-drafts] Pull Request: [cssom] Don't serialize empty rules (@media) (Tuesday, 1 October)
- [csswg-drafts] Pull Request: [cssom] Don't serialize empty rules (Tuesday, 1 October)
Angel Ponce via GitHub
Anne van Kesteren via GitHub
Antoine Quint via GitHub
- Re: [csswg-drafts] [web-animations-1] commitStyles followed by cancel should not trigger a transition (#11084) (Friday, 25 October)
- Re: [csswg-drafts] [css-animations-2] interaction between the `timeline` property and `animation-timeline` property (#11054) (Monday, 21 October)
- Re: [csswg-drafts] [css-animations-2] interaction between the `timeline` property and `animation-timeline` property (#11054) (Monday, 21 October)
- [csswg-drafts] [css-animations-2] interaction between the `timeline` property and `animation-timeline` property (#11054) (Monday, 21 October)
- Re: [csswg-drafts] [scroll-animations] Can progress-based timelines report a current time outside of the `[0%-100%]` range? (#11033) (Sunday, 20 October)
- Closed: [csswg-drafts] [scroll-animations] Can progress-based timelines report a current time outside of the `[0%-100%]` range? (#11033) (Sunday, 20 October)
- Re: [csswg-drafts] [web-animations-2] [scroll-animations-1] Auto-aligning the start time of an animation associated with a scroll timeline (#10965) (Tuesday, 15 October)
- Re: [csswg-drafts] [scroll-animations] Can progress-based timelines report a current time outside of the `[0%-100%]` range? (#11033) (Monday, 14 October)
- [csswg-drafts] [scroll-animations] Can progress-based timelines report a current time outside of the `[0%-100%]` range? (#11033) (Monday, 14 October)
- Re: [csswg-drafts] [web-animations-2] clearing the _auto-align start time_ flag (#11018) (Thursday, 10 October)
- [csswg-drafts] [web-animations-2] clearing the _auto-align start time_ flag (#11018) (Thursday, 10 October)
- Re: [csswg-drafts] [web-animations-2] [scroll-animations-1] Auto-aligning the start time of an animation associated with a scroll timeline (#10965) (Tuesday, 1 October)
Arif via GitHub
Basit Ali via GitHub
beeps via GitHub
Ben Melluish via GitHub
Benjamin Aster via GitHub
Benoît Rouleau via GitHub
Boris Chiou via GitHub
Brad Schickler via GitHub
Bramus via GitHub
- Re: [csswg-drafts] [web-animations-2] Idea: Custom Effects (#2062) (Thursday, 31 October)
- Closed: [csswg-drafts] [web-animations-2] Idea: Custom Effects (#2062) (Thursday, 31 October)
- Re: [csswg-drafts] [css-animations] Proposal: Add a way to make the animation timing function apply to the whole animation (#8881) (Thursday, 31 October)
- Closed: [csswg-drafts] [css-animations] Proposal: Add a way to make the animation timing function apply to the whole animation (#8881) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] Namespacing id vs css based view transition names (#11112) (Wednesday, 30 October)
- Re: [csswg-drafts] [cssom] Element.getComputedStyle() (#379) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Wednesday, 30 October)
- Re: [csswg-drafts] [web-animations-2] Progress APIs (#8799) (Tuesday, 29 October)
- Re: [csswg-drafts] [web-animations-2] Custom effects (#6861) (Sunday, 27 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 24 October)
- Re: [csswg-drafts] Add `@container scroll-state(direction)` to [css-conditional-5] (#11082) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Thursday, 24 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Thursday, 24 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Wednesday, 23 October)
- Re: [csswg-drafts] [web-animations-2] Custom effects (#6861) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Monday, 21 October)
- Re: [csswg-drafts] [cssom-view-1] Provide onAnimationEnd callback in scrollIntoView options (#3744) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-4] Should `dv*` account for `overflow: auto` scrollbars dynamically? (#10059) (Monday, 14 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Monday, 14 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Monday, 14 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Friday, 11 October)
- Re: [csswg-drafts] [cssom-view] Expose small/large viewport dimensions of the layout viewport (#8709) (Thursday, 10 October)
- Re: [csswg-drafts] [css-viewport] interactive-widget=resizes-content - will that likely fix issues with fixed headers/footers and on-screen keyboards? (#10464) (Thursday, 10 October)
- Closed: [csswg-drafts] [css-viewport] interactive-widget=resizes-content - will that likely fix issues with fixed headers/footers and on-screen keyboards? (#10464) (Thursday, 10 October)
- Re: [csswg-drafts] [cssom-view] Expose small/large viewport dimensions of the layout viewport (#8709) (Wednesday, 9 October)
- Re: [csswg-drafts] [cssom-view] Expose small/large viewport dimensions of the layout viewport (#8709) (Wednesday, 9 October)
- Re: [csswg-drafts] [cssom-view] Expose small/large viewport dimensions of the layout viewport (#8709) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Sunday, 6 October)
- [csswg-drafts] Pull Request: [css-nesting-1] Fix exponential explosion example (Friday, 4 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Friday, 4 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Friday, 4 October)
- [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Friday, 4 October)
- Re: [csswg-drafts] [css-view-transitions-2] view-transition-name determined by element (#8320) (Wednesday, 2 October)
- Closed: [csswg-drafts] [css-cascade-5] `revert-layer` in element-attached styles (#10934) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-cascade-5] `revert-layer` in element-attached styles (#10934) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-overflow] Top/bottom banners scrolling in and out as the pages scrolls (was:proposal: scroll-index (priority)) (#5670) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-cascade-5] `revert-layer` in element-attached styles (#10934) (Tuesday, 1 October)
- Re: [csswg-drafts] Add ::top-layer pseudo element (#10963) (Tuesday, 1 October)
bravecrayon via GitHub
Brian Birtles via GitHub
Bryce Wilson via GitHub
Chris Lilley via GitHub
- Closed: [csswg-drafts] [css-color-hdr] Add interpolation between multiple values of dynamic-range-limit (#10271) (Thursday, 31 October)
- Re: [csswg-drafts] [css-color-hdr] Add interpolation between multiple values of dynamic-range-limit (#10271) (Thursday, 31 October)
- Re: [csswg-drafts] [css-2024] Add specs to Rough Interoperability (#9793) (Thursday, 31 October)
- Re: [csswg-drafts] [motion-1] Publish an updated WD or move to CR (#9165) (Thursday, 31 October)
- Re: [csswg-drafts] [motion-1] Publish an updated WD or move to CR (#9165) (Thursday, 31 October)
- Re: [csswg-drafts] [css-images] Should EXIF image orientation data be ignored if it comes after the image data in the encoded image? (#11114) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-color-hdr] Add interpolation between multiple values of dynamic-range-limit (#10271) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-fonts] Support avar2 within tech() to support using the next generation of variable fonts tech (#10599) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-color-hdr] Add interpolation between multiple values of dynamic-range-limit (#10271) (Tuesday, 29 October)
- [csswg-drafts] [css-fonts] Reference font subsets without privacy leaks (#11092) (Friday, 25 October)
- Re: [csswg-drafts] [css-color-hdr] Add interpolation between multiple values of dynamic-range-limit (#10271) (Friday, 25 October)
- Re: [csswg-drafts] Fix typo in CSS Grid 3 overview (#10873) (Thursday, 24 October)
- Re: [csswg-drafts] Republishing Tasks Permathread (#6900) (Thursday, 24 October)
- Re: [csswg-drafts] [css-fonts] Support avar2 within tech() to support using the next generation of variable fonts tech (#10599) (Thursday, 24 October)
- Closed: [csswg-drafts] [css-color] Are `rgba()` and `hsla()` functions meant to be deprecated? (#10886) (Friday, 18 October)
- Re: [csswg-drafts] [css-fonts] Support avar2 within tech() to support using the next generation of variable fonts tech (#10599) (Thursday, 17 October)
- Re: [csswg-drafts] [css-fonts-4] font-display says it's valid in @font-feature-values but it isn't an at-rule (#2973) (Thursday, 17 October)
- Re: [csswg-drafts] [css-fonts] Support avar2 within tech() to support using the next generation of variable fonts tech (#10599) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-fonts] Support avar2 within tech() to support using the next generation of variable fonts tech (#10599) (Wednesday, 16 October)
- Re: [csswg-drafts] CSS color serialization and <input type=color> with alpha/colorspace (#11008) (Wednesday, 16 October)
- Re: [csswg-drafts] CSS color serialization and <input type=color> with alpha/colorspace (#11008) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-fonts] Support avar2 within tech() to support using the next generation of variable fonts tech (#10599) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-fonts] Should font-variant-emoji affect ZWJ emoji sequences? (#11036) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-color-4] Alias "grey()" to "gray()"? (#3298) (Sunday, 13 October)
- Re: [csswg-drafts] CSS color serialization and <input type=color> with alpha/colorspace (#11008) (Friday, 11 October)
- Re: [csswg-drafts] CSS color serialization and <input type=color> with alpha/colorspace (#11008) (Thursday, 10 October)
- Re: [csswg-drafts] CSS color serialization and <input type=color> with alpha/colorspace (#11008) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Thursday, 3 October)
- Re: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Thursday, 3 October)
- Re: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-color-5] Clarification on `none` components in relative color syntax. (#10360) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-color-5] Allow using channel keywords in any calculation (#10983) (Wednesday, 2 October)
Christoph Päper via GitHub
Christopher Cameron via GitHub
CSS Meeting Bot via GitHub
- Re: [csswg-drafts] [css-text] Prevent line breaking after explicit hyphens (#3434) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-text-4] text-autospace: what gets copied? (#8511) (Wednesday, 30 October)
- Re: [csswg-drafts] [cssom-view] Spec for offsetTop/Left does not match impls when offsetParent is `position:static` `<body>` element (#10549) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-images] Should CSS decorative images respect EXIF-orientation by default (#4165) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-color-hdr] Add interpolation between multiple values of dynamic-range-limit (#10271) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] Optionally capture some properties (e.g. opacity/border) as style instead of snapshot (#10585) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Thursday, 24 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] It is unclear which Document object https://drafts.csswg.org/resize-observer/#ref-for-resizeobserver is talking about (#10516) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-pseudo] Should the "first formatted line" propagate into a different BFC? (#11038) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-pseudo] Should the "first formatted line" propagate into a different BFC? (#11038) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-inline-3] inline boxes and line-fit-edge vs text-box-trim/edge (#10834) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-anchor-position] Better handling of scroll position for fixpos elements on first layout (#10999) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-inline] Disallow `auto` in `text-box` shorthand (#10748) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-inline-3] Allow re-ordering of <text-edge> keywords (#10713) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-inline-3] The behavior when one value is specified for `text-box-edge` (#10703) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-inline] Is `text-box-edge` inherited or not? (#10904) (Wednesday, 16 October)
- Re: [csswg-drafts] [cssom-view] Expose small/large viewport dimensions of the layout viewport (#8709) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-properties-values-api] Are fallbacks provided for registered properties validated by the CP syntax? (#10455) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-images] Mesh gradient / Freeform gradient / 2D gradient (#7648) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-values-5] Syntax of progress() vs mix() functions (#10489) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-anchor-position] Should anchor() be validated at parse time when it is known invalid? (#10955) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-variables][cssom] Empty value doesn't round-trip (#9847) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-content] Use case for counter / counters in content alt text? (#10387) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-overflow][css-contain][css-sizing] `overflow: auto` incompatible with size containment and container queries (#7875) (Wednesday, 9 October)
César Couto via GitHub
Daniel Glazman via GitHub
Daniel Holbert via GitHub
Dave Crossland via GitHub
Dave Letorey via GitHub
David A via GitHub
David H. via GitHub
David Somers via GitHub
davidsgrogan via GitHub
Delan Azabani via GitHub
Dmitry Statsenko via GitHub
Dominik Röttsches via GitHub
Douglas Parker via GitHub
dshin-moz via GitHub
ecbypi via GitHub
Egor Kloos via GitHub
Emilio Cobos Álvarez via GitHub
- Re: [csswg-drafts] [css-anchor-position-1] Behavior with transforms and offset-path (#8584) (Thursday, 31 October)
- Re: [csswg-drafts] [css-properties-values-api] "Property registration cannot be scoped" differs from all implementations in a consistent way (#10541) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-position] Static position of abspos top layer elements inside fixed pos. (#9939) (Friday, 25 October)
- [csswg-drafts] [css-view-transition] "capture the new state" and "capture the old state" are subtly different. (#11071) (Tuesday, 22 October)
- [csswg-drafts] Pull Request: [css-view-transitions] Specify with kind of exception gets used when skipping on resize. (Monday, 21 October)
- [csswg-drafts] Pull Request: [css-view-transitions] Clear captured flag on error. (Monday, 21 October)
- Re: [csswg-drafts] [css-view-transitions] Broken state management in "capture the old state" (#11058) (Monday, 21 October)
- Re: [csswg-drafts] [css-properties-values-api] "Property registration cannot be scoped" differs from all implementations in a consistent way (#10541) (Monday, 21 October)
- Re: [csswg-drafts] [css-view-transitions] Skip on activation doesn't provide a reason (#11059) (Monday, 21 October)
- [csswg-drafts] [css-view-transitions] Skip on activation doesn't provide a reason (#11059) (Monday, 21 October)
- Re: [csswg-drafts] [css-view-transitions] Broken state management in "capture the old state" (#11058) (Monday, 21 October)
- Re: [csswg-drafts] [css-view-transitions] Broken state management in "capture the old state" (#11058) (Monday, 21 October)
- Re: [csswg-drafts] [css-view-transitions] Broken state management in "capture the old state" (#11058) (Monday, 21 October)
- [csswg-drafts] [css-view-transitions] Broken state management in "capture the old state" (#11058) (Monday, 21 October)
- [csswg-drafts] Pull Request: [css-view-transitions-1] Remove redundant declaration. (Monday, 21 October)
- Re: [csswg-drafts] @media queries on mobile + zoom and media queries don't re-evaluate on zoom (#10399) (Tuesday, 15 October)
- Re: [csswg-drafts] [cssom] There should be a way to get Character Position of the Stylesheet Elements (#10480) (Tuesday, 15 October)
- Closed: [csswg-drafts] @media queries on mobile + zoom and media queries don't re-evaluate on zoom (#10399) (Tuesday, 15 October)
- Re: [csswg-drafts] @media queries on mobile + zoom and media queries don't re-evaluate on zoom (#10399) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-anchor-position] "painted strictly before" for acceptable anchor is not the correct term (#11029) (Sunday, 13 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Friday, 11 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Tuesday, 8 October)
- Closed: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Thursday, 3 October)
- Re: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Thursday, 3 October)
- Re: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Thursday, 3 October)
- [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Wednesday, 2 October)
- Re: [csswg-drafts] [cssom] Don't serialize empty rules (#10974) (Tuesday, 1 October)
Enokilis via GitHub
Estelle Weyl via GitHub
Ethan Jimenez via GitHub
Fabio Spampinato via GitHub
fantasai via GitHub
- Re: [csswg-drafts] [css-grid-3] Designer/developer feedback on masonry layout (#10233) (Thursday, 31 October)
- Re: [csswg-drafts] [css-text] Prevent line breaking after explicit hyphens (#3434) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Wednesday, 30 October)
- Re: [csswg-drafts] [css] [req] new scroll-snap-type: end, scroll uninterupted and snap on end (#11096) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-highlight-api][css-anchor-position] Allow `anchor-name` on `::highlight(...)` (#11100) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values] Proposal for an `all-vars` property to reset all custom properties (#11105) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values-4] inherit() function: like var() for parent value, for any property (#2864) (Monday, 28 October)
- Re: [csswg-drafts] [css-values]: Express conditional values in a more terse way (#5009) (Monday, 28 October)
- [csswg-drafts] [css-values-5] if() conditions with calc() comparisons (#11104) (Monday, 28 October)
- Re: [csswg-drafts] [css-values-5] What is the MVP for inline conditionals on custom properties? (#10064) (Monday, 28 October)
- Closed: [csswg-drafts] [css-values-5] What is the MVP for inline conditionals on custom properties? (#10064) (Monday, 28 October)
- Closed: [csswg-drafts] [css-values-5] Does media-progress() really want the entire <media-feature> production for its progress value? (#10966) (Monday, 28 October)
- Closed: [csswg-drafts] [css-values-5] Syntax of progress() vs mix() functions (#10489) (Monday, 28 October)
- Re: [csswg-drafts] [css-values-4][Editorial] `<condition>` type that other specs reference (#10457) (Monday, 28 October)
- Closed: [csswg-drafts] [css-values-5][css-conditional-5][css-cascade-5] Boolean Multiplier for ValDef syntax (#11091) (Monday, 28 October)
- Re: [csswg-drafts] [css-values-5][css-conditional-5][css-cascade-5] Boolean Multiplier for ValDef syntax (#11091) (Monday, 28 October)
- [csswg-drafts] [css-values-5][css-conditional-5][css-cascade-5] Boolean Multiplier for ValDef syntax (#11091) (Friday, 25 October)
- Re: [csswg-drafts] [css-text] Make first-letter work with inline text (#11047) (Friday, 18 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Thursday, 17 October)
- Re: [csswg-drafts] [css-inline] Is `text-box-edge` inherited or not? (#10904) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-inline-3] inline boxes and line-fit-edge vs text-box-trim/edge (#10834) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-inline-3] The behavior when one value is specified for `text-box-edge` (#10703) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-inline-3] The behavior when one value is specified for `text-box-edge` (#10703) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] Should the "first formatted line" propagate into a different BFC? (#11038) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-inline-3] Allow re-ordering of <text-edge> keywords (#10713) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-inline] Is `text-box-edge` inherited or not? (#10904) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-inline][css-text][css-pseudo] Define more details of the "first formatted line" (#10990) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] Safari’s ::selection “wash” and UA tweaks to highlight colors (#6853) (Tuesday, 15 October)
- Re: [csswg-drafts] Republishing Tasks Permathread (#6900) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo-4] Should `line-height` be applicable to `::placeholder`? (#5379) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo-4] Ensuring selection foreground/background contrast (#6150) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo-4] Ensuring selection foreground/background contrast (#6150) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo] Custom properties on :root (#6641) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] Custom properties on :root (#6641) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] Safari’s ::selection “wash” and UA tweaks to highlight colors (#6853) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo] highlight pseudos and compat stroke/fill properties (#7580) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo] [css-highlight-api] support for pseudo-elements? (#7118) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo] Should ::before / ::after really be part-like? (#10846) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo-4] single highlight pseudo for find-in-page? (#10212) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo-4] painting order of find-in-page highlights (#10213) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] `color-scheme` should be an allowed property for highlight pseudos (#11011) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo][css-shadow-parts] Define "part-like pseudo-element" concept (#10083) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-shadow-parts][css-pseudo] Move various ::part() details to 'part-like pseudo-element'. (#10839) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo-4] Clarify text decorations in ::spelling-error and ::grammar-error (#9633) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo-4] Add a new pseudo element search-text (#10475) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] highlight pseudos and non-applicable properties (#7591) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo-4] Add discussion of properties from the originating element (#9428) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo-4] [css-highlight-api-1] Integrating custom highlights into css-pseudo-4 (#6755) (Tuesday, 15 October)
- Re: [csswg-drafts] [selectors-4] Should :user-valid and :user-invalid apply to form and fieldset elements? (#9257) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-text-4] hanging-punctuation property not language-specific enough (#10141) (Tuesday, 15 October)
- Re: [csswg-drafts] [mediaqueries-5] Logical Media Queries (#10156) (Tuesday, 15 October)
- Re: [csswg-drafts] Top layer extended to the entire device screen, popover also rendered outside the page window (#10205) (Tuesday, 15 October)
- Re: [csswg-drafts] @media queries on mobile + zoom and media queries don't re-evaluate on zoom (#10399) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-grid] Feature: Display:Grid: grid-temp-col*: repeat+[set](autofill, min-column-width, max-column-width , bias-change, max-repeat) = repeat(auto-fill, 30rem, 40rem, min, 5) (#10400) (Tuesday, 15 October)
- Re: [csswg-drafts] CSS [parent-element]:nth-[attrib/class]-child[attrb+op+val](nth [BitflagOps] [value] ) Selectors for Display:Grid (#10402) (Tuesday, 15 October)
- Closed: [csswg-drafts] CSS: element property : device-overflow-inflation-width + device-overflow-inflated-width (#10404) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-sizing-4]: Minor fix: incorrect wpt.fyi link (#10602) (Tuesday, 15 October)
- Re: [csswg-drafts] [cssom-view-1] Provide onAnimationEnd callback in scrollIntoView options - Accidently closed? (#10737) (Tuesday, 15 October)
- Closed: [csswg-drafts] [cssom-view-1] Provide onAnimationEnd callback in scrollIntoView options - Accidently closed? (#10737) (Tuesday, 15 October)
- Re: [csswg-drafts] [cssom-view-1] Provide onAnimationEnd callback in scrollIntoView options (#3744) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-syntax] Do token streams vend component values? (#10863) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-syntax] Do token streams vend component values? (#10863) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-display-4] Special Consideration(s) of Establishing Container Block (#10871) (Tuesday, 15 October)
- Closed: [csswg-drafts] [selectors-4] Augment the grammar to unambigously encode handling of white-space? (#10940) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo] Add boundary element and line break element selector. (#11020) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] Add boundary element and line break element selector. (#11020) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-page] Default placement (text-align and vertical-align) of @page margins not useful in vertical writing modes (#10421) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-page] Default placement (text-align and vertical-align) of @page margins not useful in vertical writing modes (#10421) (Tuesday, 15 October)
- [csswg-drafts] [css-values-5] attr() and forwards compatible parsing (#11035) (Monday, 14 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Monday, 14 October)
- Re: [csswg-drafts] [css-scoping-1] Dynamic changes of state and attributes referenced by :host-context rules are pretty hard to handle efficiently. (#1914) (Friday, 11 October)
- Re: [csswg-drafts] [css-values-5][various] Better handling of arguments with commas (#9539) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-values-5] Does media-progress() really want the entire <media-feature> production for its progress value? (#10966) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-values-5] Disallow mix/random/tree-counting functions in some contexts (#10982) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-values-5] Syntax of progress() vs mix() functions (#10489) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-anchor-position] Should anchor() be validated at parse time when it is known invalid? (#10955) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-pseudo] `color-scheme` should be an allowed property for highlight pseudos (#11011) (Tuesday, 8 October)
- Re: [csswg-drafts] Auto Keyword value type of size Intrinsic vs Extrinsic. (#11009) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-inline] Is `text-box-edge` inherited or not? (#10904) (Tuesday, 8 October)
- Closed: [csswg-drafts] [css-values-5] Receive comma-separated arguments in `*-progress()` (#10862) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-values-5] Receive comma-separated arguments in `*-progress()` (#10862) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-values] Proposal: `sp` and `rsp` space glyph units (#10534) (Monday, 7 October)
- Re: [csswg-drafts] [css-break] Fragmented out-of-flow contained by box with cloned borders (#10553) (Monday, 7 October)
- Re: [csswg-drafts] [css-page-3] - looking for clarification of interaction of differing "page" properties and "break-after: avoid-page" for chapterhead pages (#10716) (Monday, 7 October)
- Re: [csswg-drafts] [css-inline] `text-box-edge: ideographic` and `ideographic-ink` should use ideographic fonts in the cascade list (#10928) (Monday, 7 October)
- Re: [csswg-drafts] [css-text-4] [text-autospace] Spacing across element boundaries for BiDi content (#10803) (Monday, 7 October)
- Re: [csswg-drafts] [css-inline][css-text][css-pseudo] Define more details of the "first formatted line" (#10990) (Wednesday, 2 October)
Fernando Serboncini via GitHub
firefoxic via GitHub
flashymittens via GitHub
Florian Rivoal via GitHub
- Re: [csswg-drafts] [css-text-4] Japanese text (in #jp-title-break) in Example 24 is unreadable, with dark color-scheme (#11099) (Tuesday, 29 October)
- Closed: [csswg-drafts] [css-text-4] Japanese text (in #jp-title-break) in Example 24 is unreadable, with dark color-scheme (#11099) (Tuesday, 29 October)
- [csswg-drafts] Pull Request: [css-ui-4] Editorial improvement; removes redundant group notation from outline property (Monday, 28 October)
- [csswg-drafts] Pull Request: [css-ui-4] Editorial improvement; removes redundant group notation from outline property (Monday, 28 October)
- [csswg-drafts] Pull Request: Fix the caret-animation example (Tuesday, 22 October)
- [csswg-drafts] Pull Request: Fix the caret-animation example (Tuesday, 22 October)
- [csswg-drafts] Pull Request: Fix the caret-animation example (Tuesday, 22 October)
- Re: [csswg-drafts] Fix the caret-animation example (#11016) (Tuesday, 22 October)
- [csswg-drafts] Pull Request: [css-ui-4] Editorial improvement; removes redundant group notation from outline-color property (Monday, 21 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Thursday, 3 October)
Florian via GitHub
fweth via GitHub
George Gloyens via GitHub
gitspeaks via GitHub
GoGabIt via GitHub
Guillaume via GitHub
- Re: [csswg-drafts] [css-conditional-5] More precisely define the syntax of `scroll-state-feature` (#11127) (Thursday, 31 October)
- Closed: [csswg-drafts] Gestion de version git hub gogab (#11128) (Thursday, 31 October)
- [csswg-drafts] [css-values-5][css-property-values-api-1] Case-sensitivity of identifiers from `<syntax>` (#11124) (Thursday, 31 October)
- Re: [csswg-drafts] [css-values-4][Editorial] `<condition>` type that other specs reference (#10457) (Thursday, 31 October)
- [csswg-drafts] Pull Request: [css-color-hdr-1] Accept `dynamic-range-limit-mix()` as a type instead of a literal function (Thursday, 31 October)
- [csswg-drafts] Pull Request: [css-color-hdr-1] Accept `dynamic-range-limit-mix()` as a type instead of a literal function (Thursday, 31 October)
- [csswg-drafts] [css-values-5] `mix()` should take `<keyframes-name>` instead of `<'animation-name'>` (#11121) (Thursday, 31 October)
- [csswg-drafts] [css-values-5] Does `container-progress()` really want the entire `<size-feature>` production for its progress value? (#11120) (Thursday, 31 October)
- Re: [csswg-drafts] [css-sizing-3]: `calc-size` links to itself (#11101) (Tuesday, 29 October)
- Closed: [csswg-drafts] [css-sizing-3]: `calc-size` links to itself (#11101) (Tuesday, 29 October)
- [csswg-drafts] Pull Request: Revert "[css-namespaces-3] Define <namespace-prefix> with case-sensitive <custom-ident>" (Friday, 25 October)
- [csswg-drafts] Pull Request: Revert "[css-namespaces-3] Define <namespace-prefix> with case-sensitive <custom-ident>" (Friday, 25 October)
- [csswg-drafts] Pull Request: [css-values-5] Allow a single `<syntax-component>` (Friday, 25 October)
- [csswg-drafts] Pull Request: [css-values-5] Allow a single `<syntax-component>` (Friday, 25 October)
- Re: [csswg-drafts] [css-values-5] Should an empty `{}` match `<declaration-value>` and `<any-value>` in functions? (#11043) (Tuesday, 22 October)
- Closed: [csswg-drafts] [css-values-5] Should an empty `{}` match `<declaration-value>` and `<any-value>` in functions? (#11043) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-values-5] Should an empty `{}` match `<declaration-value>` and `<any-value>` in functions? (#11043) (Friday, 18 October)
- Re: [csswg-drafts] [css-values-5] Should an empty `{}` match `<declaration-value>` and `<any-value>` in functions? (#11043) (Friday, 18 October)
- [csswg-drafts] [css-values-5] Should an empty `{}` match `<declaration-value>` and `<any-value>` in functions? (#11043) (Thursday, 17 October)
- Re: [csswg-drafts] [cssom-1] Serialization of feature values (#11041) (Thursday, 17 October)
- Re: [csswg-drafts] [cssom-1] Serialization of feature values (#11041) (Thursday, 17 October)
- Re: [csswg-drafts] [css-values-5] Should progress functions have a calculation tree as their internal representation? (#10979) (Thursday, 17 October)
- Re: [csswg-drafts] [css-values-5] Trailing comma in `attr()` (#8387) (Thursday, 17 October)
- [csswg-drafts] [css-values-5] `<any-value>` in functional `<general-enclosed>` should be a non-strict comma-containing production (#11042) (Wednesday, 16 October)
- [csswg-drafts] [cssom-1] Serialization of feature values (#11041) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-values-5] Trailing comma in `attr()` (#8387) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-values-5][various] Better handling of arguments with commas (#9539) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-values-5] Should progress functions have a calculation tree as their internal representation? (#10979) (Wednesday, 16 October)
- Re: [csswg-drafts] [cssom] clarification needed on sort order and lowercasing of media features (#533) (Tuesday, 15 October)
- Closed: [csswg-drafts] [cssom] clarification needed on sort order and lowercasing of media features (#533) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] Disallow mix/random/tree-counting functions in some contexts (#10982) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-values-5] Should progress functions have a calculation tree as their internal representation? (#10979) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-color-5] Allow using channel keywords in any calculation (#10983) (Wednesday, 9 October)
- [csswg-drafts] [css-values] Make mod/rem/random/log return a consistent type (#11012) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-values-5] Clarify how to determine the type of `<percentage>` in `container-progress()` and `media-progress()` (#10801) (Tuesday, 8 October)
- Closed: [csswg-drafts] [css-values-5] Clarify how to determine the type of `<percentage>` in `container-progress()` and `media-progress()` (#10801) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-shapes] Should `circle()` serialization omit the `center` value? (#10645) (Tuesday, 8 October)
- Closed: [csswg-drafts] [css-values-5] Should an arbitrary substitution nested within another be accepted in context? (#10337) (Saturday, 5 October)
- Re: [csswg-drafts] [css-values-5] Should an arbitrary substitution nested within another be accepted in context? (#10337) (Saturday, 5 October)
- Re: [csswg-drafts] [css-color-5] Clarification on `none` components in relative color syntax. (#10360) (Friday, 4 October)
- Re: [csswg-drafts] [css-color-5] Clarification on `none` components in relative color syntax. (#10360) (Friday, 4 October)
- Re: [csswg-drafts] [css-color-5] Allow using channel keywords in any calculation (#10983) (Thursday, 3 October)
- [csswg-drafts] [css-values-5] Resolve `first-valid()` at parse time (#10989) (Wednesday, 2 October)
- [csswg-drafts] Pull Request: [css-sizing-4] Avoid duplicating new values for logical properties (Tuesday, 1 October)
- [csswg-drafts] Pull Request: [css-sizing-4] Avoid duplicating new values for logical properties (Tuesday, 1 October)
- [csswg-drafts] [css-color-5] Allow using channel keywords in any calculation (#10983) (Tuesday, 1 October)
- [csswg-drafts] [css-values-5] Disallow mix/random/tree-counting functions in some contexts (#10982) (Tuesday, 1 October)
- [csswg-drafts] [css-values-5] Special case equal progress/start/end values in progress functions? (#10980) (Tuesday, 1 October)
- [csswg-drafts] [css-values-5] Should progress functions have a calculation tree as their internal representation? (#10979) (Tuesday, 1 October)
Hemi via GitHub
Herbert Braun via GitHub
hvanops via GitHub
i18u via GitHub
Ian Kilpatrick via GitHub
Isaac Muse via GitHub
Jacob Parker via GitHub
Jake Archibald via GitHub
James Addison via GitHub
James Craig via GitHub
JAWS-test via GitHub
Jeffrey Yasskin via GitHub
Jen Simmons via GitHub
Jenna Smith via GitHub
Jeroen Zwartepoorte via GitHub
jfkthame via GitHub
Jihye Hong via GitHub
JimJJewett via GitHub
Joakim via GitHub
Joeri Sebrechts via GitHub
Joey Arhar via GitHub
- Closed: [csswg-drafts] [css-ui] Pseudo-element for select's UA button (#10717) (Thursday, 31 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Thursday, 31 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Wednesday, 30 October)
- Re: [csswg-drafts] [selectors-4] Should we have :open and :closed? (#11039) (Monday, 28 October)
- Re: [csswg-drafts] [css-ui] Pseudo-elements for checkmark and dropdown icon for appearance:base `<select>` (#10908) (Thursday, 24 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Thursday, 24 October)
- Re: [csswg-drafts] [css-ui] Pseudo-elements for checkmark and dropdown icon for appearance:base `<select>` (#10908) (Thursday, 24 October)
- Re: [csswg-drafts] [css-pseudo-4] Add new pseudo-elements for customizable select (#10986) (Tuesday, 15 October)
- Re: [csswg-drafts] [selectors] Add `:open` or `:top-layer` pseudo class (#7319) (Tuesday, 15 October)
- [csswg-drafts] [selectors-4] Should we have :open and :closed? (#11039) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-ui] Pseudo-elements for checkmark and dropdown icon for appearance:base `<select>` (#10908) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo-4] Add new pseudo-elements for customizable select (#10986) (Monday, 14 October)
- Re: [csswg-drafts] [css-ui] UA stylesheet for appearance:base `<select>` (#10857) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-pseudo-4] Add new pseudo-elements for customizable select (#10986) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-ui] Pseudo-elements for checkmark and dropdown icon for appearance:base `<select>` (#10908) (Tuesday, 1 October)
- [csswg-drafts] Pull Request: [css-pseudo-4] Add new pseudo-elements for customizable select (Tuesday, 1 October)
Johannes Odland via GitHub
Jonathan Watt via GitHub
- [csswg-drafts] [css-anchor-position] Be more nuanced about last `@position-try` winning (#11080) (Thursday, 24 October)
- Re: [csswg-drafts] [css-anchor-position] Naming of the `inside` and `outside` `<anchor-side>` values (#11052) (Sunday, 20 October)
- Re: [csswg-drafts] [css-anchor-position] Naming of the `inside` and `outside` `<anchor-side>` values (#11052) (Sunday, 20 October)
- [csswg-drafts] [css-anchor-position] Naming of the `inside` and `outside` `<anchor-side>` values (#11052) (Saturday, 19 October)
- Re: [csswg-drafts] [css-anchor-position] The "acceptable anchor" algo seems broken (#11030) (Monday, 14 October)
- Re: [csswg-drafts] [css-anchor-position] The "acceptable anchor" algo seems broken (#11030) (Sunday, 13 October)
- [csswg-drafts] [css-anchor-position] The "acceptable anchor" algo seems broken (#11030) (Sunday, 13 October)
- [csswg-drafts] [css-anchor-position] "painted strictly before" for acceptable anchor is not the correct term (#11029) (Sunday, 13 October)
- [csswg-drafts] [css-anchor-position] The use of anchor-scope in the "acceptable anchor" algo (#11028) (Sunday, 13 October)
- [csswg-drafts] Pull Request: [css-anchor-position-1] Move Accessibility Implications section #11024 (Saturday, 12 October)
- [csswg-drafts] Pull Request: [css-anchor-position-1] Nest Validity subsections #11023 (Saturday, 12 October)
- Re: [csswg-drafts] [css-anchor-position] Potentially moving the "Conditional Hiding: the position-visibility property" section (#11025) (Saturday, 12 October)
- [csswg-drafts] [css-anchor-position] Potentially moving the "Conditional Hiding: the position-visibility property" section (#11025) (Saturday, 12 October)
- [csswg-drafts] [css-anchor-position] Potentially moving the "Accessibility Implications" section (#11024) (Saturday, 12 October)
- [csswg-drafts] [css-anchor-position] Potentially moving the `anchor()` function "Validity" section (#11023) (Saturday, 12 October)
- [csswg-drafts] [css-anchor-position] Potentially moving "The Anchor’s Position" section (#11022) (Saturday, 12 October)
Josh Tumath via GitHub
Joshua Comeau via GitHub
jsnkuhn via GitHub
Kagami Sascha Rosylight via GitHub
Keith Cirkel via GitHub
- Re: [csswg-drafts] [selectors] Pseudo-class to indicate when a slot has content (#6867) (Wednesday, 30 October)
- [csswg-drafts] Pull Request: [css-backgrounds-3]/[css-box-3]/[css-speech-1] drop parens around "see individual properties" (Tuesday, 29 October)
- [csswg-drafts] Pull Request: [css-backgrounds-3]/[css-box-3]/[css-speech-1] drop parens around "see individual properties" (Tuesday, 29 October)
- [csswg-drafts] Pull Request: [css-anchor-position-1]/[css-fonts-4]/[css-position-4] (editorial) make "see prose" value consistent (drop parens from outliers) (Tuesday, 29 October)
- [csswg-drafts] Pull Request: [css-anchor-position-1]/[css-fonts-4]/[css-position-4] (editorial) make "see prose" value consistent (drop parens from outliers) (Tuesday, 29 October)
- [csswg-drafts] Pull Request: [css-text-4] use "see individual properties" terminology for whitespace property (Tuesday, 29 October)
- [csswg-drafts] Pull Request: [css-text-4] use "see individual properties" terminology for whitespace property (Tuesday, 29 October)
- [csswg-drafts] [css-sizing-3]: `calc-size` links to itself (#11101) (Monday, 28 October)
- [csswg-drafts] Pull Request: [css-ui-4] Editorial improvement; removes redundant group notation from outline property (Saturday, 26 October)
- [csswg-drafts] Pull Request: [Editorial] [css-ui-4] Removes redundant group notation from outline-color property (Sunday, 20 October)
- [csswg-drafts] Pull Request: [Editorial] [css-ui-4] Removes redundant group notation from outline-color property (Sunday, 20 October)
- Re: [csswg-drafts] [css-mixins-1] how do `@function` rules cross shadow boundaries? (#10953) (Wednesday, 9 October)
- Closed: [csswg-drafts] [css-mixins-1] how do `@function` rules cross shadow boundaries? (#10953) (Wednesday, 9 October)
- Re: [csswg-drafts] [selectors] :local-link should have a more precise name (#10975) (Friday, 4 October)
- Re: [csswg-drafts] [selectors] :local-link should have a more precise name (#10975) (Friday, 4 October)
Keith Ealanta via GitHub
Kenneth Hoff via GitHub
kevers-google via GitHub
Kevin Babbitt via GitHub
Kevin Doughty via GitHub
Khushal Sagar via GitHub
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Wednesday, 30 October)
- [csswg-drafts] [css-view-transitions-2] Namespacing id vs css based view transition names (#11112) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] Define behavior of scrollbars and overflow with layered capture (#11079) (Thursday, 24 October)
- Re: [csswg-drafts] [css-view-transitions-2] when copying css properties for layered capture, resolve lengths to a fixed value (#11077) (Thursday, 24 October)
- Closed: [csswg-drafts] [css-view-transitions-2] when copying css properties for layered capture, resolve lengths to a fixed value (#11077) (Thursday, 24 October)
- Re: [csswg-drafts] [css-view-transitions-2] how do we decide whether to use layered capture? (#11078) (Thursday, 24 October)
- Re: [csswg-drafts] [css-view-transitions] Users need to be able to disable view transitions (#10267) (Thursday, 24 October)
- [csswg-drafts] [css-view-transitions-2] how do we decide whether to use layered capture? (#11078) (Tuesday, 22 October)
- [csswg-drafts] [css-view-transitions-2] when copying css properties for layered capture, resolve lengths to a fixed value (#11077) (Tuesday, 22 October)
- Closed: [csswg-drafts] [css-view-transition] "capture the new state" and "capture the old state" are subtly different. (#11071) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transition] "capture the new state" and "capture the old state" are subtly different. (#11071) (Tuesday, 22 October)
- [csswg-drafts] Pull Request: [css-view-transitions-1] Fix for fragmented boxes in new DOM. (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transition] "capture the new state" and "capture the old state" are subtly different. (#11071) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transitions-2] Optionally capture some properties (e.g. opacity/border) as style instead of snapshot (#10585) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-view-transitions-2] Optionally capture some properties (e.g. opacity/border) as style instead of snapshot (#10585) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-view-transitions-*] TPAC breakout session 2024 (#10945) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-view-transitions-*] TPAC breakout session 2024 (#10945) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-view-transitions-2] view-transition-name determined by element (#8320) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-view-transitions-2] Clarify a few nesting details (#10964) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-view-transitions-2] Should `::view-transition-group(auto)` match `view-transition-name: auto`? (#10978) (Tuesday, 1 October)
Kilian Valkhof via GitHub
Koji Ishii via GitHub
- Re: [csswg-drafts] [css-text-4] use "see individual properties" terminology for whitespace property (#11106) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-text-4] `text-spacing-trim` is harmful for Yu Gothic UI (system-ui in Japanese Windows) (#11074) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-pseudo] Should the "first formatted line" propagate into a different BFC? (#11038) (Friday, 18 October)
- Re: [csswg-drafts] [css-inline][css-text][css-pseudo] Define more details of the "first formatted line" (#10990) (Tuesday, 15 October)
- [csswg-drafts] [css-pseudo] Should the "first formatted line" propagate into a different BFC? (#11038) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-inline][css-text][css-pseudo] Define more details of the "first formatted line" (#10990) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-text] Use the Unicode East Asian Auto Spacing for `text-autospace` (#11013) (Thursday, 10 October)
- Re: [csswg-drafts] [css-inline] `text-box-edge: ideographic` and `ideographic-ink` should use ideographic fonts in the cascade list (#10928) (Wednesday, 9 October)
- [csswg-drafts] [css-text] Use the Unicode East Asian Auto Spacing for `text-autospace` (#11013) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-inline][css-text][css-pseudo] Define more details of the "first formatted line" (#10990) (Sunday, 6 October)
- Re: [csswg-drafts] [css-inline][css-text][css-pseudo] Define more details of the "first formatted line" (#10990) (Friday, 4 October)
- [csswg-drafts] [css-inline][css-text][css-pseudo] Define more details of the "first formatted line" (#10990) (Wednesday, 2 October)
L. David Baron via GitHub
Lea Verou via GitHub
- Re: [csswg-drafts] [css-values-5] Introduce nth-item() (#11103) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values-5] if() conditions with calc() comparisons (#11104) (Tuesday, 29 October)
- Re: [csswg-drafts] [selectors] :local-link should have a more precise name (#10975) (Monday, 28 October)
- Re: [csswg-drafts] [selectors] :local-link should have a more precise name (#10975) (Monday, 28 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Friday, 25 October)
- Re: [csswg-drafts] [css-cascade] Evaluate cascade order of ::slotted and global styles in the same conditions (#6466) (Friday, 25 October)
- Re: [csswg-drafts] [selectors] `:user-interacted` pseudo-class to match controls the user has interacted with (#11065) (Friday, 25 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Friday, 25 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Friday, 25 October)
- Re: [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Thursday, 24 October)
- Re: [csswg-drafts] [selectors] `:user-interacted` pseudo-class to match controls the user has interacted with (#11065) (Thursday, 24 October)
- Re: [csswg-drafts] [css-cascade][css-syntax] New `!revertable` flag to mark a declaration as "can be reverted when IACVT" (#10443) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-scoping][selectors] `:root` should resolve to `:host` in shadow trees (#11000) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-scoping] `:has-shadow` pseudo-class (#11007) (Tuesday, 22 October)
- [csswg-drafts] [selectors] `:user-interacted` pseudo-class to match controls the user has interacted with (#11065) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-scoping] `:has-shadow` pseudo-class (#11007) (Monday, 21 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Friday, 11 October)
- Re: [csswg-drafts] [selectors] `/idref()/` combinator to follow element references for arbitrary IDREF attributes (#10970) (Thursday, 10 October)
- [csswg-drafts] [css-scoping] `:has-shadow` pseudo-class (#11007) (Monday, 7 October)
- Re: [csswg-drafts] [css-cascade] Outside `@scope`, `:scope` should resolve to `:host` in shadow trees (#11000) (Friday, 4 October)
- Re: [csswg-drafts] [selectors] :local-link should have a more precise name (#10975) (Friday, 4 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Friday, 4 October)
- Re: [csswg-drafts] [selectors] :local-link should have a more precise name (#10975) (Friday, 4 October)
- Re: [csswg-drafts] [selectors] :local-link should have a more precise name (#10975) (Friday, 4 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Friday, 4 October)
- Re: [csswg-drafts] [css-color-5] Clarification on `none` components in relative color syntax. (#10360) (Friday, 4 October)
- [csswg-drafts] `:predefined` pseudo-class for built-ins (i.e. not custom elements) (#11001) (Friday, 4 October)
- [csswg-drafts] [css-cascade] Outside `@scope`, `:scope` should resolve to `:host` in shadow trees (#11000) (Friday, 4 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Thursday, 3 October)
- Re: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Thursday, 3 October)
- Re: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Wednesday, 2 October)
- Re: [csswg-drafts] [selectors] `/idref()/` combinator to follow element references for arbitrary IDREF attributes (#10970) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Tuesday, 1 October)
Lucas via GitHub
Luis Pato via GitHub
Luke Warlow via GitHub
mantou via GitHub
Marcel via GitHub
Marcus Blättermann via GitHub
Marius Gundersen via GitHub
Mark via GitHub
Martin Thomson via GitHub
Matthias Zöchling via GitHub
Mattias Hällkvist via GitHub
mattwoodrow via GitHub
Mayank via GitHub
Michael Gibson via GitHub
Miriam Suzanne via GitHub
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Thursday, 24 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade] Evaluate cascade order of ::slotted and global styles in the same conditions (#6466) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-conditional] Element queries (#10509) (Friday, 18 October)
- Re: [csswg-drafts] [css-contain][css-overflow] Setting containment on root should not make scrolling impossible (#9003) (Friday, 18 October)
- Re: [csswg-drafts] [css-contain][css-overflow] Setting containment on root should not make scrolling impossible (#9003) (Thursday, 17 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Monday, 14 October)
- Re: [csswg-drafts] [css-cascade] A way to escape the current cascade layer and render styles in the parent layer (`@layer ..`) (#11010) (Monday, 14 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Friday, 11 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Thursday, 10 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Thursday, 10 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Thursday, 10 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Thursday, 10 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-cascade] A way to escape the current cascade layer and render styles in the parent layer (`@layer ..`) (#11010) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-mixins-1] how do `@function` rules cross shadow boundaries? (#10953) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-mixins] Should `result` be mandatory in `@function`? (#10562) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Wednesday, 9 October)
- Closed: [csswg-drafts] [css-cascade-6] Publish an updated WD (#10370) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-cascade-5] `revert-layer` in element-attached styles (#10934) (Wednesday, 2 October)
mlandisbqs via GitHub
Monknow via GitHub
Munira via GitHub
Naman Goel via GitHub
Natalie Weizenbaum via GitHub
Nehuen Prados via GitHub
Nicky McCurdy via GitHub
Nicolas Hoffmann via GitHub
Nicole Sullivan via GitHub
Nicolò Ribaudo via GitHub
NicTanghe via GitHub
Noam Rosenthal via GitHub
- Re: [csswg-drafts] [css-view-transitions-2] Namespacing id vs css based view transition names (#11112) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] Namespacing id vs css based view transition names (#11112) (Thursday, 31 October)
- Re: [csswg-drafts] [css-properties-values-api] "Property registration cannot be scoped" differs from all implementations in a consistent way (#10541) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-properties-values-api] "Property registration cannot be scoped" differs from all implementations in a consistent way (#10541) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] how do we decide whether to use layered capture? (#11078) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] Optionally capture some properties (e.g. opacity/border) as style instead of snapshot (#10585) (Wednesday, 30 October)
- Closed: [csswg-drafts] [css-view-transitions-2] Using 'was created via cross-origin redirects' Document creation state causes unexpected results (#11063) (Thursday, 24 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Wednesday, 23 October)
- [csswg-drafts] [css-view-transitions-2] Define behavior of scrollbars and overflow with layered capture (#11079) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-view-transitions-2] when copying css properties for layered capture, resolve lengths to a fixed value (#11077) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-view-transitions-2] how do we decide whether to use layered capture? (#11078) (Wednesday, 23 October)
- Closed: [csswg-drafts] [css-shapes-2] Interpolation between `shape()` and `path()` needs more detail (#10740) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Tuesday, 22 October)
- [csswg-drafts] Pull Request: [css-view-transitions-2] Allow transitions when traversing into a document that was created using cross-origin redirects (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transitions-2] Using 'was created via cross-origin redirects' Document creation state causes unexpected results (#11063) (Tuesday, 22 October)
- Closed: [csswg-drafts] [css-view-transitions] Skip on activation doesn't provide a reason (#11059) (Monday, 21 October)
- Closed: [csswg-drafts] [css-view-transitions] Broken state management in "capture the old state" (#11058) (Monday, 21 October)
- Re: [csswg-drafts] [css-view-transitions] Broken state management in "capture the old state" (#11058) (Monday, 21 October)
- Re: [csswg-drafts] [css-view-transitions] Broken state management in "capture the old state" (#11058) (Monday, 21 October)
- Re: [csswg-drafts] [css-view-transitions] Broken state management in "capture the old state" (#11058) (Monday, 21 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Monday, 21 October)
- [csswg-drafts] Pull Request: [css-view-transitions-2] First pass at layered capture (Thursday, 17 October)
- Re: [csswg-drafts] [css-view-transitions-2] Optionally capture some properties (e.g. opacity/border) as style instead of snapshot (#10585) (Thursday, 17 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Thursday, 17 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Thursday, 17 October)
- Re: [csswg-drafts] Republishing Tasks Permathread (#6900) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-view-transitions-2] Optionally capture some properties (e.g. opacity/border) as style instead of snapshot (#10585) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-view-transitions-2] Optionally capture some properties (e.g. opacity/border) as style instead of snapshot (#10585) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-view-transitions-2] `view-transition-group` and tree-scoping (#10633) (Monday, 14 October)
- Closed: [csswg-drafts] [css-view-transition-2] Should non-default `view-transition-group` act like `contain`? (#10780) (Monday, 14 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Thursday, 10 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Monday, 7 October)
- Re: [csswg-drafts] [css-view-transitions-2] Should `::view-transition-group(auto)` match `view-transition-name: auto`? (#10978) (Friday, 4 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Friday, 4 October)
- [csswg-drafts] Pull Request: [css-view-transitions-1] Don't animate transform/size by default when prefers-reduced-motion is on (Thursday, 3 October)
- [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Thursday, 3 October)
- Re: [csswg-drafts] [css-view-transitions-2] view-transition-name determined by element (#8320) (Wednesday, 2 October)
- [csswg-drafts] Pull Request: [css-shapes-2][css-borders-4] Add myself as editor (Wednesday, 2 October)
- Re: [csswg-drafts] [css-view-transitions-2] view-transition-name determined by element (#8320) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-view-transitions-2] view-transition-name determined by element (#8320) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-view-transitions-2] Clarify a few nesting details (#10964) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-shapes-2] Consider allowing `<position>` for the `from` and some other points (#10644) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-properties-values-api] "Property registration cannot be scoped" differs from all implementations in a consistent way (#10541) (Tuesday, 1 October)
- Closed: [csswg-drafts] [css-view-transitions-2] view-transition-name determined by element (#8320) (Tuesday, 1 October)
- [csswg-drafts] Pull Request: [css-shapes-2] Clarify shape/path interpolation (Tuesday, 1 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Tuesday, 1 October)
- [csswg-drafts] [css-view-transitions-2] Should `::view-transition-group(auto)` match `view-transition-name: auto`? (#10978) (Tuesday, 1 October)
Oliver Williams via GitHub
Omar Ahmed via GitHub
Oriol Brufau via GitHub
- Re: [csswg-drafts] [cssom-view] Spec for offsetTop/Left does not match impls when offsetParent is `position:static` `<body>` element (#10549) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-values] Proposal for an `all-vars` property to reset all custom properties (#11105) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-sizing-4] How does height: stretch interact with margin collapsing with parent (#11044) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values] Proposal for an `all-vars` property to reset all custom properties (#11105) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-sizing-4] How does height: stretch interact with margin collapsing with parent (#11044) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values] Proposal for an `all-vars` property to reset all custom properties (#11105) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values-5] if() conditions with calc() comparisons (#11104) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-writing-modes-4] Allow sideways-x and vertical-x to share a block formatting context? (#10714) (Sunday, 27 October)
- Re: [csswg-drafts] [css-sizing] Has #4951 been amended by a later resolution? (#11093) (Sunday, 27 October)
- Re: [csswg-drafts] using special values like max-content in functions (#5554) (Sunday, 27 October)
- [csswg-drafts] [css-sizing] Has #4951 been amended by a later resolution? (#11093) (Friday, 25 October)
- Re: [csswg-drafts] [css-sizing-4] min/max size transfers across aspect-ratio (#6071) (Friday, 25 October)
- Re: [csswg-drafts] [cssom][web-animations-1] Consistent behavior for invalid pseudos in getComputedStyle/getAnimations (#11081) (Friday, 25 October)
- Re: [csswg-drafts] Proposal: Transparent window (#7281) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Thursday, 24 October)
- Re: [csswg-drafts] [selectors] `:user-interacted` pseudo-class to match controls the user has interacted with (#11065) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values] Extend sibling-index() and sibling-count() with a selector argument (#9572) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-sizing] Nobody follows the spec about cyclic percentages in min sizing properties (#10969) (Wednesday, 23 October)
- Re: [csswg-drafts] [selectors] `:user-interacted` pseudo-class to match controls the user has interacted with (#11065) (Tuesday, 22 October)
- Re: [csswg-drafts] Proposal: Transparent window (#7281) (Tuesday, 22 October)
- [csswg-drafts] [css-sizing] `stretch` should enforce a non-negative content size (#11076) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-cascade][css-syntax] New `!revertable` flag to mark a declaration as "can be reverted when IACVT" (#10443) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-grid-3][masonry] Masonry Syntax Designer/Developer Feedback (#11060) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-variables-1] Expose pending substitution value? (#11055) (Monday, 21 October)
- Re: [csswg-drafts] [css-scoping][selectors] `:root` should resolve to `:host` in shadow trees (#11000) (Sunday, 20 October)
- Re: [csswg-drafts] [css-values] Request for New CSS Unit Proposal (pem Unit) (#11051) (Saturday, 19 October)
- Re: [csswg-drafts] [css-text] Make first-letter work with inline text (#11047) (Friday, 18 October)
- Re: [csswg-drafts] [css-sizing] Does indefinite `stretch` behave as automatic size or as initial value? (#11006) (Friday, 18 October)
- Re: [csswg-drafts] [css-sizing-4] How does height: stretch interact with margin collapsing with parent (#11044) (Friday, 18 October)
- Re: [csswg-drafts] [css-values-5] Should an empty `{}` match `<declaration-value>` and `<any-value>` in functions? (#11043) (Friday, 18 October)
- Re: [csswg-drafts] [css-sizing-4] How does height: stretch interact with margin collapsing with parent (#11044) (Thursday, 17 October)
- Re: [csswg-drafts] [css-sizing] Does indefinite `stretch` behave as automatic size or as initial value? (#11006) (Thursday, 17 October)
- Re: [csswg-drafts] [css-sizing-4] How does height: stretch interact with margin collapsing with parent (#11044) (Thursday, 17 October)
- Re: [csswg-drafts] [css-sizing-4] How does height: stretch interact with margin collapsing with parent (#11044) (Thursday, 17 October)
- Re: [csswg-drafts] Proposal: Transparent window (#7281) (Thursday, 17 October)
- Re: [csswg-drafts] [css-sizing-4] How does height: stretch interact with margin collapsing with parent (#11044) (Thursday, 17 October)
- Re: [csswg-drafts] Proposal: Transparent window (#7281) (Thursday, 17 October)
- Re: [csswg-drafts] [cssom-1] Serialization of feature values (#11041) (Thursday, 17 October)
- Re: [csswg-drafts] [css-sizing] min/max-content contribution is an outer size, not an inner one (#10985) (Thursday, 17 October)
- Closed: [csswg-drafts] [css-sizing] min/max-content contribution is an outer size, not an inner one (#10985) (Thursday, 17 October)
- Re: [csswg-drafts] [css-sizing] Does indefinite `stretch` behave as automatic size or as initial value? (#11006) (Thursday, 17 October)
- Re: [csswg-drafts] [cssom-1] Serialization of feature values (#11041) (Thursday, 17 October)
- Re: [csswg-drafts] [css-pseudo] Should the "first formatted line" propagate into a different BFC? (#11038) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-values-4] `<integer>` grammar terms and `<number>`-returning functions (#11040) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-sizing-3] Content contribution of min-inline-size:fit-content and max-inline-size:fit-content (#10721) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-sizing-3] Content contribution of min-inline-size:fit-content and max-inline-size:fit-content (#10721) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] attr() and forwards compatible parsing (#11035) (Monday, 14 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Monday, 14 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Monday, 14 October)
- Re: [csswg-drafts] Mixing :is() (or equivalent) with pseudo-elements (#9702) (Monday, 14 October)
- Re: [csswg-drafts] css expression inheritance (#2749) (Monday, 14 October)
- Re: [csswg-drafts] [css-scoping][selectors] `:root` should resolve to `:host` in shadow trees (#11000) (Sunday, 13 October)
- Re: [csswg-drafts] [css-content] ::marker content available for assistive technology (#11003) (Saturday, 12 October)
- Re: [csswg-drafts] [css-values] Proposal: add sibling-count() and sibling-index() (#4559) (Saturday, 12 October)
- Re: [csswg-drafts] [css-conditional-5] comma-separated container query aren't supported on browsers (#11015) (Friday, 11 October)
- Re: [csswg-drafts] [css-conditional-5] comma-separated container query aren't supported on browsers (#11015) (Friday, 11 October)
- Closed: [csswg-drafts] [css-conditional-5] comma-separated container query aren't supported on browsers (#11015) (Friday, 11 October)
- Re: [csswg-drafts] Why there's no horizontal-rtl and horizontal-ltr values in the "Writing mode" property? (#10731) (Friday, 11 October)
- Re: [csswg-drafts] [css-sizing] Does indefinite `stretch` behave as automatic size or as initial value? (#11006) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-values-5][various] Better handling of arguments with commas (#9539) (Tuesday, 8 October)
- Re: [csswg-drafts] Auto Keyword value type of size Intrinsic vs Extrinsic. (#11009) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-grid-3] Designer/developer feedback on masonry layout (#10233) (Monday, 7 October)
- Re: [csswg-drafts] [css-sizing] Does indefinite `stretch` behave as automatic size or as initial value? (#11006) (Saturday, 5 October)
- [csswg-drafts] [css-sizing] Does indefinite `stretch` behave as automatic size or as initial value? (#11006) (Saturday, 5 October)
- Re: [csswg-drafts] [css-tables][css-sizing] What sizing keywords allow fixed table mode? (#10937) (Saturday, 5 October)
- Re: [csswg-drafts] [css-inline][css-text][css-pseudo] Define more details of the "first formatted line" (#10990) (Friday, 4 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Friday, 4 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Friday, 4 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Friday, 4 October)
- Re: [csswg-drafts] [css-inline][css-text][css-pseudo] Define more details of the "first formatted line" (#10990) (Friday, 4 October)
- [csswg-drafts] [css-sizing] min/max-content contribution is an outer size, not an inner one (#10985) (Tuesday, 1 October)
Patrick Brosset via GitHub
Pekka Paalanen via GitHub
Philip Rogers via GitHub
Preeti yadav via GitHub
PupilTong via GitHub
Quentin Albert via GitHub
r12a via GitHub
Raura via GitHub
rgpublic via GitHub
rjgotten via GitHub
Rob Mayer via GitHub
Robert Flack via GitHub
- [csswg-drafts] [css-overflow-5] Tree structure of scroll container controls. (#11125) (Thursday, 31 October)
- Re: [csswg-drafts] [css-scroll-snap-2] Why is scroll-start measured against the width/height of the scrollport? (#8854) (Thursday, 31 October)
- Re: [csswg-drafts] [web-animations-1] commitStyles followed by cancel should not trigger a transition (#11084) (Thursday, 31 October)
- Re: [csswg-drafts] [overflow-5] Allowing markers to be active even when not scrollable to aligned position. (#10738) (Wednesday, 30 October)
- Closed: [csswg-drafts] [cssom-view] Add scrollIntoView parameter to only scroll the nearest scrolling container (#10451) (Wednesday, 30 October)
- Re: [csswg-drafts] [cssom-view] Add scrollIntoView parameter to only scroll the nearest scrolling container (#10451) (Wednesday, 30 October)
- Re: [csswg-drafts] [cssom-view] Spec for offsetTop/Left does not match impls when offsetParent is `position:static` `<body>` element (#10549) (Wednesday, 30 October)
- Re: [csswg-drafts] [overflow-5] Allowing markers to be active even when not scrollable to aligned position. (#10738) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-overflow-5] What is the active :checked marker when some markers point to elements within different scrolling containers? (#11098) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-overflow-5] Focus order of generated controls (#10912) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-overflow-5] Creating scroll-marker groups within which to select an active marker (#10916) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-overflow-5] Bikeshed pseudoclasses for active scroll-marker (#10918) (Tuesday, 29 October)
- Re: [csswg-drafts] [web-animations-2] Progress APIs (#8799) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-overflow-5] What is the active :checked marker when some markers point to elements within different scrolling containers? (#11098) (Monday, 28 October)
- [csswg-drafts] [css-overflow-5] What is the active :checked marker when some markers point to elements within different scrolling containers? (#11098) (Monday, 28 October)
- Re: [csswg-drafts] [cssom][web-animations-1] Consistent behavior for invalid pseudos in getComputedStyle/getAnimations (#11081) (Friday, 25 October)
- Re: [csswg-drafts] [web-animations-2] Custom effects (#6861) (Friday, 25 October)
- Re: [csswg-drafts] [web-animations-1] commitStyles followed by cancel should not trigger a transition (#11084) (Friday, 25 October)
- Re: [csswg-drafts] [web-animations-1] commitStyles followed by cancel should not trigger a transition (#11084) (Friday, 25 October)
- Re: [csswg-drafts] [web-animations-2] Custom effects (#6861) (Thursday, 24 October)
- [csswg-drafts] Pull Request: [cssom-view-1] Apply scroll snap to scroll-into-view-position (Tuesday, 22 October)
- Re: [csswg-drafts] [scroll-animations] Can progress-based timelines report a current time outside of the `[0%-100%]` range? (#11033) (Friday, 18 October)
- [csswg-drafts] Pull Request: [css-overflow-5] Editorial improvements to css-overflow-5 scroll markers (Friday, 18 October)
- [csswg-drafts] [css-env-1] Maximum safe area inset values to allow sliding bottom bar (#11019) (Thursday, 10 October)
robglidden via GitHub
Romain Menke via GitHub
- Re: [csswg-drafts] [css-conditional-5] More precisely define the syntax of `scroll-state-feature` (#11127) (Thursday, 31 October)
- [csswg-drafts] [css-conditional-5] More precisely define the syntax of `scroll-state-feature` (#11127) (Thursday, 31 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] Using `if()` to do dark/light switching of image urls. (#10577) (Thursday, 10 October)
- Re: [csswg-drafts] [css-cascade] A way to escape the current cascade layer and render styles in the parent layer (`@layer ..`) (#11010) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Friday, 4 October)
- Re: [csswg-drafts] [css-cascade] Can we use `@scope` for style isolation? (#11002) (Friday, 4 October)
- Re: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Wednesday, 2 October)
Roman Komarov via GitHub
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-values] Extend sibling-index() and sibling-count() with a selector argument (#9572) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-values] Proposal: `descendant-count()` function (#11069) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Tuesday, 22 October)
- [csswg-drafts] `[css-values]` Proposal: `descendant-count()` function (#11069) (Tuesday, 22 October)
- [csswg-drafts] [css-values] Proposal: `children-count()` function (#11068) (Tuesday, 22 October)
- [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Tuesday, 22 October)
- Re: [csswg-drafts] Proposal: Transparent window (#7281) (Saturday, 19 October)
- Re: [csswg-drafts] [css-cascade][css-syntax] New `!revertable` flag to mark a declaration as "can be reverted when IACVT" (#10443) (Thursday, 10 October)
- Re: [csswg-drafts] [css-anchor-position] Should anchor() be validated at parse time when it is known invalid? (#10955) (Wednesday, 9 October)
rthrejheytjyrtj545 via GitHub
Rune Lillesveen via GitHub
- Re: [csswg-drafts] [css-conditional][css-anchor-position][scroll-animations] Snapshotting post-layout State (#10796) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-anchor-position] Better handling of scroll position for fixpos elements on first layout (#10999) (Friday, 25 October)
- Re: [csswg-drafts] [css-anchor-position] Better handling of scroll position for fixpos elements on first layout (#10999) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-conditional-5] Link scroll-state snapshotting to cssom-view #10796 (#11056) (Monday, 21 October)
- [csswg-drafts] Pull Request: [css-conditional-5] Link scroll-state snapshotting to cssom-view #10796 (Monday, 21 October)
- Re: [csswg-drafts] [cssom] There should be a way to get Character Position of the Stylesheet Elements (#10480) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-conditional] @container scroll-state(snapped) and snapchanged vs snapchanging (#10784) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-conditional] @container scroll-state(snapped) and snapchanged vs snapchanging (#10784) (Tuesday, 15 October)
- Re: [csswg-drafts] [cssom-view-1] Add: run snapshot post-layout state steps #10796 (#11037) (Tuesday, 15 October)
- [csswg-drafts] Pull Request: [cssom-view-1] Add: run snapshot post-layout state steps #10796 (Tuesday, 15 October)
- [csswg-drafts] Pull Request: [css-conditional-5] snapped matches scrollsnapchanging #10784 (Monday, 14 October)
Sainan via GitHub
Sam Atkins via GitHub
Sam Sneddon via GitHub
Sam Weinig via GitHub
Sam Windsor via GitHub
Samuel Bradshaw via GitHub
Sanket Joshi via GitHub
Sara Joy via GitHub
Sean van Zuidam via GitHub
Sebastian Zartner via GitHub
Shauna Gordon via GitHub
Shaw Jia via GitHub
Simon Fraser via GitHub
- Re: [csswg-drafts] [css-images] Should EXIF image orientation data be ignored if it comes after the image data in the encoded image? (#11114) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-images] Should EXIF image orientation data be ignored if it comes after the image data in the encoded image? (#11114) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-images] Should EXIF image orientation data be ignored if it comes after the image data in the encoded image? (#11114) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-images] Should CSS decorative images respect EXIF-orientation by default (#4165) (Wednesday, 30 October)
- [csswg-drafts] [css-images] Should EXIF image orientation data be ignored if it comes after the image data in the encoded image? (#11114) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-ui][selectors][mediaqueries] Expose current scrolling direction (#6400) (Thursday, 24 October)
- Re: [csswg-drafts] Add `@container scroll-state(direction)` to [css-conditional-5] (#11082) (Thursday, 24 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Monday, 21 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Sunday, 20 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Sunday, 20 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Thursday, 17 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Thursday, 17 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Wednesday, 9 October)
- Re: [csswg-drafts] [cssom-view] Expose small/large viewport dimensions of the layout viewport (#8709) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Tuesday, 1 October)
Stephanie Eckles via GitHub
Stephen Chenney via GitHub
- [csswg-drafts] Pull Request: [CSS-UI-4] Clarify which element caret properties come from (Wednesday, 30 October)
- Re: [csswg-drafts] [css-highlight-api] Feedback: the global string-keyed registry makes usage very hard (#11095) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-highlight-api] Should pseudo-classes work with Custom Highlights (#7647) (Wednesday, 30 October)
- Closed: [csswg-drafts] [css-ui-4] inteference with the caret blinking and the ability to animate its color (#9707) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-pseudo] Safari’s ::selection “wash” and UA tweaks to highlight colors (#6853) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo-4] Clarify text decorations in ::spelling-error and ::grammar-error (#9633) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] `color-scheme` should be an allowed property for highlight pseudos (#11011) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] highlight pseudos and non-applicable properties (#7591) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-pseudo] highlight pseudos and non-applicable properties (#7591) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-pseudo] `color-scheme` should be an allowed property for highlight pseudos (#11011) (Thursday, 10 October)
- [csswg-drafts] Pull Request: Fix the caret-animation example (Thursday, 10 October)
- Re: [csswg-drafts] [css-ui-4] inteference with the caret blinking and the ability to animate its color (#9707) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-ui-4] inteference with the caret blinking and the ability to animate its color (#9707) (Friday, 4 October)
Steve Orvell via GitHub
Tab Atkins Jr. via GitHub
- Re: [csswg-drafts] [css-values-5] attr() and forwards compatible parsing (#11035) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-values-5] Using `if()` to do dark/light switching of image urls. (#10577) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-sizing-4] How does height: stretch interact with margin collapsing with parent (#11044) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values-5] if() conditions with calc() comparisons (#11104) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values-5] Introduce nth-item() (#11103) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-values-4] Switch advanced attr() to being var()-like (#4482) (Monday, 28 October)
- Closed: [csswg-drafts] [css-values-4] Switch advanced attr() to being var()-like (#4482) (Monday, 28 October)
- Re: [csswg-drafts] [css-values-5] if() conditions with calc() comparisons (#11104) (Monday, 28 October)
- [csswg-drafts] [css-values-5] Introduce nth-item() (#11103) (Monday, 28 October)
- Re: [csswg-drafts] [css-values-5] Forwards compatibility for inline `if()` (#10818) (Monday, 28 October)
- Closed: [csswg-drafts] [css-values-5] Forwards compatibility for inline `if()` (#10818) (Monday, 28 October)
- Re: [csswg-drafts] [css-values-5] What is the MVP for inline conditionals on custom properties? (#10064) (Friday, 25 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Friday, 25 October)
- Closed: [csswg-drafts] [css-values] Security concerns regarding attr() (#5092) (Friday, 25 October)
- [csswg-drafts] Pull Request: [css-values-5] Allow a single `<syntax-component>` (Friday, 25 October)
- Re: [csswg-drafts] [css-values-5] Allow a single `<syntax-component>` (#11088) (Friday, 25 October)
- Re: [csswg-drafts] [css-values] Security concerns regarding attr() (#5092) (Friday, 25 October)
- Re: [csswg-drafts] [css-values-5] Add `resolution` to `<attr-type>` (#9752) (Friday, 25 October)
- Closed: [csswg-drafts] [css-values-5] Add `resolution` to `<attr-type>` (#9752) (Friday, 25 October)
- Re: [csswg-drafts] [css-values] attr()'s type system is inconsistent with other things (#10437) (Friday, 25 October)
- Closed: [csswg-drafts] [css-values] attr()'s type system is inconsistent with other things (#10437) (Friday, 25 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values-5] [css-overflow-4]How does `line-clamp` transition from `<integer>` to `auto` or `none`? (#10502) (Thursday, 24 October)
- Re: [csswg-drafts] Proposal: Transparent window (#7281) (Thursday, 24 October)
- Re: [csswg-drafts] Proposal: Transparent window (#7281) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values] Proposal: `descendant-count()` function (#11069) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Thursday, 24 October)
- Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141) (Thursday, 24 October)
- Re: [csswg-drafts] [css-anchor-position] Better handling of scroll position for fixpos elements on first layout (#10999) (Thursday, 24 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-anchor-position] Better handling of scroll position for fixpos elements on first layout (#10999) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-values] Proposal: `round()` to a finite scale (#11067) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Monday, 21 October)
- Closed: [csswg-drafts] [css-variables-1] Expose pending substitution value? (#11055) (Monday, 21 October)
- Re: [csswg-drafts] [css-values] Add a way to set longhands to the corresponding expansion of a shorthand value (#8055) (Monday, 21 October)
- Re: [csswg-drafts] [css-values] Add a way to set longhands to the corresponding expansion of a shorthand value (#8055) (Monday, 21 October)
- Re: [csswg-drafts] [css-variables-1] Expose pending substitution value? (#11055) (Monday, 21 October)
- Re: [csswg-drafts] [css-anchor-position] Naming of the `inside` and `outside` `<anchor-side>` values (#11052) (Sunday, 20 October)
- Re: [csswg-drafts] [css-values-5] Should progress functions have a calculation tree as their internal representation? (#10979) (Wednesday, 16 October)
- Re: [csswg-drafts] [cssom-view] Consider making scroll methods return promises (#1562) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-values-5] Trailing comma in `attr()` (#8387) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-values-5][various] Better handling of arguments with commas (#9539) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-align][css-position][css-anchor-position] Introduce "document containing block" for some purposes? (#10861) (Tuesday, 15 October)
- Re: [csswg-drafts] [selectors-4] Should we have :open and :closed? (#11039) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-anchor-position] Better handling of scroll position for fixpos elements on first layout (#10999) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5][various] Better handling of arguments with commas (#9539) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] Forwards compatibility for inline `if()` (#10818) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] Normalized attr() substitution value (#10503) (Tuesday, 15 October)
- [csswg-drafts] [css-values-4] `<integer>` grammar terms and `<number>`-returning functions (#11040) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-values-5] Should progress functions have a calculation tree as their internal representation? (#10979) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] Should progress functions have a calculation tree as their internal representation? (#10979) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] attr() and forwards compatible parsing (#11035) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Tuesday, 15 October)
- Closed: [csswg-drafts] [css-values-5][various] Better handling of arguments with commas (#9539) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5][various] Better handling of arguments with commas (#9539) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Monday, 14 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Monday, 14 October)
- Re: [csswg-drafts] [css-anchor-position] "painted strictly before" for acceptable anchor is not the correct term (#11029) (Monday, 14 October)
- Closed: [csswg-drafts] [css-anchor-position] "painted strictly before" for acceptable anchor is not the correct term (#11029) (Monday, 14 October)
- [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Monday, 14 October)
- Re: [csswg-drafts] [css-anchor-position] The "acceptable anchor" algo seems broken (#11030) (Monday, 14 October)
- Re: [csswg-drafts] [css-color-4] Alias "grey()" to "gray()"? (#3298) (Monday, 14 October)
- Re: [csswg-drafts] [css-syntax] Missing emoji in `non-ascii` identifier codepoints (#11005) (Tuesday, 8 October)
- Re: [csswg-drafts] [css-values-5] Should progress functions have a calculation tree as their internal representation? (#10979) (Monday, 7 October)
- Closed: [csswg-drafts] [css-values-5] Special case equal progress/start/end values in progress functions? (#10980) (Monday, 7 October)
- Re: [csswg-drafts] [css-values-5] Do not make the type of `*-progress()` consistent with its input calculations? (#10840) (Monday, 7 October)
- Closed: [csswg-drafts] [css-values-5] Do not make the type of `*-progress()` consistent with its input calculations? (#10840) (Monday, 7 October)
- Re: [csswg-drafts] [css-values-5] Do not make the type of `*-progress()` consistent with its input calculations? (#10840) (Monday, 7 October)
- Re: [csswg-drafts] [css-values-5] Do not make the type of `*-progress()` consistent with its input calculations? (#10840) (Monday, 7 October)
- Closed: [csswg-drafts] [css-values-5] Do not make the type of `*-progress()` consistent with its input calculations? (#10840) (Monday, 7 October)
- Re: [csswg-drafts] Alternative masonry path forward (#9041) (Friday, 4 October)
- Re: [csswg-drafts] [css-anchor-position]: Question: Why is anchor-size() only valid in a sizing property? (#9827) (Friday, 4 October)
- Closed: [csswg-drafts] [css-sizing-4] Do not add `stretch | fit-content | contain` for the logical properties (#7370) (Friday, 4 October)
- Re: [csswg-drafts] [css-overflow-4] Draft spec for `continue: collapse` (#7708) (#10816) (Friday, 4 October)
- Closed: [csswg-drafts] [css-nesting] Writing error in example (#9283) (Friday, 4 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Friday, 4 October)
- Re: [csswg-drafts] [css-syntax] Missing emoji in `non-ascii` identifier codepoints (#11005) (Friday, 4 October)
- Re: [csswg-drafts] [css-syntax] Missing emoji in `non-ascii` identifier codepoints (#11005) (Friday, 4 October)
- [csswg-drafts] [css-anchor-position] Better handling of scroll position for fixpos elements on first layout (#10999) (Thursday, 3 October)
- Re: [csswg-drafts] [css-color-5] Allow using channel keywords in any calculation (#10983) (Thursday, 3 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Thursday, 3 October)
- Re: [csswg-drafts] [css-shadow-parts][css-nesting] is & allowed after ::part() (#10788) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-pseudo-4] ::self-link pseudo, for self-linking (#10498) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-pseudo-4] ::self-link pseudo, for self-linking (#10498) (Wednesday, 2 October)
- Re: [csswg-drafts] [mediaqueries] `streaming` media feature for implementing streamer mode (#10973) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-mixins] Improve ergonomics of `using` by allowing wildcards (#10954) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-color-5] Allow using channel keywords in any calculation (#10983) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-color-5] Is relative colors "omitted alpha" rule useful? (#10991) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2] corner-shape support for superellipsis (#10993) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2] Consider allowing `<position>` for the `from` and some other points (#10644) (Wednesday, 2 October)
- Re: [csswg-drafts] Alternative masonry path forward (#9041) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-values-5] Special case equal progress/start/end values in progress functions? (#10980) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-shapes-2] `curve to` keyword `using` seems a bit off (#10649) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-shapes-2] Consider allowing `<position>` for the `from` and some other points (#10644) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-shapes-2][css-borders-4] Add a way to change an element's shape (#6997) (Tuesday, 1 October)
Tatsunori Uchino via GitHub
Thad Guidry via GitHub
Tim Nguyen via GitHub
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Thursday, 31 October)
- Re: [csswg-drafts] [css-view-transitions-2] How are auto-generated `view-transition-name`s exposed in JS APIs (#10978) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Wednesday, 30 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Thursday, 24 October)
- Re: [csswg-drafts] [css-text-4] `text-spacing-trim` is harmful for Yu Gothic UI (system-ui in Japanese Windows) (#11074) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-values] Proposal: `descendant-count()` function (#11069) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transition] "capture the new state" and "capture the old state" are subtly different. (#11071) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transition] "capture the new state" and "capture the old state" are subtly different. (#11071) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transitions-2] Allow an auto-generated `view-transition-name` that doesn't default to ID (#10995) (Tuesday, 22 October)
- Re: [csswg-drafts] [scroll-animations-1][css-animations-2] Add animation-range to animation shorthand (#8054) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transitions-2] Using 'was created via cross-origin redirects' Document creation state causes unexpected results (#11063) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-view-transitions] Skip on activation doesn't provide a reason (#11059) (Monday, 21 October)
- Re: [csswg-drafts] [css-fonts] Should font-variant-emoji affect ZWJ emoji sequences? (#11036) (Monday, 21 October)
- Closed: [csswg-drafts] [css-view-transition] `::view-transition-old/new` element doesnt respect original parent with overflow: auto (#11049) (Monday, 21 October)
- Re: [csswg-drafts] [css-view-transition] `::view-transition-old/new` element doesnt respect original parent with overflow: auto (#11049) (Monday, 21 October)
- Closed: [csswg-drafts] [css-inline] Disallow `auto` in `text-box` shorthand (#10748) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-values-5][various] Better handling of arguments with commas (#9539) (Tuesday, 8 October)
- Re: [csswg-drafts] [selectors] :local-link should have a more precise name (#10975) (Friday, 4 October)
- Re: [csswg-drafts] [css-view-transitions-2] view-transition-name determined by element (#8320) (Wednesday, 2 October)
- Re: [csswg-drafts] [css-view-transitions-2] Should `::view-transition-group(auto)` match `view-transition-name: auto`? (#10978) (Tuesday, 1 October)
- Re: [csswg-drafts] [selectors] :local-link should have a more precise name (#10975) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Tuesday, 1 October)
- Re: [csswg-drafts] [css-ui] Colors to use for appearance:base `<select>` (#10909) (Tuesday, 1 October)
Toby Boekwijt via GitHub
tomasts248 via GitHub
Trevor Paley via GitHub
Ultinio via GitHub
Victorien Elvinger via GitHub
Vladimir Levantovsky via GitHub
vmpstr via GitHub
W3C Bot via GitHub
webdevelopers-eu via GitHub
Westbrook Johnson via GitHub
Wii via GitHub
woody-li via GitHub
Xiaocheng Hu via GitHub
Yair Even Or via GitHub
Yasuo Kida (木田泰夫) via GitHub
Yehonatan Daniv via GitHub
- Re: [csswg-drafts] [web-animations-2] Custom effects (#6861) (Thursday, 31 October)
- Re: [csswg-drafts] [web-animations-2] Progress APIs (#8799) (Wednesday, 30 October)
- Re: [csswg-drafts] [web-animations-2] Custom effects (#6861) (Thursday, 24 October)
- Re: [csswg-drafts] [web-animations-2] Custom effects (#6861) (Thursday, 24 October)
- Re: [csswg-drafts] [css-animations-2][web-animations-2] (proposal) Add pointer driven animations (#10574) (Wednesday, 23 October)
- Re: [csswg-drafts] [scroll-animations-1][css-animations-2] Add animation-range to animation shorthand (#8054) (Tuesday, 22 October)
- Re: [csswg-drafts] [scroll-animations-1] Typo in calculation of ViewTimeline progress (#10960) (Thursday, 17 October)
- Re: [csswg-drafts] [cssom-view] Expose small/large viewport dimensions of the layout viewport (#8709) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-animations-2] Specify the animation-trigger property (#10128) (Monday, 7 October)
- Re: [csswg-drafts] [scroll-animations-1] Range for entire scroll range (#9367) (Tuesday, 1 October)
Yusuf KaYeht via GitHub
Ziad El Khoury Hanna via GitHub
ziofat via GitHub
Óscar Otero via GitHub
Сергей via GitHub
一丝 via GitHub
- Re: [csswg-drafts] [css-flexbox][css-align] Support `justify-items` for flexbox containers (and `justify-self` for items) (#9495) (Tuesday, 29 October)
- Re: [csswg-drafts] [css-pseudo][css-shadow-parts] Define "part-like pseudo-element" concept (#10083) (Thursday, 24 October)
- Re: [csswg-drafts] [css-fonts] Clarification font-variant-emoji should not affect characters `0-9#*` (#11014) (Wednesday, 23 October)
- Re: [csswg-drafts] [css-values-5] [css-overflow-4]How does `line-clamp` transition from `<integer>` to `auto` or `none`? (#10502) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-values-5] [css-overflow-4]How does `line-clamp` transition from `<integer>` to `auto` or `none`? (#10502) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-values-5] [css-overflow-4]How does `line-clamp` transition from `<integer>` to `auto` or `none`? (#10502) (Tuesday, 22 October)
- Re: [csswg-drafts] [css-scrollbars] Scrollbar Hover/Interaction Colors (#10591) (Friday, 18 October)
- Re: [csswg-drafts] [css-fonts-4] font-display says it's valid in @font-feature-values but it isn't an at-rule (#2973) (Thursday, 17 October)
- Re: [csswg-drafts] [css-fonts-4] @font-feature-values { font-display } (#7412) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-fonts-4][css-font-loading] Applying default font-display to FontFace.load() (#3188) (Wednesday, 16 October)
- Re: [csswg-drafts] [css-fonts] Should font-variant-emoji affect ZWJ emoji sequences? (#11036) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] attr()'s "px"/etc keywords (#11034) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-values-5] [css-overflow-4]How does `line-clamp` transition from `<integer>` to `auto` or `none`? (#10502) (Tuesday, 15 October)
- Re: [csswg-drafts] [css-fonts] [palettes] Disallow usage of var() in `@font-palette-values` (#6931) (Thursday, 10 October)
- Re: [csswg-drafts] [css-fonts] Clarification font-variant-emoji should not affect characters `0-9#*` (#11014) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-fonts] Clarification font-variant-emoji should not affect characters `0-9#*` (#11014) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-fonts] Clarification font-variant-emoji should not affect characters `0-9#*` (#11014) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-fonts] Clarification font-variant-emoji should not affect characters `0-9#*` (#11014) (Wednesday, 9 October)
- [csswg-drafts] [css-fonts] Clarification font-variant-emoji should not affect characters `0-9#*` (#11014) (Wednesday, 9 October)
- Re: [csswg-drafts] [css-ui] Pseudo-elements for checkmark and dropdown icon for appearance:base `<select>` (#10908) (Wednesday, 9 October)
小黑子 via GitHub
Last message date: Thursday, 31 October 2024 23:53:41 UTC