www-style@w3.org from October 2013 by date

Thursday, 31 October 2013

• Re: [css-regions] Floats overflow in named flows Alan Stearns
• Re: [css-flexbox] "Determine the flex container’s used cross size" step needs to take min/max size into account Tab Atkins Jr.
• Re: [css-regions] Floats overflow in named flows Tab Atkins Jr.
• Re: Requesting an extension on reviewing CSS3 Text [I18N-ACTION-271] fantasai
• Requesting an extension on reviewing CSS3 Text [I18N-ACTION-271] Phillips, Addison
• Re: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Richard Ishida
• RE: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Matitiahu Allouche
• Re: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Aryeh Gregor
• [counter-styles] location of i18n doc Richard Ishida
• Re: [counter-styles] i18n-ISSUE-282: Problems with Ethiopic-numeric algorithm Richard Ishida

Wednesday, 30 October 2013

• Re: [css-shapes] how to position <basic-shape>s Sylvain Galineau

Thursday, 31 October 2013

• [CSSWG] Minutes Telecon 2013-10-30 Dael Jackson

Wednesday, 30 October 2013

• Re: [counter-styles] At-risk list Tab Atkins Jr.
• Re: [css-counter-styles] japanese-informal counter style Tab Atkins Jr.
• Re: [css3-flexbox] Should "align-self:stretch" have any effect on main-size? (i.e. should stretched cross-size be used for establishing main size?) Daniel Holbert
• Re: [css3-flexbox] Should "align-self:stretch" have any effect on main-size? (i.e. should stretched cross-size be used for establishing main size?) Daniel Holbert
• Re: [counter-styles] At-risk list Reece Dunn
• Re: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Tab Atkins Jr.
• Re: [counter-styles] i18n-ISSUE-281: Problems with example 12 Tab Atkins Jr.
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 Alan Stearns
• Re: [counter-styles] At-risk list Tab Atkins Jr.
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 fantasai
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 Chris Lilley
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 Chris Lilley
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 Chris Lilley
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 fantasai
• Re: [counter-styles] i18n-ISSUE-281: Problems with example 12 Richard Ishida
• Agenda conf call 30-oct-2013 Daniel Glazman
• Re: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Richard Ishida
• Re: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Aryeh Gregor

Monday, 28 October 2013

• [css3-mediaqueries] device-max-height ? Andreas Schneider

Wednesday, 30 October 2013

• RE: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Matitiahu Allouche
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 Dirk Schulze
• RE: [counter-styles] i18n-ISSUE-281: Problems with example 12 Phillips, Addison
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 Alan Stearns
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 fantasai
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 Alan Stearns
• Re: [CSS4-MediaQueries] media feature proposal: display-colors-inverted (previously from IndieUI User Context) James Craig
• Re: [counter-styles] i18n-ISSUE-281: Problems with example 12 Tab Atkins Jr.
• Re: [counter-styles] At-risk list Reece Dunn
• Re: [css-flexbox] "Determine the flex container’s used cross size" step needs to take min/max size into account Daniel Holbert
• Re: [counter-styles] i18n-ISSUE-282: Problems with Ethiopic-numeric algorithm Tab Atkins Jr.
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 fantasai
• Re: [css-shapes] how to position <basic-shape>s Alan Stearns
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 Alan Stearns
• Re: [CSSWG][css-writing-modes] Updated WD of CSS3 Writing Modes fantasai
• [CSSWG][css-writing-modes] Updated WD of CSS3 Writing Modes fantasai
• [counter-styles] At-risk list fantasai
• Re: [counter-styles] i18n-ISSUE-283: 113,023 Tab Atkins Jr.
• Re: [counter-styles] i18n-ISSUE-284: All negative capable Tab Atkins Jr.
• Re: [css-counter-styles] negative descriptor for Japanese and Korean Tab Atkins Jr.
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 fantasai
• Re: [css-shapes] how to position <basic-shape>s fantasai
• Re: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Tab Atkins Jr.
• Re: [css-flexbox] "Determine the flex container’s used cross size" step needs to take min/max size into account Tab Atkins Jr.

Tuesday, 29 October 2013

• [css-syntax] Soon to Last Call Simon Sapin
• Re: [css-flexbox] "Determine the flex container’s used cross size" step needs to take min/max size into account Daniel Holbert
• [css-flexbox] "Determine the flex container’s used cross size" step needs to take min/max size into account Daniel Holbert
• Re: [css-shapes] Positioning <basic-shapes> summary, v2 Dirk Schulze
• Re: [css-syntax] Multiple !values Sebastian Zartner
• [css-shapes] Positioning <basic-shapes> summary, v2 Alan Stearns
• [css-masking] CSS Masking Module Level 1 in Last Call - Please review Dirk Schulze
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Brian Kardell
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Alan Stearns
• [css-cascade] Environment encoding for @import Simon Sapin
• [cssom] Environment encoding for xml-stylesheet PIs Simon Sapin
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) L. David Baron
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Tab Atkins Jr.
• Re: [css-syntax] Multiple !values fantasai
• Re: Displaying an ellipsis on the last visible line of a block that overflows vertically Tab Atkins Jr.
• Re: [css-syntax] Multiple !values Tab Atkins Jr.
• Re: [css-syntax] Cross-origin fallback charset Simon Sapin
• Re: [css-syntax] Multiple !values Sebastian Zartner
• Re: [css-syntax] Multiple !values Simon Pieters
• Re: [css-syntax] Multiple !values Simon Sapin
• Re: [css-syntax] Multiple !values Sebastian Zartner
• [css-regions] Floats overflow in named flows Radu STAVILA
• [css-syntax] Cross-origin fallback charset Simon Sapin
• [css-syntax] Multiple !values Simon Sapin
• Re: Displaying an ellipsis on the last visible line of a block that overflows vertically Bruno Racineux
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Alan Stearns
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Brian Kardell
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) L. David Baron
• [CSS4-MediaQueries] media feature proposal: display-colors-inverted (previously from IndieUI User Context) James Craig
• Re: Displaying an ellipsis on the last visible line of a block that overflows vertically Tab Atkins Jr.
• Re: Displaying an ellipsis on the last visible line of a block that overflows vertically Robert O'Callahan
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Alan Stearns
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Tab Atkins Jr.
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) L. David Baron
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Sylvain Galineau
• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Tab Atkins Jr.

Monday, 28 October 2013

