www-style@w3.org from June 2012 by date

Saturday, 30 June 2012

• RE: [css3-writing-modes] vertical orientation and UTR50 Sylvain Galineau
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• Re: [css3-writing-modes] vertical orientation and UTR50 Glenn Adams
• RE: [css3-writing-modes] vertical orientation and UTR50 Sylvain Galineau
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• RE: [css3-writing-modes] vertical orientation and UTR50 Sylvain Galineau

Friday, 29 June 2012

• RE: [css3-writing-modes] vertical orientation and UTR50 Sylvain Galineau
• Re: [css4-ui] Scrollbar tracking control Sebastian Zartner
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• RE: [css3-writing-modes] vertical orientation and UTR50 Sylvain Galineau
• RE: [css3-writing-modes] vertical orientation and UTR50 Sylvain Galineau
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• Re: [css3-flexbox] Algorithm never clamps inflexible children, when all children are inflexible Daniel Holbert
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• Re: [css3-writing-modes] vertical orientation and UTR50 Alan Stearns
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• RE: [css3-writing-modes] vertical orientation and UTR50 Sylvain Galineau
• Re: [css3-writing-modes] vertical orientation and UTR50 Glenn Adams
• Re: [css3-values] Required minimum precision Florian Rivoal
• Re: [css3-values] Required minimum precision Florian Rivoal
• Re: [css3-values] Required minimum precision Florian Rivoal
• Re: [css3-values] Required minimum precision Florian Rivoal
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• Re: [css3-writing-modes] vertical orientation and UTR50 John Daggett
• RE: [css3-writing-modes] vertical orientation and UTR50 Koji Ishii
• [css3-writing-modes] vertical orientation and UTR50 John Daggett
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements L. David Baron
• [css-background] No reference to CSS Image Values and Replaced Content Sebastian Zartner
• Re: Sticky Positioning Alexandre Elias
• Re: [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Daniel Holbert
• Re: [css3-values] Required minimum precision Robert O'Callahan
• Re: [cssom-view] Definition of scrollWidth doesn't seem to make sense Robert O'Callahan
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Robert O'Callahan
• Re: [cssom-view] Definition of scrollWidth doesn't seem to make sense Elliott Sprehn
• Re: [css3-flexbox] question about calculating "hypothetical main size" Kang-Hao (Kenny) Lu
• Re: [css3-flexbox] question about calculating "hypothetical main size" Tab Atkins Jr.
• Re: [css3-flexbox] Algorithm never clamps inflexible children, when all children are inflexible Tab Atkins Jr.
• RE: [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Alex Mogilevsky
• Re: Sticky Positioning Brad Kemper
• Re: [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Tab Atkins Jr.
• Re: [css3-values] Required minimum precision Liam R E Quin

Thursday, 28 June 2012

• Re: Sticky Positioning Maciej Stachowiak
• Re: [css3-values] Required minimum precision L. David Baron
• Re: Sticky Positioning Maciej Stachowiak
• Re: Sticky Positioning Alexandre Elias
• Re: [css3-values] Required minimum precision Boris Zbarsky
• [css3-values] Disposition of Comments, remaining issues, and moving to CR fantasai
• Re: Sticky Positioning Maciej Stachowiak
• Re: [css3-values] Required minimum precision Tab Atkins Jr.
• Re: [css3-values] Required minimum precision Boris Zbarsky
• Re: [css3-values] Required minimum precision Tab Atkins Jr.
• Re: [css3-values] reserved keywords and user-defined identifiers Tab Atkins Jr.
• Re: [css3-values] Required minimum precision Boris Zbarsky
• [css3-values] Required minimum precision Tab Atkins Jr.
• Re: Sticky Positioning Maciej Stachowiak
• [css3-values] Issue 18 proposal - defining an always-invalid URL Tab Atkins Jr.
• Re: [CSSWG] Minutes and Resolutions 2012-06-27 fantasai
• Re: Sticky Positioning Simon Fraser
• Re: Sticky Positioning Brad Kemper
• Re: [CSS21] os/2 and hhea tables Gérard Talbot
• [css3-flexbox] question about calculating "hypothetical main size" Kang-Hao (Kenny) Lu
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Florian Rivoal
• Re: boxes within boxes within boxes (SOLVED) william drescher
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Aryeh Gregor

Wednesday, 27 June 2012

• boxes within boxes within boxes william drescher
• Re: Sticky Positioning Alexandre Elias

Thursday, 28 June 2012

• Re: [css3-flexbox] Painting order Morten Stenshorne
• [css3-flexbox] Paint flex items atomically? Morten Stenshorne
• Re: Sticky Positioning Simon Fraser
• Re: Sticky Positioning Simon Fraser
• Re: [CSS21] os/2 and hhea tables Gérard Talbot
• Re: Sticky Positioning Bjoern Hoehrmann
• Re: [css3-regions] Improve the NamedFlow JS interface Alan Stearns

Wednesday, 27 June 2012

• Re: [CSS21] os/2 and hhea tables Peter Moulder
• Re: [css3-flexbox] Painting order Tab Atkins Jr.
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Tab Atkins Jr.
• Re: Sticky Positioning Tab Atkins Jr.
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? fantasai
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Simon Fraser
• [CSSWG] Minutes and Resolutions 2012-06-27 fantasai
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Robert O'Callahan
• Re: [css4-background] background-position-x and background-position-y or logical directions Edward O'Connor
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Robert O'Callahan
• Re: [css3-text] Why is the definition of word in text-transform non normative Eric Muller
• Re: Sticky Positioning Robert O'Callahan
• [cssom] .style on CSSFontFaceRule and CSSPageRule should probably not be CSSStyleDeclarations as that interface is currently defined Boris Zbarsky
• Re: [css3-flexbox] Painting order Morten Stenshorne
• RE: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Sylvain Galineau
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Christoph Päper
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Daniel Holbert
• RE: [css4-background] background-position-x and background-position-y or logical directions Sylvain Galineau
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Boris Zbarsky
• RE: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Alex Mogilevsky
• Re: Sticky Positioning Edward O'Connor
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Tab Atkins Jr.
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Tab Atkins Jr.
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Simon Fraser
• Re: [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Tab Atkins Jr.
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Boris Zbarsky
• Re: [css3-values] vmax, please! Brad Kemper
• [css3-transforms] Proposal for behavior of background-attachment:fixed inside transformed elements Simon Fraser
• RE: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Alex Mogilevsky
• Re: [css3-flexbox] Painting order Tab Atkins Jr.
• Re: [css3-flexbox] Painting order Morten Stenshorne
• Agenda conf call 27-jun-2012 Daniel Glazman
• Re: [css4-background] background-position-x and background-position-y or logical directions Brad Kemper
• Re: Sticky Positioning Ojan Vafai
• Re: [css4-selectors] Pseudo-class for writing mode Tab Atkins Jr.

Tuesday, 26 June 2012

• Sticky Positioning Edward O'Connor
• RE: [css4-background] background-position-x and background-position-y or logical directions Sylvain Galineau
• RE: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Sylvain Galineau
• RE: [css4-background] background-position-x and background-position-y or logical directions Brian Manthos
• Re: [css4-background] background-position-x and background-position-y or logical directions Brad Kemper
• Re: [css3-values] nesting calc() Pete Boere
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Brad Kemper
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Brad Kemper
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Anton Prowse
• RE: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Sylvain Galineau
• RE: [css4-background] background-position-x and background-position-y or logical directions Sylvain Galineau
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Kang-Hao (Kenny) Lu
• RE: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Sylvain Galineau
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Boris Zbarsky
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Kang-Hao (Kenny) Lu
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Kang-Hao (Kenny) Lu
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Boris Zbarsky
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Jonathan Kew
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Kang-Hao (Kenny) Lu
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Kang-Hao (Kenny) Lu
• Re: [css4-background] background-position-x and background-position-y or logical directions Florian Rivoal
• Re: [css4-background] background-position-x and background-position-y or logical directions Markus Ernst
• Re: [css4-selectors] Pseudo-class for writing mode Joshua Cranmer
• Re: [css4-background] background-position-x and background-position-y or logical directions Florian Rivoal
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Florian Rivoal
• Re: [css3-flexbox] Painting order Morten Stenshorne
• Re: [css4-selectors] Pseudo-class for writing mode François REMY
• Re: [CSS21] [section 10.6.3] Height of block-level non-replaced elements in normal flow: editorial correction? Anton Prowse
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Anton Prowse
• Re: [css3-flexbox] ordering and accessibility concerns fantasai
• Re: [css4-selectors] Pseudo-class for writing mode Sebastian Zartner
• Re: [css3-regions] Clarification on getRegionFlowRanges with display:none nodes Tab Atkins Jr.

Monday, 25 June 2012

• Re: [css3-regions] Clarification on getRegionFlowRanges with display:none nodes Alan Stearns
• Re: [css3-flexbox] ordering and accessibility concerns Tab Atkins Jr.
• Re: [css3-cascade] inheritance and ::backdrop fantasai
• Re: [css3-flexbox] ordering and accessibility concerns fantasai
• Re: [css3-regions] Clarification on getRegionFlowRanges with display:none nodes Tab Atkins Jr.
• Re: [css3-flexbox] ordering and accessibility concerns Tab Atkins Jr.
• Re: [css3-flexbox] Painting order Tab Atkins Jr.
• Re: inheritance and ::backdrop Tab Atkins Jr.
• [CSS21] [section 10.6.3] Height of block-level non-replaced elements in normal flow: editorial correction? Gérard Talbot
• Re: [css4-selectors] Pseudo-class for writing mode Bjoern Hoehrmann
• inheritance and ::backdrop fantasai
• Re: [css3-values] nesting calc() Kang-Hao (Kenny) Lu
• Re: [css3-gcpm] Float direction logical values are badly named Tab Atkins Jr.
• Re: [css3-exclusions] ordering exclusions by z-order Tab Atkins Jr.
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Daniel Holbert
• RE: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? j.j.
• Re: [css4-selectors] Pseudo-class for writing mode Tab Atkins Jr.
• Re: [css4-background] background-position-x and background-position-y or logical directions Tab Atkins Jr.
• Re: [css3-values] nesting calc() Tab Atkins Jr.
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue fantasai
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Tab Atkins Jr.
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Daniel Holbert
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue fantasai
• RE: [css3-flexbox] Negative flexibility and proportional shrinking Alex Mogilevsky
• Re: [css3-flexbox] Painting order fantasai
• Re: [css3-conditional] incorporating non-normative modifications from css3-mediaqueries L. David Baron
• RE: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Sylvain Galineau
• Re: [css4-background] background-position-x and background-position-y or logical directions Brad Kemper
• Re: [css3-regions] Improve the NamedFlow JS interface Andrei Bucur
• Re: [css4-background] background-position-x and background-position-y or logical directions Florian Rivoal
• [css3-conditional] Florian Rivoal
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Florian Rivoal
• Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Morten Stenshorne
• [css3-flexbox] Painting order Morten Stenshorne
• [css3-flexbox] Negative flexibility and proportional shrinking Morten Stenshorne

Sunday, 24 June 2012

• Re: [CSS21] os/2 and hhea tables Adam Twardoch (List)
• RE: [CSS21] os/2 and hhea tables Roger Baker
• RE: [CSS21] os/2 and hhea tables Roger Baker
• Re: [CSS21] The 'clear' property on table wrappers. Anton Prowse

Saturday, 23 June 2012

• Re: [CSS21] os/2 and hhea tables Adam Twardoch (List)
• Re: [css4-background] background-position-x and background-position-y or logical directions Brad Kemper
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Jonathan Kew
• Re: [css3-ui] padding-box at risk? Daniel Tan/BoltClock
• [css3-ui] padding-box at risk? Rudolph Gottesheim
• Re: [CSS21] os/2 and hhea tables Gérard Talbot
• Re: [CSS21] os/2 and hhea tables Gérard Talbot
• [CSS21] os/2 and hhea tables Roger Baker
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Christoph Päper
• Re: [css3-page] Effect of 'visibility: hidden' on page boxes Simon Sapin

Friday, 22 June 2012

• Re: [css3-page] Effect of 'visibility: hidden' on page boxes fantasai
• Re: [css3-page][css3-background] Canvas background painting and positioning area fantasai
• Re: [css3-writing-modes] before/after terminology alternative? Brad Kemper
• Re: [css-regions] Shadow DOM and Regions CSSOM Dimitri Glazkov
• Re: [css4-ui] Scrollbar tracking control Brad Kemper
• Re: [css3-writing-modes] before/after terminology alternative? Alan Gresley
• Re: [css3-writing-modes] column progression direction Alan Gresley
• Re: [css-variables] CSS Custom Properties L1 François REMY
• Re: [css-variables] CSS Custom Properties L1 Simon Sapin
• Re: [css4-background] background-position-x and background-position-y or logical directions Florian Rivoal
• Re: [css3-background] Computed value of background-position, and other background-* Florian Rivoal
• [css3-break][css3-text] Applying break-* to inline elements fantasai
• Re: [css4-selectors] Typo in :dir pseudo-class section fantasai
• Re: [css4-selectors] Pseudo-class for writing mode fantasai
• Re: [css3-background] Animatable: lines fantasai
• [css4-selectors] Pseudo-class for writing mode Sebastian Zartner
• [css4-selectors] Typo in :dir pseudo-class section Sebastian Zartner
• Re: [css4-ui] Scrollbar tracking control Sebastian Zartner
• Re: [cssom-view] Definition of scrollWidth doesn't seem to make sense Robert O'Callahan
• Re: [cssom-view] Definition of scrollWidth doesn't seem to make sense Robert O'Callahan
• RE: [css3-background] Corner clipping and mouse events Sylvain Galineau

Thursday, 21 June 2012

• [cssom-view] scrollMaxX/Y Robert O'Callahan
• Re: [css3-background] Corner clipping and mouse events fantasai
• Re: [css3-exclusions] ordering exclusions by z-order Robert O'Callahan
• Re: [cssom-view] scrollHeight and scrollWidth definitions have some problems Robert O'Callahan
• Re: [css4-background] background-position-x and background-position-y or logical directions fantasai
• Re: [css3-flexbox] ordering and accessibility concerns fantasai
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 fantasai
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 fantasai
• Re: [css3-page][CSS21] Margins at forced/unforced page breaks Simon Sapin
• Re: [css3-background] Computed value of background-position, and other background-* fantasai
• Re: [css3-background][css4-background] Incorrect instructions on how to give feedback fantasai
• Re: [css3-page][CSS21] Margins at forced/unforced page breaks fantasai
• [css3-regions] Clarification on getRegionFlowRanges with display:none nodes Alan Stearns
• Re: [css-variables] CSS Custom Properties L1 François REMY
• Re: [css-regions] Shadow DOM and Regions CSSOM Alan Stearns
• Re: [css3-regions] Improve the NamedFlow JS interface Alan Stearns
• Re: [css-variables] CSS Custom Properties L1 Simon Sapin
• RE: CfC: publish FPWD of Fullscreen spec; deadline May 24 Sylvain Galineau
• Re: [css-variables] CSS Custom Properties L1 François REMY
• RE: [css4-background] background-position-x and background-position-y or logical directions Sylvain Galineau
• Re: [css-variables] CSS Custom Properties L1 Simon Sapin
• Re: [css4-background] background-position-x and background-position-y or logical directions Brad Kemper
• Re: [css-variables] CSS Custom Properties L1 François REMY
• Re: [css4-background] background-position-x and background-position-y or logical directions Florian Rivoal
• Re: [css3-regions] Improve the NamedFlow JS interface Andrei Bucur
• Re: [css4-background] background-position-x and background-position-y or logical directions Marat Tanalin | tanalin.com
• Re: [css3-writing-modes] column progression direction Leif Arne Storset
• [css4-background] background-position-x and background-position-y or logical directions Florian Rivoal
• Re: [css3-background] Computed value of background-position Florian Rivoal
• [css3-background] Computed value of background-position, and other background-* Florian Rivoal
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Daniel Glazman
• [css3-background][css4-background] Incorrect instructions on how to give feedback Florian Rivoal
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Arthur Barstow
• Re: [css3-writing-modes] before/after terminology alternative? Koji Ishii
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Anne van Kesteren
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Anne van Kesteren
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Anne van Kesteren
• Re: [css3-page][CSS21] Margins at forced/unforced page breaks Simon Sapin
• Re: [css3-flexbox][css3-ui] ordering and accessibility concerns Brad Kemper
• Re: [css3-values] nesting calc() Christoph Päper
• RE: [css3-writing-modes] column progression direction Koji Ishii
• [css3-writing-modes] column progression direction fantasai
• Re: [css3-writing-modes] before/after terminology alternative? fantasai
• Re: Replacing [isolate || bidi-override] by isolate | bidi-override | isolate-override fantasai
• RE: [css3-flexbox] ordering and accessibility concerns John Foliot

Wednesday, 20 June 2012

• Re: [css3-flexbox][css3-ui] ordering and accessibility concerns fantasai
• Re: [css3-flexbox] ordering and accessibility concerns Marat Tanalin | tanalin.com
• [css3-flexbox] ordering and accessibility concerns fantasai
• Re: [css3-page][CSS21] Margins at forced/unforced page breaks fantasai
• Re: [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? fantasai
• [CSSWG] Minutes and Resolutions 2012-06-20 fantasai
• [CSS21] [CSS3 Text] Should 'text-transform: uppercase' apply to input type="text" (text entered, typed in text field by user)? Gérard Talbot
• Re: [css4-ui] Scrollbar tracking control Brad Kemper
• Re: CSS + Shadow DOM = <3 + more François REMY
• Re: [css3-background] Corner clipping and mouse events Brad Kemper
• [css-regions] Shadow DOM and Regions CSSOM Andrei Bucur
• Re: [css-variables] CSS Custom Properties L1 Kang-Hao (Kenny) Lu
• Re: [css-variables] CSS Custom Properties L1 Brian Kardell
• [css3-page][CSS21] Margins at forced/unforced page breaks Simon Sapin
• [css3-gcpm] Float direction logical values are badly named Nicholas Shanks
• Re : Re : [css3-values] nesting calc() François REMY
• Re: Re : [css3-values] nesting calc() Kang-Hao (Kenny) Lu
• Re : [css3-values] nesting calc() François REMY
• Re: [css3-values] nesting calc() Kang-Hao (Kenny) Lu
• Re: [css3-values] nesting calc() François REMY
• RE: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue Alex Mogilevsky
• Re: [css3-animations] Interaction of timing functions specified in a keyframe with properties defined in other keyframes L. David Baron
• [css3-animations] Interaction of timing functions specified in a keyframe with properties defined in other keyframes Sylvain Galineau

Tuesday, 19 June 2012

• Re: [css3-regions] Regions as non-replaced block containers Alan Stearns
• Agenda conf call 20-jun-2012 Linss, Peter
• Re: [CSSOM-view] Support centering an element when scrolling into view. Thaddee Tyl
• Re: [css3-animations] updating 'animation-fill-mode' definition Brian Birtles
• Re: [CSS21] Making URLs absolute (Was: Re: [css3-background] Fixing the computed value line for some properties) fantasai
• Re: [CSSOM-view] Support centering an element when scrolling into view. Thaddee Tyl
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Tobie Langel
• Re: [css3-values] nesting calc() Kang-Hao (Kenny) Lu
• RE: CfC: publish FPWD of Fullscreen spec; deadline May 24 Sylvain Galineau
• Re: [css3-values] nesting calc() François REMY
• [css3-animations] updating 'animation-fill-mode' definition L. David Baron
• [css3-values] nesting calc() fantasai
• [css3-background] Corner clipping and mouse events Sylvain Galineau
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Daniel Glazman
• [css3-break] page-break: recto/verso fantasai
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 fantasai
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 fantasai
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Arthur Barstow
• Re: Selectable text inside block level links (was Re: Clickable area for hyperlinks) Leif Arne Storset
• [css3-mediaqueries] CSS Media Queries Recommendation Published Florian Rivoal
• Re: [css3-page] 9.4. Allowed page breaks Simon Sapin
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Daniel Glazman
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Arthur Barstow
• Re: [css3-page] preferred height, containing blocks, counters, vertical-align, size, links MURAKAMI Shinyu
• Re: [css3-page] Effect of 'visibility: hidden' on page boxes MURAKAMI Shinyu
• Re: [css3-page][css3-background] Canvas background painting and positioning area MURAKAMI Shinyu
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Daniel Glazman
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Daniel Glazman
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Anne van Kesteren
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Anne van Kesteren

Monday, 18 June 2012

• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 fantasai
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 fantasai
• Re: [css4-color] unclamped values for RGB Rik Cabanier
• Re: [CSS21] Can internal table elements be relatively positioned, or establish stacking contexts? Anton Prowse
• RE: [css3-regions] flow-into and iframes Alex Mogilevsky
• [css-variables] CSS Custom Properties L1 François REMY
• [css3-box] interactions of overflow-x and overflow-y L. David Baron
• [css3-page] 9.4. Allowed page breaks Simon Sapin
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Arthur Barstow
• Re: [CSS21] Can internal table elements be relatively positioned, or establish stacking contexts? Øyvind Stenhaug
• Re: [css4-color] unclamped values for RGB Alan Gresley

Sunday, 17 June 2012

• [css3-regions] flow-into and iframes Rob Crowther
• Re: [css4-color] unclamped values for RGB Rik Cabanier
• Re: [css4-color] unclamped values for RGB Rik Cabanier
• Re: [CSS21] Can internal table elements be relatively positioned, or establish stacking contexts? Simon Sapin
• Re: [CSS21] The 'clear' property on table wrappers. Simon Sapin
• Re: [CSS21] The 'clear' property on table wrappers. Anton Prowse

Saturday, 16 June 2012

• Re: [css21] Objection to erratum [Was: Re: NUMBER vs <number>] Tab Atkins Jr.
• [CSS21] Can internal table elements be relatively positioned, or establish stacking contexts? Anton Prowse
• Re: [css21] Objection to erratum [Was: Re: NUMBER vs <number>] Anton Prowse
• Re: [css21] Objection to erratum [Was: Re: NUMBER vs <number>] Tab Atkins Jr.
• Re: CSS + Shadow DOM = <3 + more Dimitri Glazkov
• Re: [css21] URL token grammar doesn't match reality Anton Prowse
• Re: [css-variables] and [css-colors] Tab Atkins Jr.
• Re: CSS + Shadow DOM = <3 + more François REMY
• Re: [CSS21] Width of an absolutely positioned table. Anton Prowse
• [CSS21] Making URLs absolute (Was: Re: [css3-background] Fixing the computed value line for some properties) Anton Prowse
• Re: [css21][css3-syntax] $foo in the core grammar Anton Prowse
• [css21] Objection to erratum [Was: Re: NUMBER vs <number>] Anton Prowse
• [css-variables] and [css-colors] François REMY
• [css-colors] references an inexistant property François REMY
• Re: [CSS21] The 'clear' property on table wrappers. Simon Sapin
• Re: [CSS21] The 'clear' property on table wrappers. Anton Prowse
• Re: [css3-page][css3-mediaqueries] Changing element styles on page breaks Simon Sapin
• Re: [css3-page][css3-mediaqueries] Changing element styles on page breaks Brad Kemper
• Re: Selectable text inside block level links (was Re: Clickable area for hyperlinks) Boris Zbarsky
• Re: Selectable text inside block level links (was Re: Clickable area for hyperlinks) Philippe Wittenbergh
• Re: [css4-color] unclamped values for RGB Bjoern Hoehrmann

Friday, 15 June 2012

• Re: CSS + Shadow DOM = <3 + more Dimitri Glazkov
• Re: [css4-color] unclamped values for RGB Tab Atkins Jr.
• Re: [css4-color] unclamped values for RGB Rik Cabanier
• Re: Selectable text inside block level links (was Re: Clickable area for hyperlinks) Boris Zbarsky
• Re: Selectable text inside block level links (was Re: Clickable area for hyperlinks) Tab Atkins Jr.
• Selectable text inside block level links (was Re: Clickable area for hyperlinks) André Luís
• Re: [css4-color] unclamped values for RGB Tab Atkins Jr.
• Re: CSS + Shadow DOM = <3 + more Tab Atkins Jr.
• [css4-color] unclamped values for RGB Rik Cabanier
• Re: CSS + Shadow DOM = <3 + more François REMY
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Tab Atkins Jr.
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Rik Cabanier
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Tab Atkins Jr.
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Rik Cabanier
• CSS + Shadow DOM = <3 + more Dimitri Glazkov
• Re: [css4-ui] Scrollbar tracking control Tab Atkins Jr.
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Rik Cabanier
• Re: [css4-ui] Scrollbar tracking control Simon Fraser
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Rik Cabanier
• Re: [CSSOM View] MediaQueryList as EventTarget Dean Jackson
• Re: [css-variables] CSS Variables are a NEW kind of variable Brad Kemper
• Re: [css3-images][css4-images] Replace 'dppx' with 'x'? Simon Fraser
• Re: [css3-images][css4-images] Replace 'dppx' with 'x'? Kenneth Rohde Christiansen
• Re: [css3-images][css4-images] Replace 'dppx' with 'x'? Florian Rivoal
• Re: Clickable area for hyperlinks Florian Rivoal
• Re: [css4-ui] Scrollbar tracking control Sebastian Zartner
• Re: [CSSOM View] MediaQueryList as EventTarget Kenneth Rohde Christiansen
• Re: [CSSOM View] MediaQueryList as EventTarget Anne van Kesteren
• Re: [css3-images][css4-images] Replace 'dppx' with 'x'? Tab Atkins Jr.
• Re: (Offtopic) Allowing use of CSS syntax in SVG presentation attributes Peter Moulder
• Re: [css4-ui] Scrollbar tracking control Elliott Sprehn
• Re: [css3-images][css4-images] Replace 'dppx' with 'x'? Simon Fraser
• Re: [css4-ui] Scrollbar tracking control Sebastian Zartner
• Re: [CSSOM View] MediaQueryList as EventTarget L. David Baron
• Re: [CSSOM View] MediaQueryList as EventTarget Glenn Adams
• [CSSOM View] MediaQueryList as EventTarget Dean Jackson
• Re: [css4-ui] Scrollbar tracking control Bjoern Hoehrmann
• Re: [css4-ui] Scrollbar tracking control Tab Atkins Jr.
• Re: [css4-ui] Scrollbar tracking control Tab Atkins Jr.
• Re: [css4-ui] Scrollbar tracking control Elliott Sprehn
• Re: [css4-ui] Scrollbar tracking control L. David Baron

Thursday, 14 June 2012

• Re: [css4-ui] Scrollbar tracking control Bjoern Hoehrmann
• [css4-ui] Scrollbar tracking control Tab Atkins Jr.
• Re: [css3-images][css4-images] Replace 'dppx' with 'x'? Brad Kemper
• Re: [css3-images][css4-images] Replace 'dppx' with 'x'? fantasai
• RE: [css3-exclusions] ordering exclusions by z-order Rossen Atanassov
• Re: [css-variables] CSS Variables are a NEW kind of variable François REMY
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Brian Kardell
• Re: [css-variables] CSS Variables are a NEW kind of variable François REMY
• Re: [css-variables] CSS Variables are a NEW kind of variable François REMY
• Re: [css-variables] CSS Variables are a NEW kind of variable Divya Manian
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Divya Manian
• Re: [css-variables] CSS Variables are a NEW kind of variable Kang-Hao (Kenny) Lu
• Re: [css-variables] CSS Variables are a NEW kind of variable Divya Manian
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable François REMY
• Re: [css-variables] CSS Variables are a NEW kind of variable François REMY
• Re: [css3-images][css4-images] Replace 'dppx' with 'x'? Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Kang-Hao (Kenny) Lu
• RE: [css-variables] CSS Variables are a NEW kind of variable Sylvain Galineau
• Re: [css-variables] CSS Variables are a NEW kind of variable Sebastian Zartner
• Re: [css-variables] CSS Variables are a NEW kind of variable Divya Manian
• Re: [css-variables] CSS Variables are a NEW kind of variable François REMY
• Re: [css3-images][css4-images] Replace 'dppx' with 'x'? Simon Fraser
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Brian Kardell
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: Clickable area for hyperlinks Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Brian Kardell
• RE: [css-variables] CSS Variables are a NEW kind of variable Sylvain Galineau
• Re: Clickable area for hyperlinks Simon Sapin
• Re: Clickable area for hyperlinks Simon Sapin
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable François REMY
• Re: Clickable area for hyperlinks Boris Zbarsky
• Re: Clickable area for hyperlinks Tab Atkins Jr.
• Re: [CSSWG] Minutes and Resolutions Telecon 2012-06-13 Tab Atkins Jr.
• Re: Clickable area for hyperlinks Simon Sapin
• Re: Clickable area for hyperlinks Boris Zbarsky
• Re: Clickable area for hyperlinks Simon Sapin
• Re: [css-variables] CSS Variables are a NEW kind of variable Brian Kardell
• Re: [css-variables] CSS Variables are a NEW kind of variable François REMY
• Re: [CSSWG] Minutes and Resolutions Telecon 2012-06-13 Marat Tanalin | tanalin.com
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Alan Gresley
• Clickable area for hyperlinks Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: (Offtopic) Allowing use of CSS syntax in SVG presentation attributes Liam R E Quin
• Re: [css-variables] CSS Variables are a NEW kind of variable Kang-Hao (Kenny) Lu
• (Offtopic) Allowing use of CSS syntax in SVG presentation attributes Peter Moulder
• RE: [css-variables] CSS Variables are a NEW kind of variable Sylvain Galineau
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.

Wednesday, 13 June 2012

• Re: [css-variables] CSS Variables are a NEW kind of variable Divya Manian
• Re: [css-variables] CSS Variables are a NEW kind of variable Chris Eppstein
• Re: [css-variables] CSS Variables are a NEW kind of variable L. David Baron
• Re: [css-variables] CSS Variables are a NEW kind of variable Jonathan Camenisch
• Re: [css-variables] CSS Variables are a NEW kind of variable Chris Eppstein
• Re: [css-variables] CSS Variables are a NEW kind of variable Chris Eppstein
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Chris Eppstein
• [CSSWG] Minutes and Resolutions Telecon 2012-06-13 fantasai
• Re: [css3-writing-modes] available vs fill-available and multiple specs with definitions Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-writing-modes] available vs fill-available and multiple specs with definitions Tab Atkins Jr.
• Re: [css3-writing-modes] available vs fill-available and multiple specs with definitions Elliott Sprehn
• Re: [css-variables] CSS Variables are a NEW kind of variable François REMY
• Re: [css3-writing-modes] available vs fill-available and multiple specs with definitions Tab Atkins Jr.
• Re: [css3-writing-modes] available vs fill-available and multiple specs with definitions Tab Atkins Jr.
• Re: [css3-writing-modes] available vs fill-available and multiple specs with definitions Elliott Sprehn
• Re: [css3-writing-modes] available vs fill-available and multiple specs with definitions Simon Sapin
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• [css3-writing-modes] available vs fill-available and multiple specs with definitions Elliott Sprehn
• Re: [css-variables] CSS Variables are a NEW kind of variable Chris Eppstein
• Re: [css-variables] CSS Variables are a NEW kind of variable Tab Atkins Jr.
• Re: [css-variables] CSS Variables are a NEW kind of variable Divya Manian
• Re: [css3-writing-modes] fit-content equation is backwards from the CSS2.1 spec Elliott Sprehn
• Re: [css3-writing-modes] fit-content equation is backwards from the CSS2.1 spec Tab Atkins Jr.
• [css3-writing-modes] fit-content equation is backwards from the CSS2.1 spec Elliott Sprehn
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-selectors] Structural pseudo-classes and the root element. Kang-Hao (Kenny) Lu
• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• [css3-selectors] Structural pseudo-classes and the root element. Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• Agenda conf call 13-jun-2012 Daniel Glazman
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• Re: [css3-page] Instantiating a margin box Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-page] Instantiating a margin box Peter Moulder
• Re: [css3-page][css3-background] Canvas background painting and positioning area Peter Moulder
• [cssom-view] scrollHeight and scrollWidth definitions have some problems Boris Zbarsky
• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• [CSSWG][css3-flexbox] Last Call Working Draft Published fantasai
• [CSSWG][css3-align] CSS3 Box Alignment First Public Working Draft fantasai
• RE: [css3-flexbox] better algorithm for hypothetical main size Alex Mogilevsky
• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• Re: [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Tab Atkins Jr.
• Re: [css3-flexbox] better algorithm for hypothetical main size Tab Atkins Jr.
• Re: [css3-page] odd grammar for @page rules Tab Atkins Jr.
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.

Tuesday, 12 June 2012

• Re: [css3-regions][cssom] Bubbling for the regionLayoutUpdate event Alan Stearns
• RE: [css3-flexbox] better algorithm for hypothetical main size Alex Mogilevsky
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• Re: [css3-page] odd grammar for @page rules fantasai
• RE: [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Alex Mogilevsky
• [css3-page][css3-lists] Implicit Counter Increments fantasai
• Re: [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Daniel Holbert
• Re: [css3-page] Instantiating a margin box fantasai
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• [css3-flexbox] better algorithm for hypothetical main size Alex Mogilevsky
• RE: [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Alex Mogilevsky
• [css-device-adapt] Should the constraining procedure be tied to media queries? Ryan Betts
• [css3-images] Typo in 'image-resolution' - ddpx instead of dppx Tab Atkins Jr.
• Re: [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Daniel Holbert
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• Re: [css3-page] Editorial comments Brad Kemper
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-page] odd grammar for @page rules Simon Sapin
• Re: [css3-page] preferred height, containing blocks, counters, vertical-align, size, links Simon Sapin
• Re: [css3-page] Instantiating a margin box Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-page] Effect of 'visibility: hidden' on page boxes Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• Re: [css3-page] Effect of 'visibility: hidden' on page boxes Liam R E Quin
• Re: [css3-page] Effect of 'visibility: hidden' on page boxes Tab Atkins Jr.
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Boris Zbarsky
• Re: [css3-page] Paged Media Spec Corrections fantasai
• [css3-page] Effect of 'visibility: hidden' on page boxes fantasai
• Re: [css3-page] @page margin_box rule inconsistency fantasai
• Re: [css3-page] Negative Page Dimension fantasai
• Re: [css3-page] margin box layout fantasai
• Re: [css3-page] empty margin boxes fantasai
• Re: [css3-page] Editorial comments fantasai
• Re: [css3-syntax] First draft of parser section completed Tab Atkins Jr.
• RE: [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Alex Mogilevsky
• Re: [css3-page] incorrect sentence in css 3 paged media fantasai
• Re: [css3-page] Default values for properties in page context fantasai
• Re: [css3-page] 6.3.2: "if a box is empty" fantasai
• Re: [css3-flexbox] (Editorial) Plural of basis fantasai
• Re: [css3-page] In the normal flow of the root element? fantasai
• Re: [css3-page] preferred height, containing blocks, counters, vertical-align, size, links fantasai

Monday, 11 June 2012

• Re: [css3-page] odd grammar for @page rules fantasai
• Re: [CSS21] [css3-page] page-break collapsing fantasai
• Re: [css3-page] Inheritance in the page and margin contexts fantasai
• Re: [css3-page] Instantiating a margin box fantasai
• Re: [css3-page] Instantiating a margin box fantasai
• Re: [css3-page] In the normal flow of the root element? Simon Sapin
• RE: [css3-regions][cssom] Bubbling for the regionLayoutUpdate event Alex Mogilevsky
• Re: [css3-page] In the normal flow of the root element? fantasai
• Re: [css3-page][css3-background] Canvas background painting and positioning area Simon Sapin
• [css3-page] Margin boxes: replacing 6.3.2 Variable Dimension Computation Rules Simon Sapin
• [css3-flexbox] min-width & min-height "auto" value -- applies to both axes, or just main axis? Daniel Holbert
• Re: [css3-page][css3-background] Canvas background painting and positioning area fantasai
• RE: [css3-writing-modes] text-combine-mode should allow it being wider than 1em, and also other fallback behavior Koji Ishii
• Re: [css3-page][css3-mediaqueries] Changing element styles on page breaks fantasai
• [css3-page] Instantiating a margin box Simon Sapin
• [css3-page] In the normal flow of the root element? Simon Sapin
• Re: [css3-page][css3-mediaqueries] Changing element styles on page breaks fantasai
• Re: [css3-page] Error in grammar of section 3.4.1 fantasai
• Re: [css3-regions][cssom] Bubbling for the regionLayoutUpdate event Alan Stearns
• Re: [css3-regions][cssom] Bubbling for the regionLayoutUpdate event Andrei Bucur
• RE: [css3-text] scoping line break controls, characters that disappear at the end of lines Koji Ishii
• [css3-fragmentation] Cross-browser consistency Andrei Bucur
• Re: [css3-background] Animatable: lines Kang-Hao (Kenny) Lu
• Re: [selectors3] WIP: a selector parser based on css3-syntax Kang-Hao (Kenny) Lu

Sunday, 10 June 2012

• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Eric A. Meyer
• Re: [css4-values] basic data types in SVG Simon Sapin
• Re: [css4-values] basic data types in SVG Cameron McCormack
• [css4-values] basic data types in SVG (was: [css3-syntax] stroke-dasharray unit less values) Kang-Hao (Kenny) Lu
• Re: [css3-syntax] stroke-dasharray unit less values Cameron McCormack
• [css3-syntax] stroke-dasharray unit less values Dirk Schulze

Saturday, 9 June 2012

• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Witold Baryluk
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Rik Cabanier
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Rik Cabanier
• [selectors3] WIP: a selector parser based on css3-syntax Simon Sapin
• Re: [css3-regions][cssom] Bubbling for the regionLayoutUpdate event Alan Stearns
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Simon Sapin
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Simon Sapin
• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Brad Kemper
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Boris Zbarsky
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Brad Kemper
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Boris Zbarsky
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Brad Kemper
• Re: [css3-syntax] First draft of parser section completed Kang-Hao (Kenny) Lu
• [css3-syntax] First draft of parser section completed Tab Atkins Jr.

Friday, 8 June 2012

• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Tab Atkins Jr.
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? L. David Baron
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Tab Atkins Jr.
• Re: [css4-color] Make the r/g/b components be <number> rather than <integer>? Simon Sapin
• [css4-color] Make the r/g/b components be <number> rather than <integer>? Tab Atkins Jr.
• RE: [css3-flexbox] (Editorial) Plural of basis Sylvain Galineau
• Re: [css3-flexbox] Going to Last Call fantasai
• Re: [css3-flexbox] (Editorial) Plural of basis L. David Baron
• Re: [css3-flexbox] (Editorial) Plural of basis Tab Atkins Jr.
• Re: [css3-flexbox] Going to Last Call Tab Atkins Jr.
• Re: [css3-flexbox] Going to Last Call Peter Gasston
• Re: [css3-flexbox] (Editorial) Plural of basis Daniel Glazman
• [css3-regions] Regions as non-replaced block containers Mihnea-Vlad Ovidenie
• [css3-regions][cssom] Bubbling for the regionLayoutUpdate event Andrei Bucur
• [css3-exclusions] wrap-margin and wrap-padding properties Peter Gasston
• [css3-flexbox] (Editorial) Plural of basis Florian Rivoal
• Re: [css3-writing-modes] height: fill-available's behavior is suboptimal L. David Baron
• [css3-writing-modes] height: fill-available's behavior is suboptimal Tab Atkins Jr.
• Re: [css3-selectors] Valid syntax that never represents an element fantasai
• Re: [css3-background] Animatable: lines Brad Kemper

Thursday, 7 June 2012

• Re: [css3-background] Animatable: lines Tab Atkins Jr.
• [css3-background] Animatable: lines L. David Baron
• Re: [css3-background] Animatable: yes except keyword values Tab Atkins Jr.
• [css3-background] Animatable: yes except keyword values Sylvain Galineau
• Re: [css3-selectors] Valid syntax that never represents an element Tab Atkins Jr.
• Re: [css3-selectors] Valid syntax that never represents an element Simon Sapin
• Re: :hover and :active interaction with labels Ian Hickson
• Re: :hover and :active interaction with labels Tab Atkins Jr.
• Re: [css3-flexbox] order Tab Atkins Jr.
• Re: :hover and :active interaction with labels Ian Hickson
• [css3-flexbox] Going to Last Call fantasai
• Re: [css3-selectors] Valid syntax that never represents an element Tab Atkins Jr.
• Re: [css3-selectors] Valid syntax that never represents an element Kang-Hao (Kenny) Lu
• Re: [css3-selectors] Valid syntax that never represents an element Tab Atkins Jr.
• Re: [css3-flexbox] Initial value of 'justify-content' fantasai
• Re: [css3-selectors] Valid syntax that never represents an element Bjoern Hoehrmann
• [css3-selectors] Valid syntax that never represents an element Lea Verou
• [selectors4] Redundant regexp in the grammar Simon Sapin
• [css3-flexbox] Initial value of 'justify-content' Morten Stenshorne
• Re: [css3-transforms] Effect of CSS transforms on scrollable areas Robert O'Callahan
• Re: [CSSOM-view] Support centering an element when scrolling into view. Robert O'Callahan

Wednesday, 6 June 2012

• [CSSWG] Minutes and Resolutions Telecon 2012-06-06 fantasai
• Re: [css3-flexbox] flex-grow initial value should be 0px Tab Atkins Jr.
• Re: [css3-marquee][css3-gcpm][css3-box] rethinking overflow, overflow-x, overflow-y and overflow-style Brad Kemper
• RE: [css3-flexbox] flex-grow initial value should be 0px Alex Mogilevsky
• RE: [css3-flexbox] 7.3 Components of flexbility Sylvain Galineau
• Re: [css3-marquee][css3-gcpm][css3-box] rethinking overflow, overflow-x, overflow-y and overflow-style Florian Rivoal
• Re : [css-variables] Putting it all toegether (syntax) François REMY
• Re: [css3-flexbox] flex-grow initial value should be 0px Morten Stenshorne
• Re: [css3-lists] Counter style "hyphen" replaced with "dash" fantasai
• Re: [CSSOM-view] Support centering an element when scrolling into view. Thaddee Tyl
• Re: [css3-flexbox] Change the behavior of omitted flex-shrink in the flex shorthand Tab Atkins Jr.
• Re: [css3-flexbox] "flex-basis: auto" means completely different things as specified value vs. computed value Tab Atkins Jr.
• Re: [css3-flexbox] Change the behavior of omitted flex-shrink in the flex shorthand fantasai

Tuesday, 5 June 2012

• Re: [css3-flexbox] "flex-basis: auto" means completely different things as specified value vs. computed value fantasai
• Re: -webkit-background-clip:text and -webkit-text-fill-color? fantasai
• Re: [css3-flexbox] 7.3 Components of flexbility fantasai
• Re: [css3-marquee][css3-gcpm][css3-box] rethinking overflow, overflow-x, overflow-y and overflow-style fantasai

Wednesday, 6 June 2012

• RE: [css3-flexbox] flex-shrink defines a negative flex ratio; negative numbers are invalid Sylvain Galineau
• RE: [css3-flexbox] flex-grow initial value should be 0px Alex Mogilevsky
• [css3-flexbox] Algorithm never clamps inflexible children, when all children are inflexible Daniel Holbert
• Re: [css-variables] Putting it all toegether (syntax) Kang-Hao (Kenny) Lu
• RE: [css3-flexbox] flex-grow initial value should be 0px Alex Mogilevsky
• Re: [css3-flexbox] flex-grow initial value should be 0px Daniel Holbert
• Re: [css3-writing-modes] before/after terminology alternative? Liam R E Quin

Tuesday, 5 June 2012

• RE: Putting it all toegether (syntax) Sylvain Galineau
• Re: [css3-flexbox] flex-grow initial value should be 0px Tab Atkins Jr.
• Re: [css3-flexbox] "flex-basis: auto" means completely different things as specified value vs. computed value Tab Atkins Jr.
• RE: [css3-flexbox] flex-grow initial value should be 0px Alex Mogilevsky
• Re: [css3-flexbox] Typo: "must be specified with a unit" seems to exclude keywords as flex-basis values Tab Atkins Jr.
• Re: [css3-flexbox] Some references to "flex basis" should be replaced with "hypothetical main size" Tab Atkins Jr.
• [css3-flexbox] Typo: "must be specified with a unit" seems to exclude keywords as flex-basis values Daniel Holbert
• [css3-flexbox] Some references to "flex basis" should be replaced with "hypothetical main size" Daniel Holbert
• Putting it all toegether (syntax) Marat Tanalin | tanalin.com
• Re: [CSS21] The 'clear' property on table wrappers. Gérard Talbot
• Agenda conf call 06-jun-2012 Daniel Glazman
• Re: [css3-flexbox] flex-grow initial value should be 0px Daniel Holbert
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 fantasai
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 fantasai
• Re: [css3-flexbox] flex-shrink defines a negative flex ratio; negative numbers are invalid Tab Atkins Jr.
• Re: [CSS21] The 'clear' property on table wrappers. L. David Baron
• [CSS21] The 'clear' property on table wrappers. Simon Sapin
• Re: [css3-flexbox] flex-grow initial value should be 0px fantasai
• Re: [css-variables] Putting it all toegether (syntax) Christoph Päper
• Re: [css-variables] Putting it all toegether (syntax) François REMY
• Re: [CSSOM-view] Support centering an element when scrolling into view. Thaddee Tyl
• Re: [css-variables] Putting it all toegether (syntax) Peter Sorotokin
• Re: [css-variables] Putting it all toegether (syntax) Tab Atkins Jr.
• Re: [css-variables] Putting it all toegether (syntax) Brian Kardell
• [css3-text] text-shadow offsets: physical, not relative Sylvain Galineau
• Re: [css-variables] Putting it all toegether (syntax) Marat Tanalin | tanalin.com

Monday, 4 June 2012

• [css3-flexbox] Nit: One remaining s/flexbox/flex container/ needed in ED Daniel Holbert
• Re: [css-variables] Putting it all toegether (syntax) Tab Atkins Jr.
• Re: [css-variables] Putting it all toegether (syntax) Tab Atkins Jr.
• Re: [css-variables] Putting it all toegether (syntax) Marat Tanalin | tanalin.com
• Re: [css3-flexbox] "flex-basis: auto" means completely different things as specified value vs. computed value Daniel Holbert
• [css-variables] Putting it all toegether (syntax) François REMY
• Re: [css3-flexbox] "flex-basis: auto" means completely different things as specified value vs. computed value Tab Atkins Jr.
• Re: [css3-flexbox] flex-grow initial value should be 0px Tab Atkins Jr.
• Re: [css3-flexbox] flex-grow initial value should be 0px Ojan Vafai
• Re: [css3-transforms] ... to-animation Dirk Schulze
• Re: [css3-transforms] <transform-list> Dirk Schulze
• Re: [css3-marquee][css3-gcpm][css3-box] rethinking overflow, overflow-x, overflow-y and overflow-style Florian Rivoal
• Re: [css3-marquee][css3-gcpm][css3-box] rethinking overflow, overflow-x, overflow-y and overflow-style Florian Rivoal
• Re: [css3-transforms] ... to-animation Dr. Olaf Hoffmann
• Re: [css3-gcpm] bookmark-label: keyword definitions and whitespace processing Brad Kemper

Sunday, 3 June 2012

• Re: [css3-transforms] <transform-list> Dr. Olaf Hoffmann
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Anne van Kesteren
• Re: [css3-gcpm] bookmark-label: keyword definitions and whitespace processing Simon Sapin
• Re: [css3-gcpm] bookmark-label: keyword definitions and whitespace processing Brad Kemper

Saturday, 2 June 2012

• Re: [css-variables] Using $foo as the syntax for variables Brad Kemper
• Re: [css-variables] Variables in @page Markus Ernst
• Re: [css3-marquee][css3-gcpm][css3-box] rethinking overflow, overflow-x, overflow-y and overflow-style Brad Kemper

Friday, 1 June 2012

• Re: [css3-fonts] truetype collection MURATA Makoto
• Re: [css-variables] Examples Tab Atkins Jr.
• Re: [css3-transforms] about ‘animate’ and 'animateTransform' Dirk Schulze
• Re: [css3-flexbox] "flex-basis: auto" means completely different things as specified value vs. computed value Daniel Holbert
• [css3-flexbox] "flex-basis: auto" means completely different things as specified value vs. computed value Daniel Holbert
• Re: [css3-marquee][css3-gcpm][css3-box] rethinking overflow, overflow-x, overflow-y and overflow-style Alan Stearns
• Re: [css-variables] Variables in @page Tab Atkins Jr.
• Re: [css-variables] Variables in @page François REMY
• Re: [css-variables] Variables in @page Tab Atkins Jr.
• Re: [css-variables] Variables in @page François REMY
• Re: [css3-transforms] Effect of CSS transforms on scrollable areas Rik Cabanier
• Re: [css-variables] Variables in @page Tab Atkins Jr.
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Tab Atkins Jr.
• Re: [css-background] Order of properties in background shorthand L. David Baron
• Re: [css-background] Order of properties in background shorthand tony chang
• Re: [css-background] Order of properties in background shorthand Boris Zbarsky
• Re: [css-background] Order of properties in background shorthand Sebastian Zartner
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Ian Hickson
• Re: [css-background] Order of properties in background shorthand Boris Zbarsky
• Re: [css3-writing-modes] before/after terminology alternative? MURAKAMI Shinyu
• Re: [css-variables] Variables in @page Simon Sapin
• Re: [css3-exclusions] ordering exclusions by z-order Robert O'Callahan
• Re: [css-variables] Variables in @page (was: CSS Variables are a NEW kind of variable) Sebastian Zartner
• Re: [css-background] Order of properties in background shorthand Sebastian Zartner
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Anne van Kesteren
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Anne van Kesteren
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Simon Pieters
• Re: CfC: publish FPWD of Fullscreen spec; deadline May 24 Anne van Kesteren
• Re: [css3-regions][cssom] NamedFlowCollection as a live collection? Anne van Kesteren
• Re: [css3-regions][cssom] NamedFlowCollection as a live collection? Mihnea-Vlad Ovidenie
• Re: [css-background] Order of properties in background shorthand Boris Zbarsky
• Re: [css-background] Order of properties in background shorthand Sebastian Zartner
• RE: -webkit-background-clip:text and -webkit-text-fill-color? Sylvain Galineau
• RE: -webkit-background-clip:text and -webkit-text-fill-color? Brian Manthos

Last message date: Saturday, 30 June 2012 22:24:04 UTC