• Re: Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) L. David Baron
• Re: TestTWF Pull requests needing review Rebecca Hauck
• Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation) Brian Kardell
• RE: TestTWF Pull requests needing review Paul Tykodi
• Re: [css-regions] Named Flows, Elements and Box Generation François REMY
• TestTWF Pull requests needing review Rebecca Hauck
• Re: [css-regions] Named Flows, Elements and Box Generation Sylvain Galineau
• Re: [css-regions] Named Flows, Elements and Box Generation Tab Atkins Jr.
• Re: [css-regions] Named Flows, Elements and Box Generation Tab Atkins Jr.
• Re: [css-regions] Named Flows, Elements and Box Generation Håkon Wium Lie
• Re: [css-regions] Named Flows, Elements and Box Generation Håkon Wium Lie
• Re: [css-books] Re: [css3-gcpm] Complex Footnotes Håkon Wium Lie
• Re: [css-regions] Named Flows, Elements and Box Generation Tab Atkins Jr.
• Re: [css-regions] Named Flows, Elements and Box Generation Håkon Wium Lie
• [css-regions] Tweetdeck-style app and flow-into Alan Stearns
• Re: [css-values] text() Tab Atkins Jr.
• Re: [css-books] Re: [css3-gcpm] Complex Footnotes Liam R E Quin
• Re: [css-values] text() Simon Sapin
• Re: [css-values] text() Tab Atkins Jr.
• Re: Displaying an ellipsis on the last visible line of a block that overflows vertically Tab Atkins Jr.
• Re: [css-regions] Named Flows, Elements and Box Generation Tab Atkins Jr.
• Re: [css-books] Re: [css3-gcpm] Complex Footnotes Tab Atkins Jr.
• Re: [css-regions] Named Flows, Elements and Box Generation Sylvain Galineau
• Re: [css-regions] Add " Reordering and Accessibility" section just like Flexbox Takeshi Kurosawa
• Re: [css-cascade] CSS Cascade Level 3 Candidate Recommendation Ian Jacobs
• Re: [css-cascade] CSS Cascade Level 3 Candidate Recommendation Alan Stearns
• Re: [css-cascade] CSS Cascade Level 3 Candidate Recommendation Bjoern Hoehrmann

Sunday, 27 October 2013

• RE: [css-regions] Named Flows, Elements and Box Generation François REMY
• Re: [css-values] text() Jon Rimmer
• Re: Displaying an ellipsis on the last visible line of a block that overflows vertically Marat Tanalin
• Re: [css-books] Re: [css3-gcpm] Complex Footnotes James Clark
• Re: [css-books] Re: [css3-gcpm] Complex Footnotes Håkon Wium Lie
• Re: [css-regions] Add " Reordering and Accessibility" section just like Flexbox Alan Stearns
• [css-regions] Add " Reordering and Accessibility" section just like Flexbox Takeshi Kurosawa
• Re: [css-regions] Named Flows, Elements and Box Generation Alan Stearns
• Re: [css-regions] Named Flows, Elements and Box Generation Johannes Wilm
• Re: [css-books] Re: [css3-gcpm] Complex Footnotes Liam R E Quin
• Re: Displaying an ellipsis on the last visible line of a block that overflows vertically Antony Kennedy
• [css-fonts] Stylistic alternates James Clark
• Re: [css-books] Re: [css3-gcpm] Complex Footnotes James Clark
• Displaying an ellipsis on the last visible line of a block that overflows vertically Robert O'Callahan

Saturday, 26 October 2013

• Re: [css-regions] Named Flows, Elements and Box Generation Håkon Wium Lie
• Re: [css3-books] Re: [css3-gcpm] Leaders layout corner cases Håkon Wium Lie

Friday, 25 October 2013

• Re: [css-regions] Named Flows, Elements and Box Generation Johannes Wilm

Saturday, 26 October 2013

• Fwd: [css-regions] Named Flows, Elements and Box Generation Johannes Wilm
• Re: [css3-books] Re: [css3-gcpm] Leaders layout corner cases Brad Kemper
• Re: [css-values] text() Håkon Wium Lie
• [css-values] text() Jon Rimmer
• [css-books] Re: [css3-gcpm] Complex Footnotes Håkon Wium Lie
• Re: [css3-books] Re: [css3-gcpm] Leaders layout corner cases Håkon Wium Lie

Friday, 25 October 2013

• [css-page][css3-gcpm] Early Draft of Pagination Document from Digital Publishing Interest Group Cramer, Dave
• Re: [CSS21] Margin collapsing with negative margins Gérard Talbot
• RE: CSS support for TrueType collection files Levantovsky, Vladimir
• Re: CSS support for TrueType collection files John Daggett
• Re: [CSS21] Margin collapsing with negative margins Sylvain Galineau
• [CSS21] Margin collapsing with negative margins Gérard Talbot

Thursday, 24 October 2013

• Telecon Minutes 2013-10-23 Dael Jackson
• RE: CSS support for TrueType collection files Levantovsky, Vladimir
• Re: [css-fonts] CSS support for TrueType collection files John Daggett
• Re: [css-fonts] CSS support for TrueType collection files Behdad Esfahbod
• [css-fonts] CSS support for TrueType collection files John Daggett
• [css3-writing-modes] Yet another approach to discuss Tr fallback issue for UTR#50 and text-orientation Koji Ishii
• Re: [css-text-4] Option for 'true' alignment with text-align Brad Kemper

Wednesday, 23 October 2013

• Re: [css-regions] Named Flows, Elements and Box Generation Sylvain Galineau
• Re: [css-regions] Named Flows, Elements and Box Generation Alan Stearns
• Re: [css-regions] Named Flows, Elements and Box Generation Håkon Wium Lie
• Re: [css-regions] Named Flows, Elements and Box Generation Alan Stearns
• Re: [css-regions] Named Flows, Elements and Box Generation L. David Baron
• Re: [css-ui] outline-stye: auto Scott Rowe
• [css-snappoints] Unofficial draft of Scroll Snap Points Rossen Atanassov
• Re: [css-text-4] Option for 'true' alignment with text-align Robert O'Callahan
• Re: [css-text-4] Option for 'true' alignment with text-align Tab Atkins Jr.
• Re: [css-ui] outline-stye: auto L. David Baron
• [css-text-4] Option for 'true' alignment with text-align L. David Baron
• Re: [css3-books] Re: [css3-gcpm] Leaders layout corner cases Brad Kemper
• Re: [css-grid] Intrinsic / preferred logical widths on the grid element Tab Atkins Jr.
• Re: [css-book] Re: [css-page] Meaning of :first page selector (was: [css3-gcpm] Page groups, named pages, and :first) Tab Atkins Jr.
• Re: [css-book] Re: [css-page] Meaning of :first page selector (was: [css3-gcpm] Page groups, named pages, and :first) Tab Atkins Jr.
• Re: [css-book] Re: [css-page] Meaning of :first page selector (was: [css3-gcpm] Page groups, named pages, and :first) Cramer, Dave
• Re: [css-regions][css-overflow] named flows and overflow:fragments use case 1 Alan Stearns
• Re: [css-shapes] how to position <basic-shape>s Alan Stearns
• Re: [css-animations] Starting animations with animation-play-state: paused Sylvain Galineau
• Agenda conf call 23-oct-2013 Peter Linss

Tuesday, 22 October 2013

• Re: [css-grid] Intrinsic / preferred logical widths on the grid element Julien Chaffraix
• Re: [css-animations] Starting animations with animation-play-state: paused Shane Stephens
• Re: [css-animations] Starting animations with animation-play-state: paused Sylvain Galineau
• RE: [css-regions][css-overflow] named flows and overflow:fragments use case 1 François REMY
• Re: [css-book] Re: [css-page] Meaning of :first page selector (was: [css3-gcpm] Page groups, named pages, and :first) Håkon Wium Lie
• Re: [css-animations] Starting animations with animation-play-state: paused Shane Stephens
• RE: objection re: RESOLVED: setProperty's handling of importance logically behaves same as appending a declaraiton (like IE/WebKit) François REMY
• Re: [css-snappoints] Early comments on Snap Points Robert O'Callahan
• Re: [css-shapes] how to position <basic-shape>s Sylvain Galineau
• Re: [css-animations] Starting animations with animation-play-state: paused Sylvain Galineau
• Re: [css-snappoints] Early comments on Snap Points Tab Atkins Jr.
• [css-snappoints] Early comments on Snap Points Tab Atkins Jr.
• Re: [css-book] Re: [css-page] Meaning of :first page selector (was: [css3-gcpm] Page groups, named pages, and :first) Tab Atkins Jr.
• Re: [css-book] Re: [css-page] Meaning of :first page selector (was: [css3-gcpm] Page groups, named pages, and :first) Håkon Wium Lie
• Re: [css-book] Re: [css-page] Meaning of :first page selector (was: [css3-gcpm] Page groups, named pages, and :first) Tab Atkins Jr.
• Re: [css3-break] fragmentation and full screen elements Brad Kemper
• [css-book] Re: [css-page] Meaning of :first page selector (was: [css3-gcpm] Page groups, named pages, and :first) Håkon Wium Lie
• [css3-books] Re: [css3-gcpm] Leaders layout corner cases Håkon Wium Lie
• [css-books] Re: [css3-gcpm] Does string-set work on elements or on boxes? Håkon Wium Lie
• [css-font-load-events] Minor comments Kunihiko Sakamoto
• Re: [css-shapes] how to position <basic-shape>s fantasai
• Re: [css-animations] Starting animations with animation-play-state: paused Steve Block
• Re: line-height: normal and multiple descendant font sizes Alan Gresley
• Re: line-height: normal and multiple descendant font sizes Alan Gresley
• [css-regions] Named Flows, Elements and Box Generation Alan Stearns

Monday, 21 October 2013

• Re: [css-page-3] 'marks' and 'bleed' Cramer, Dave
• Re: [css-page-3] 'marks' and 'bleed' Håkon Wium Lie
• Re: [css-page-3] 'marks' and 'bleed' Florian Rivoal
• Re: line-height: normal and multiple descendant font sizes Gérard Talbot
• Re: [css-page-3] 'marks' and 'bleed' Håkon Wium Lie
• Re: [css-page-3] 'marks' and 'bleed' Cramer, Dave
• [css-page-3] 'marks' and 'bleed' Håkon Wium Lie
• [css3-break] fragmentation and full screen elements Mihai Balan
• Re: .clearfix Tab Atkins Jr.
• Re: .clearfix Bruno Racineux
• Re: line-height: normal and multiple descendant font sizes Alan Gresley
• Re: A dedicated property to clear descendant floats (was: Proposal for "overflow:clip" for stronger painting isolation) Tab Atkins Jr.
• Re: A dedicated property to clear descendant floats (was: Proposal for "overflow:clip" for stronger painting isolation) Bruno Racineux

Sunday, 20 October 2013

• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• RE: leaving Tr fallback undefined Koji Ishii
• Re: Proposal for "overflow:clip" for stronger painting isolation Tab Atkins Jr.
• Re: A dedicated property to clear descendant floats (was: Proposal for "overflow:clip" for stronger painting isolation) Tab Atkins Jr.
• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• Re: line-height: normal and multiple descendant font sizes Glenn Adams

Saturday, 19 October 2013

• Re: line-height: normal and multiple descendant font sizes Gérard Talbot
• Re: line-height: normal and multiple descendant font sizes Gérard Talbot
• Re: line-height: normal and multiple descendant font sizes Alan Gresley
• Re: [css-shapes] how to position <basic-shape>s Alan Stearns
• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• Re: A dedicated property to clear descendant floats (was: Proposal for "overflow:clip" for stronger painting isolation) Marat Tanalin
• Re: line-height: normal and multiple descendant font sizes L. David Baron
• Re: line-height: normal and multiple descendant font sizes Alan Gresley
• Re: line-height: normal and multiple descendant font sizes Gérard Talbot
• Re: line-height: normal and multiple descendant font sizes Alan Gresley
• Re: A dedicated property to clear descendant floats (was: Proposal for "overflow:clip" for stronger painting isolation) Bruno Racineux
• Re: A dedicated property to clear descendant floats (was: Proposal for "overflow:clip" for stronger painting isolation) Marat Tanalin
• Re: Proposal for "overflow:clip" for stronger painting isolation Bruno Racineux
• Re: A dedicated property to clear descendant floats (was: Proposal for "overflow:clip" for stronger painting isolation) Bruno Racineux
• Re: line-height: normal and multiple descendant font sizes Glenn Adams

Friday, 18 October 2013

• Re: line-height: normal and multiple descendant font sizes Gérard Talbot
• Re: [css-shapes] how to position <basic-shape>s fantasai
• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• Re: Proposal for "overflow:clip" for stronger painting isolation Bruno Racineux
• Re: line-height: normal and multiple descendant font sizes Gérard Talbot
• Re: line-height: normal and multiple descendant font sizes Gérard Talbot
• Re: line-height: normal and multiple descendant font sizes Gérard Talbot
• A dedicated property to clear descendant floats (was: Proposal for "overflow:clip" for stronger painting isolation) Marat Tanalin
• Re: [css-shapes] how to size and position <image>s Alan Stearns
• Re: .clearfix Brian Kardell
• Re: [css-shapes] inset() vs. inset-rectange() Alan Stearns
• Re: [css-shapes] inset() vs. inset-rectange() Lea Verou
• Re: Proposal for "overflow:clip" for stronger painting isolation Simon Fraser
• Re: Behavior of device-pixel-ratio under zoom James Robinson
• Re: .clearfix Tab Atkins Jr.
• Re: .clearfix Kang-Hao (Kenny) Lu
• Re: [css-shapes] how to size and position <image>s fantasai
• Re: .clearfix Kang-Hao (Kenny) Lu
• Re: [css-shapes] how to size and position <image>s fantasai
• Re: .clearfix (was: Proposal for "overflow:clip" for stronger painting isolation) Tab Atkins Jr.
• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• .clearfix (was: Proposal for "overflow:clip" for stronger painting isolation) Kang-Hao (Kenny) Lu
• Re: line-height: normal and multiple descendant font sizes John Hudson
• Re: Proposal for "overflow:clip" for stronger painting isolation Tab Atkins Jr.
• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• Re: line-height: normal and multiple descendant font sizes Alan Gresley
• Re: Proposal for "overflow:clip" for stronger painting isolation Alan Gresley
• Re: Proposal for "overflow:clip" for stronger painting isolation Bruno Racineux
• Re: Behavior of device-pixel-ratio under zoom Simon Pieters
• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• Re: [css-shapes] how to position <basic-shape>s Tab Atkins Jr.
• Re: [css-shapes] how to size and position <image>s Alan Stearns
• Re: [css-shapes] how to size and position <image>s fantasai

Wednesday, 16 October 2013

• Re: [css-shapes] how to position <basic-shape>s fantasai

Friday, 18 October 2013

• Re: line-height: normal and multiple descendant font sizes Alan Gresley

Thursday, 17 October 2013

• Re: Proposal for "overflow:clip" for stronger painting isolation Kang-Hao (Kenny) Lu
• Re: Behavior of device-pixel-ratio under zoom James Robinson
• Re: Proposal for "overflow:clip" for stronger painting isolation Tab Atkins Jr.
• Re: Behavior of device-pixel-ratio under zoom Simon Pieters
• Re: Proposal for "overflow:clip" for stronger painting isolation Bruno Racineux
• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• [css-ui] outline-stye: auto Scott Rowe
• Re: line-height: normal and multiple descendant font sizes Glenn Adams
• Re: line-height: normal and multiple descendant font sizes Gérard Talbot
• Re: [css-shapes] how to size and position <image>s Alan Stearns
• Re: [css-shapes] how to size and position <image>s Tab Atkins Jr.
• Re: [css-shapes] how to size and position <image>s Alan Stearns
• Re: Behavior of device-pixel-ratio under zoom James Robinson
• line-height: normal and multiple descendant font sizes Glenn Adams
• Re: Behavior of device-pixel-ratio under zoom Simon Pieters
• Re: [css-animations] Starting animations with animation-play-state: paused Sylvain Galineau
• Re: [css-shapes] how to size and position <image>s Dirk Schulze
• Re: [css3-writing-modes] leaving Tr fallback undefined fantasai
• Re: [css-shapes] how to size and position <image>s fantasai
• Re: [css-shapes] how to size and position <image>s fantasai
• Re: [css-shapes] how to size and position <image>s Dirk Schulze
• [css-animations] Starting animations with animation-play-state: paused Shane Stephens
• [css3-writing-modes] leaving Tr fallback undefined John Daggett
• Re: [css-shapes] inset() vs. inset-rectange() Alan Stearns
• Re: [CSSWG] Minutes Telecon 2013-10-16 Alan Stearns
• Re: [css-shapes] inset() vs. inset-rectange() Tab Atkins Jr.
• [CSSWG] Minutes Telecon 2013-10-16 Dael Jackson

Wednesday, 16 October 2013

• Re: Implementers information Kang-Hao (Kenny) Lu
• Re: [css-shapes] how to position <basic-shape>s Alan Stearns
• Re: [css-shapes] inset() vs. inset-rectange() Alan Stearns
• [css-shapes] inset() vs. inset-rectange() fantasai
• Re: [css-shapes] how to position <basic-shape>s fantasai
• Re: [css-shapes] how to size and position <image>s Alan Stearns
• Re: [css-shapes] how to position <basic-shape>s Alan Stearns
• Re: [css-shapes] how to position <basic-shape>s fantasai
• Re: [css-writing-modes] feedback: bottom-to-top scripts? fantasai
• Re: [css-shapes] how to size and position <image>s fantasai
• Re: [css-shapes] how to size and position <image>s Alan Stearns
• Re: [css-shapes] how to size and position <image>s fantasai
• Re: Implementers information Dirk Pranke
• Re: Implementers information Brian Kardell
• Re: Implementers information Tab Atkins Jr.
• Implementers information Brian Kardell
• Re: Insulating part of a HTML document from global CSS Garrett Smith
• Re: Insulating part of a HTML document from global CSS Tab Atkins Jr.
• Re: Agenda conf call 16-oct-2013 Chris Lilley
• Re: Insulating part of a HTML document from global CSS Garrett Smith
• Re: Insulating part of a HTML document from global CSS Robert O'Callahan
• Insulating part of a HTML document from global CSS Tom Wardrop
• Re: Agenda conf call 16-oct-2013 John Daggett
• Agenda conf call 16-oct-2013 Peter Linss

Tuesday, 15 October 2013

• RE: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Matitiahu Allouche
• Re: [css-regions] Reworking getNamedFlows() Alan Stearns
• Re: [css-multicol] column-width bound (>0) is illegal Gérard Talbot
• Re: [css-multicol] column-width bound (>0) is illegal Tab Atkins Jr.
• Re: [css-multicol] column-width bound (>0) is illegal Tab Atkins Jr.
• Re: [css-multicol] column-width bound (>0) is illegal Gérard Talbot
• Re: [css-multicol] column-width bound (>0) is illegal Gérard Talbot
• Re: [css-multicol] column-width bound (>0) is illegal Gérard Talbot
• Re: [css-multicol] column-width bound (>0) is illegal Kang-Hao (Kenny) Lu
• Re: [css-regions] Reworking getNamedFlows() Tab Atkins Jr.
• Re: [css-shapes] how to position <basic-shape>s Alan Stearns
• Re: [css-regions] Reworking getNamedFlows() Alan Stearns
• Re: [css-multicol] can overflow content influence column height? Tab Atkins Jr.
• Re: [css-multicol] column-width bound (>0) is illegal Tab Atkins Jr.
• Re: [css-regions] Reworking getNamedFlows() Tab Atkins Jr.
• Re: [css-multicol] column-width bound (>0) is illegal Morten Stenshorne
• Re: [css-multicol] column-width bound (>0) is illegal Tab Atkins Jr.
• Re: [counter-styles] i18n-ISSUE-285: Hebrew number converter inadequate for numbers >= 1000 Richard Ishida
• Re: [css-multicol] column-width bound (>0) is illegal Alan Stearns
• [css-multicol] column-width bound (>0) is illegal Tab Atkins Jr.
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions John Daggett
• RE: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions Koji Ishii
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions 董福興 Bobby Tung
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions MURATA Makoto
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions John Daggett
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions John Daggett
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions Asmus Freytag
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions Koji Ishii
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions John Daggett
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions MURATA Makoto
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions John Daggett
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions John Daggett
• Re: [css-writing-modes] feedback: bottom-to-top scripts? fantasai

Monday, 14 October 2013

• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions MURATA Makoto
• Re: [css-regions] Reworking getNamedFlows() Alan Stearns
• RE: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions Koji Ishii
• Re: [css-compositing] why general blending is confusing Rik Cabanier
• RE: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions Koji Ishii
• Re: [css-multicol] can overflow content influence column height? Alan Stearns
• [css-multicol] can overflow content influence column height? Håkon Wium Lie
• [css-compositing] Compositing and Blending Last Call Working Draft Rik Cabanier
• Re: [css-grid] Computed value for grid-template-{rows|columns} Tab Atkins Jr.
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Dirk Schulze
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Mark S. Miller
• Re: [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Alan Gresley
• Re: [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Kang-Hao (Kenny) Lu
• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions fantasai
• Re: [css-writing-modes] feedback: bottom-to-top scripts? fantasai
• Re: [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Alan Gresley
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Dirk Schulze
• [css-books][css-figures] New WHATWG specifications Håkon Wium Lie
• Re: [css-regions][css-overflow] enhancing overflow:fragments use case 2 Alan Stearns

Sunday, 13 October 2013

• [cssom] moving forward on .usedStyle Mike Sherov
• Re: [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Kang-Hao (Kenny) Lu
• Re: Please reinstate the :selection spec Tab Atkins Jr.
• Re: [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Tab Atkins Jr.
• Re: [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Kang-Hao (Kenny) Lu

Friday, 11 October 2013

• Please reinstate the :selection spec Michael Sheaver

Sunday, 13 October 2013

• Re: [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Tab Atkins Jr.
• Re: [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Kang-Hao (Kenny) Lu
• Re: [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Alan Gresley
• [css-overflow-clipping] would 'overflow: clip' affect the layout of surrounding elements? Kang-Hao (Kenny) Lu
• Re: [css-compositing] why general blending is confusing Dean Jackson

Saturday, 12 October 2013

• Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions Glenn Adams
• Re: [css-compositing] why general blending is confusing Robert O'Callahan
• Re: [css-compositing] why general blending is confusing Dean Jackson
• Re: [css-compositing] why general blending is confusing Dean Jackson
• Re: [css-compositing] why general blending is confusing Robert O'Callahan
• Re: [css-compositing] why general blending is confusing Dirk Schulze
• [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions Koji Ishii
• Re: [css3-regions][css3-breaks] Forced region breaks inside a container with break-inside: avoid fantasai
• [css-compositing] why general blending is confusing Dean Jackson

Friday, 11 October 2013

• Re: [css3-regions][css3-breaks] Forced region breaks inside a container with break-inside: avoid Mihai Balan
• Re: [css-device-adapt] Avoid referring to Desktop Kenneth Rohde Christiansen
• Re: [css-device-adapt] Avoid referring to Desktop Rune Lillesveen
• Re: [css-device-adapt] Avoid referring to Desktop Rune Lillesveen
• Re: [filter-effects] filter different components of an element Alan Gresley
• Re: [filter-effects] filter different components of an element François REMY
• Re: [filter-effects] filter different components of an element Kang-Hao (Kenny) Lu
• Re: [filter-effects] filter different components of an element Dirk Schulze
• Re: [filter-effects] filter different components of an element Kang-Hao (Kenny) Lu
• Re: [filter-effects] filter different components of an element Kang-Hao (Kenny) Lu
• Re: [css-grid] Computed value for grid-template-{rows|columns} François REMY
• Re: [css-grid] Computed value for grid-template-{rows|columns} Sergio Villar Senin
• Re: [css-grid] Computed value for grid-template-{rows|columns} François REMY
• [css-grid] Computed value for grid-template-{rows|columns} Sergio Villar Senin

Thursday, 10 October 2013

• [CSSWG] Minutes Telcon 2013-10-09 Dael Jackson
• [CSSWG][css-text-3] CSS3 Text Last Call Working Draft fantasai
• Re: [css-grid] Bug in Example 24, line-based placement Tab Atkins Jr.
• [css-fonts] Chinese font Kai count as cursive 董福興 Bobby Tung
• Re: h Cramer, Dave
• Re: h Liam R E Quin
• Re: [whatwg] Proposal: Adding methods like getElementById and getElementsByTagName to DocumentFragments Simon Pieters
• Re: [css-break] another fragmentation question Håkon Wium Lie
• RE: [css3-break] ED 20130211 - minor editorial comments Tony Graham
• h fantasai
• Re: [css-regions][css3-break] Handling content overflow out of its region range Andrei Bucur
• Re: [css3-regions][css3-breaks] Forced region breaks inside a container with break-inside: avoid fantasai
• RE: [css-overflow] pathological fragment box generation Rossen Atanassov
• RE: [css3-break] ED 20130211 - minor editorial comments Rossen Atanassov
• RE: [css3-break] Summary of recent comments Rossen Atanassov

Wednesday, 9 October 2013

• Re: Agenda conf call 09-oct-2013 Lea Verou
• Re: [css-shapes] how to position <basic-shape>s Tab Atkins Jr.
• Re: [css-shapes] how to position <basic-shape>s Lev Solntsev
• Re: [css-shapes] how to position <basic-shape>s Tab Atkins Jr.
• Re: [css-shapes] how to position <basic-shape>s Lev Solntsev
• Re: [css-masking] Shorthanding the clip properties Dirk Schulze
• Re: [mediaqueries4] zoom-ratio as a media feature Tab Atkins Jr.
• Re: [css-shapes] how to position <basic-shape>s Tab Atkins Jr.
• Re: proposal: css compression via aliasing Tab Atkins Jr.
• [css-shapes] how to position <basic-shape>s Alan Stearns
• Re: Order of CLIP property coordinates Tab Atkins Jr.
• Re: [css-masking] Shorthanding the clip properties Tab Atkins Jr.
• Re: [css-writing-modes] feedback: bottom-to-top scripts? Tab Atkins Jr.
• Re: [css3-meadiaqueries] Proposal for "content-width" and "content-height" media features Tab Atkins Jr.
• Re: [css-flexbox] Fixing a mistake with flex-grow betwen 0 and 1 Tab Atkins Jr.
• Re: [css-values] Deprecating the 3-value <position> form Sylvain Galineau
• [css-cascade] CSS Cascade Level 3 Candidate Recommendation fantasai
• Re: [mediaqueries4] zoom-ratio as a media feature Tab Atkins Jr.
• Re: [css3-writing-modes] Summary of Tr in UTR#50 and 'text-orientation' discussions John Daggett
• Re: [selectors4] Comma-separated attribute value selectors Dario De Bastiani
• RE: [css3-writing-modes] Summary of Tr in UTR#50 and 'text-orientation' discussions Rossen Atanassov
• Re: [selectors4] Comma-separated attribute value selectors Brian Kardell
• Re: [mediaqueries4] zoom-ratio as a media feature Rick Byers
• Re: [css-flexbox] Fixing a mistake with flex-grow betwen 0 and 1 Daniel Holbert
• Re: [css-flexbox] Fixing a mistake with flex-grow betwen 0 and 1 Daniel Holbert
• Re: [css-masking] Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Dirk Schulze
• Re: [css-masking] Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Simon Sapin
• Re: [mediaqueries4] zoom-ratio as a media feature Simon Sapin
• Re: [css3-meadiaqueries] Proposal for "content-width" and "content-height" media features Kenneth Rohde Christiansen
• Re: Sticky Positioning Simon Sapin
• Re: proposal: css compression via aliasing Henrik Andersson
• Re: proposal: css compression via aliasing François REMY

Wednesday, 21 August 2013

• Re: [selectors4] Comma-separated attribute value selectors Célian Veyssière

Wednesday, 28 August 2013

• Re: :stuck psuedo class WAS: specifying position:sticky Cameron McCormack

Tuesday, 3 September 2013

• [css-writing-modes] feedback: bottom-to-top scripts? Martin Holmes

Friday, 6 September 2013

• [css3-values] feedback Dennis German

Monday, 9 September 2013

• [css3-meadiaqueries] Proposal for "content-width" and "content-height" media features Robert Koritnik

Tuesday, 10 September 2013

• proposal: css compression via aliasing Joey Bradshaw

Wednesday, 9 October 2013

• Fwd: [css-writing-modes-2] text-combine-horizontal a.k.a. Tate-chu-yoko Bert Bos

Thursday, 26 September 2013

• Order of CLIP property coordinates Kristjan Kure

Friday, 27 September 2013

• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Ken Lunde

Monday, 30 September 2013

• [css-fonts-3] font-variant-numeric Ian Storm Taylor

Monday, 7 October 2013

• [css3-values] feedback Wallace Hermano

Wednesday, 9 October 2013

• Re: Sticky Positioning Dennis Cheung
• [mediaqueries4] zoom-ratio as a media feature Alex Bell
• Fwd: Re: [css3-gcpm] Complex Footnotes Bert Bos
• Re: [cssom-view] behavior of document.body.scrollTop Simon Pieters
• Re: [cssom-view] behavior of document.body.scrollTop Mike Sherov
• Re: [css-masking] Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Dirk Schulze
• Re: [css-masking] Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Dirk Schulze
• Re: [cssom-view] behavior of document.body.scrollTop Simon Pieters
• Re: [css-masking] Shorthanding the clip properties Dirk Schulze
• Re: [css-values] Deprecating the 3-value <position> form fantasai
• Re: [css-values] Deprecating the 3-value <position> form Dirk Schulze
• [css-masking] Shorthanding the clip properties fantasai
• [css-masking] Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) fantasai
• Re: [css-values] Deprecating the 3-value <position> form fantasai
• Re: [css-shapes] Functional Notation fantasai
• Re: [css-flexbox] Fixing a mistake with flex-grow betwen 0 and 1 Daniel Holbert
• Re: [css-flexbox] Fixing a mistake with flex-grow betwen 0 and 1 Daniel Holbert
• Re: [css-shapes] Functional Notation Brad Kemper
• Re: [css-values] Deprecating the 3-value <position> form Dirk Schulze
• [cssom-view] behavior of document.body.scrollTop Mike Sherov
• Agenda conf call 09-oct-2013 Peter Linss
• [css-values] Deprecating the 3-value <position> form Tab Atkins Jr.
• Re: [css-regions] Editorial comment on content chain order Alan Stearns
• Re: [css-regions] Editorial comment on pseudo-elements processing model Alan Stearns

Tuesday, 8 October 2013

• Re: [css3-writing-modes] Summary of Tr in UTR#50 and 'text-orientation' discussions John Daggett
• [css-regions][css-overflow] escaping the sibling trap - use case 3 Alan Stearns
• Re: [css-shapes] Minor Comments Alan Stearns
• [css-shapes] shape-margin should allow percentages Alan Stearns
• Re: [css-shapes] Functional Notation Alan Stearns
• RE: [css3-writing-modes] Summary of Tr in UTR#50 and 'text-orientation' discussions Rossen Atanassov
• Re: [css-shapes] Functional Notation Tab Atkins Jr.
• Re: [css-flexbox] Fixing a mistake with flex-grow betwen 0 and 1 Tab Atkins Jr.
• Re: [css3-gcpm] Complex Footnotes Cramer, Dave
• Re: [css3-gcpm] Complex Footnotes Liam R E Quin
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-flexbox] Fixing a mistake with flex-grow betwen 0 and 1 François REMY
• Re: [css3-multicol] margin collapsing between column-spanning element and blocks in column boxes: if, when? Morten Stenshorne
• Re: [css3-multicol] margin collapsing between column-spanning element and blocks in column boxes: if, when? Håkon Wium Lie
• Re: [css-shapes] Functional Notation Dirk Schulze
• Re: [css3-multicol] margin collapsing between column-spanning element and blocks in column boxes: if, when? Morten Stenshorne
• Re: [css3-animations] can inserting a @keyframes rule start an animation? L. David Baron
• [css-regions][css-overflow] enhancing overflow:fragments use case 2 Alan Stearns

Monday, 7 October 2013

• Re: [css3-animations] can inserting a @keyframes rule start an animation? Tab Atkins Jr.
• [css3-animations] can inserting a @keyframes rule start an animation? Ralph Thomas
• Re: [css3-multicol] margin collapsing between column-spanning element and blocks in column boxes: if, when? Håkon Wium Lie
• [css-flexbox] Fixing a mistake with flex-grow betwen 0 and 1 Tab Atkins Jr.
• Re: [css-shapes] Functional Notation Brad Kemper
• Re: [css-shapes] Functional Notation fantasai
• Re: [css-shapes] Functional Notation fantasai
• Re: [css3-multicol] z-order of column-rule: below or above border? Brad Kemper
• Re: [css3-multicol] z-order of column-rule: below or above border? Morten Stenshorne
• Re: [css3-multicol] margin collapsing between column-spanning element and blocks in column boxes: if, when? Morten Stenshorne
• [css-regions][css-overflow] named flows and overflow:fragments use case 1 Alan Stearns

Sunday, 6 October 2013

• Re: [css3-gcpm] Complex Footnotes Liam R E Quin
• Re: [css3-gcpm] Complex Footnotes Tony Graham
• Re: [css3-multicol] margin collapsing between column-spanning element and blocks in column boxes: if, when? Håkon Wium Lie
• Re: [css3-multicol] z-order of column-rule: below or above border? Håkon Wium Lie
• Re: [css3-gcpm] Complex Footnotes Håkon Wium Lie
• Re: [css3-gcpm] Complex Footnotes Håkon Wium Lie
• RE: [css3-writing-modes] Summary of Tr in UTR#50 and 'text-orientation' discussions Koji Ishii
• Re: [css-shapes] Functional Notation Dirk Schulze
• Re: [css3-writing-modes] Summary of Tr in UTR#50 and 'text-orientation' discussions John Daggett

Saturday, 5 October 2013

• [css-overflow] Is the last fragment in a 'fragment box'? Alan Stearns
• Re: [css-shapes] Functional Notation Brad Kemper

Friday, 4 October 2013

• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-device-adapt] Apply @viewport to top-level documents only François REMY
• Re: [css-device-adapt] Apply @viewport to top-level documents only Alexandre Elias
• RE: [css3-writing-modes] Summary of Tr in UTR#50 and 'text-orientation' discussions Rossen Atanassov
• Re: [css-device-adapt] Apply @viewport to top-level documents only Sylvain Galineau
• Re: [css-device-adapt] Apply @viewport to top-level documents only Sylvain Galineau
• Re: [css-device-adapt] Apply @viewport to top-level documents only François REMY
• [css3-break] Summary of recent comments Alan Stearns
• Re: [css-device-adapt] Apply @viewport to top-level documents only Sylvain Galineau
• Re: [css-device-adapt] Apply @viewport to top-level documents only François REMY
• Re: [css-device-adapt] Apply @viewport to top-level documents only Sylvain Galineau
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-ui] text-overflow: fade ? François REMY
• Re: [css-ui] text-overflow: fade ? Brad Kemper
• Re: [css-device-adapt] Apply @viewport to top-level documents only François REMY
• Re: [css-device-adapt] Apply @viewport to top-level documents only Sylvain Galineau
• Re: [css-device-adapt] Apply @viewport to top-level documents only François REMY
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Dirk Schulze
• Re: [css-device-adapt] Apply @viewport to top-level documents only Sylvain Galineau
• Re: [css-device-adapt] Apply @viewport to top-level documents only Rune Lillesveen
• Re: [css-device-adapt] Apply @viewport to top-level documents only Rune Lillesveen
• Re: [css-device-adapt] Apply @viewport to top-level documents only Kenneth Rohde Christiansen
• Re: [css-device-adapt] Avoid referring to Desktop Kenneth Rohde Christiansen
• Re: [css-device-adapt] Apply @viewport to top-level documents only François REMY
• Re: [css-device-adapt] Avoid referring to Desktop Rune Lillesveen
• Re: [css-device-adapt][cssom-view] CSSOM View Kenneth Rohde Christiansen
• [css-device-adapt][cssom-view] CSSOM View Rune Lillesveen
• Re: [css3-gcpm] Complex Footnotes Tony Graham
• Re: [css-shapes] Functional Notation Dirk Schulze
• Re: [css-ui] text-overflow: fade ? Alan Gresley
• Re: [css-ui] text-overflow: fade ? Brad Kemper
• Re: [css-shapes] Functional Notation Brad Kemper
• Re: [css-regions] Possible change to the Region interface Elliott Sprehn
• [css3-gcpm] Complex Footnotes Cramer, Dave
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Rik Cabanier
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Tab Atkins Jr.
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Rik Cabanier
• Re: [css-device-adapt] Apply @viewport to top-level documents only Sylvain Galineau

Thursday, 3 October 2013

• Re: [css-device-adapt] Apply @viewport to top-level documents only L. David Baron

Friday, 4 October 2013

• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Tab Atkins Jr.

Thursday, 3 October 2013

• Re: [css-ui] text-overflow: fade ? Tab Atkins Jr.
• Re: [css-ui] text-overflow: fade ? Rik Cabanier
• Re: [css-ui] text-overflow: fade ? François REMY
• Re: [css-device-adapt] Apply @viewport to top-level documents only Rune Lillesveen
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-regions] Possible change to the Region interface Boris Zbarsky
• Re: [css-regions] Possible change to the Region interface Rik Cabanier
• Re: [css-shapes] Functional Notation Tab Atkins Jr.
• Re: [css-regions] Possible change to the Region interface Tab Atkins Jr.
• Re: [css-ui] text-overflow: fade ? Tab Atkins Jr.
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-ui] text-overflow: fade ? Rik Cabanier
• Re: [css-regions] Possible change to the Region interface Mihnea-Vlad Ovidenie
• Re: [css-ui] text-overflow: fade ? Tab Atkins Jr.
• Re: [css-shapes] Functional Notation Tab Atkins Jr.
• Re: [css-overflow-clipping][css-overflow] First Draft of Overflow Clipping now available! Sylvain Galineau
• Re: [css-device-adapt] Apply @viewport to top-level documents only Sylvain Galineau
• Re: [css3-gcpm] Running elements Brad Kemper
• Re: [CSS21] Absolute positioning and float inherit on same element. Alan Gresley
• Re: [CSS21] Absolute positioning and float inherit on same element. Øyvind Stenhaug
• Re: [css-device-adapt] Apply @viewport to top-level documents only Rune Lillesveen
• Re: [css-device-adapt] Apply @viewport to top-level documents only Kenneth Rohde Christiansen
• Re: [css-device-adapt] Apply @viewport to top-level documents only Sylvain Galineau
• Re: [CSSWG] Minutes Telcon 2013-10-02 Sylvain Galineau
• Re: [CSSWG] Minutes Telcon 2013-10-02 Bjoern Hoehrmann
• [css-text][css-ui] Overflow and ellipses, some in rtl Alan Gresley
• Re: [css-device-adapt] Apply @viewport to top-level documents only Kenneth Rohde Christiansen
• Re: [css-device-adapt] Apply @viewport to top-level documents only Rune Lillesveen
• Re: [css-device-adapt] Apply @viewport to top-level documents only Rune Lillesveen
• [CSS21] Absolute positioning and float inherit on same element. Alan Gresley
• Re: [css-device-adapt] Apply @viewport to top-level documents only François REMY
• Re: [css-device-adapt] Apply @viewport to top-level documents only Henrik Andersson
• [css-device-adapt] Apply @viewport to top-level documents only Rune Lillesveen
• Re: [css-shapes] circle radius as a percentage François REMY
• Re: [css-device-adapt] orientation: descriptor Rune Lillesveen
• Re: [css-shapes] relative box François REMY
• Re: [css-ui] text-overflow: fade ? François REMY
• [CSSWG] Minutes Telcon 2013-10-02 Dael Jackson
• Re: [css-regions] Possible change to the Region interface François REMY
• Re: [css-device-adapt] Issue 5: @viewport inside @media Rune Lillesveen
• Re: [css-overflow-clipping][css-overflow] First Draft of Overflow Clipping now available! Alan Gresley
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Alan Gresley
• [css-masking] Review request before LC Dirk Schulze
• Re: [css-shapes] Functional Notation Dirk Schulze
• RE: [css-images] Intent to implement object-fit and object-position in Blink Israel Hilerio
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Sylvain Galineau
• RE: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Koji Ishii
• Re: [css-shapes] Functional Notation fantasai
• Re: [css-shapes] Functional Notation fantasai
• Re: [css-shapes] Functional Notation fantasai

Wednesday, 2 October 2013

• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Tab Atkins Jr.
• Re: JavaScript-Driven Accelerated Animations Ian Vollick
• Re: JavaScript-Driven Accelerated Animations Tab Atkins Jr.
• Re: JavaScript-Driven Accelerated Animations Robert O'Callahan
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Tab Atkins Jr.
• Re: JavaScript-Driven Accelerated Animations Ian Vollick
• Re: JavaScript-Driven Accelerated Animations Ian Vollick
• Re: [css-device-adapt] Issue 5: @viewport inside @media Simon Sapin
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Robert O'Callahan
• Re: JavaScript-Driven Accelerated Animations Robert O'Callahan
• Re: Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Tab Atkins Jr.
• Re: Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Simon Sapin
• Re: [css-regions] Possible change to the Region interface Alan Stearns
• Re: JavaScript-Driven Accelerated Animations Tab Atkins Jr.
• Re: JavaScript-Driven Accelerated Animations Tab Atkins Jr.
• Re: JavaScript-Driven Accelerated Animations Boris Zbarsky
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Tab Atkins Jr.
• JavaScript-Driven Accelerated Animations Ian Vollick
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Robert O'Callahan
• Re: [css-device-adapt] Issue 5: @viewport inside @media Rune Lillesveen
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Tab Atkins Jr.
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Robert O'Callahan
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Tab Atkins Jr.
• Re: [css-overflow-clipping] First Draft of Overflow Clipping now available! Robert O'Callahan
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Sylvain Galineau
• [css-overflow-clipping] First Draft of Overflow Clipping now available! Tab Atkins Jr.
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-shapes] Functional Notation Tab Atkins Jr.
• Re: Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Tab Atkins Jr.
• Re: [css-shapes] Functional Notation Dirk Schulze
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Simon Sapin
• Re: Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Tab Atkins Jr.
• [css3-ui] Re: Referring to elements from CSS Simon Sapin
• Re: Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Simon Sapin
• Re: [css-shapes] Functional Notation Tab Atkins Jr.
• Re: [css-shapes] Functional Notation Tab Atkins Jr.
• RE: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Koji Ishii
• Re: [css-shapes] Functional Notation fantasai
• Re: Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Simon Sapin
• Re: [css3-gcpm] Running elements Alan Stearns
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Sylvain Galineau
• Re: [css-shapes] Functional Notation Dirk Schulze
• RE: [css-text] Clusters for letter spacing in Thai and other complex scripts Koji Ishii
• RE: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Koji Ishii
• Re: [css-shapes] Functional Notation fantasai
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Sylvain Galineau
• Re: Agenda conf call 02-oct-2013 Lea Verou
• RE: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Koji Ishii
• Re: [css3-gcpm] Running elements Cramer, Dave
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Sylvain Galineau
• Re: [css-shapes] Re: Agenda conf call 02-oct-2013 Sylvain Galineau
• RE: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Koji Ishii
• Re: [css-shapes] Re: Agenda conf call 02-oct-2013 Alan Stearns
• Re: [css-device-adapt] Avoid referring to Desktop Kenneth Rohde Christiansen
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Sylvain Galineau
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Simon Pieters
• Re: [css-page] Meaning of :first page selector (was: [css3-gcpm] Page groups, named pages, and :first) Cramer, Dave
• Re: Agenda conf call 02-oct-2013 Glenn Adams
• Re: [css-device-adapt] Avoid referring to Desktop Rick Byers
• [css-device-adapt] Avoid referring to Desktop Kenneth Rohde Christiansen
• [css-device-adapt] orientation: descriptor Kenneth Rohde Christiansen
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Robert O'Callahan
• RE: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Koji Ishii
• [css-shapes] Re: Agenda conf call 02-oct-2013 Håkon Wium Lie
• Re: Agenda conf call 02-oct-2013 Simon Sapin
• Re: Agenda conf call 02-oct-2013 Simon Sapin
• Agenda conf call 02-oct-2013 Daniel Glazman
• Re: Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Simon Sapin
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Simon Pieters
• Re: [css-text] Clusters for letter spacing in Thai and other complex scripts James Clark
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-shapes] relative box Alan Stearns
• Re: [css-shapes] Functional Notation fantasai
• Re: [css-shapes] Minor Comments Alan Stearns
• Re: [css-shapes] relative box fantasai
• Re: [css-shapes] Minor Comments fantasai
• Re: [css-shapes] Minor Comments Alan Stearns
• Re: [css-shapes] Minor Comments fantasai
• Re: [css-shapes] relative box Alan Stearns

Tuesday, 1 October 2013

• Re: [css-grid] Intrinsic / preferred logical widths on the grid element Tab Atkins Jr.
• [css-grid] Intrinsic / preferred logical widths on the grid element Julien Chaffraix
• Re: [css-shapes] Minor Comments Alan Stearns
• Re: [css-ui] text-overflow: fade ? Tab Atkins Jr.
• Re: Selectors: hooks needed by DOM Tab Atkins Jr.
• [css-ui] text-overflow: fade ? Tab Atkins Jr.
• Re: Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Tab Atkins Jr.
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [css-shapes] review comments Alan Stearns
• Re: [css-shapes] Functional Notation Tab Atkins Jr.
• Re: [css-page-floats] Non-page-floats sections Håkon Wium Lie
• Re: [cssom-view] Behavior of getBoxQuads, convert*FromNode Robert O'Callahan
• Referring to elements from CSS. (In, but not limited to [css-images-4] and [css-gcpm]) Simon Sapin
• Re: [css-page-floats] Non-page-floats sections Daniel Glazman
• [cssom-view] Behavior of getBoxQuads, convert*FromNode Simon Pieters
• Re: [css-shapes] Functional Notation Alan Stearns
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Robert O'Callahan
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Simon Pieters
• Re: [css-shapes] Functional Notation fantasai
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Simon Pieters
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Robert O'Callahan
• Re: [css-regions] Possible change to the Region interface Boris Zbarsky
• Re: [cssom-view] DOMRect with aliases x, y to left, top? François REMY
• [css-page-floats] ED 20130924 - minor editorial Tony Graham
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Simon Pieters
• Re: [css-images] Intent to implement object-fit and object-position in Blink Morten Stenshorne
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Henrik Andersson
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Henrik Andersson
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Henrik Andersson
• Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions Simon Pieters
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Simon Pieters
• Re: [css-regions] Possible change to the Region interface Cameron McCormack
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Dirk Schulze
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Henrik Andersson
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Dirk Schulze
• Re: [cssom-view] DOMRect with aliases x, y to left, top? Simon Pieters
• Re: [CSSWG] Minutes Paris F2F 2013-09-12 III: GCPM Simon Sapin
• Re: Selectors: hooks needed by DOM Simon Sapin
• Re: [css-shapes] Functional Notation Dirk Schulze
• [css-shapes] Functional Notation fantasai
• [css-shapes] relative box fantasai
• [css-shapes] Minor Comments fantasai
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' James Clark
• [css-shapes] review comments Dirk Schulze
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' James Clark
• Re: [css-images] Intent to implement object-fit and object-position in Blink Anselm Hannemann
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' John Daggett
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' John Daggett
• Re: objection re: RESOLVED: setProperty's handling of importance logically behaves same as appending a declaraiton (like IE/WebKit) Zack Weinberg
• Re: [css-shapes][cssom] Serializing Shape Values Alan Stearns
• Re: [css-images] Intent to implement object-fit and object-position in Blink Israel Hilerio
• Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation' Sylvain Galineau
• Re: [css-regions] Possible change to the Region interface Elliott Sprehn
• Re: objection re: RESOLVED: setProperty's handling of importance logically behaves same as appending a declaraiton (like IE/WebKit) L. David Baron
• [CSSWG] Minutes Paris F2F 2013-09-13 Fri V: Text, Writing Modes, Animations Dael Jackson
• [CSSWG] Minutes Paris F2F 2013-09-13 Fri IV: Ruby Dael Jackson

Last message date: Thursday, 31 October 2013 19:18:29 UTC