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

Thursday, 30 June 2011

• Re: css3-fonts: should not dictate usage policy with respect to origin John Daggett
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: [css3-speech] voice-family Brad Kemper
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Cameron McCormack
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Tab Atkins
• Re: css3-fonts: should not dictate usage policy with respect to origin Brad Kemper
• Re: [css3-speech] voice-family fantasai
• Re: css3-fonts: should not dictate usage policy with respect to origin John Daggett
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Thomas Phinney
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Boris Zbarsky
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: [css3-speech] voice-family Andrew Thompson
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Daggett
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Tab Atkins Jr.
• Re: css3-fonts: should not dictate usage policy with respect to origin Boris Zbarsky
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Levantovsky, Vladimir
• Re: [css3-speech] Test suite Andrew Thompson
• Re: css3-fonts: should not dictate usage policy with respect to origin John Daggett
• Re: [css3-speech] Test suite fantasai
• [css3-speech] Test suite Simon Fraser
• Re: [css3-speech] voice-duration fantasai
• [css3-lists] list-item and counter rendering fantasai
• [css3-speech] Editorial Comments fantasai
• [css3-speech] voice-duration fantasai
• [css3-speech] voice-pitch fantasai
• [css3-speech] voice-family fantasai
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Alex Danilo
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Robert O'Callahan
• [css3-speech] cue <uri> load fails fantasai
• [css3-speech] cue volume fantasai
• [css3-speech] voice-balance and azimuth fantasai
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams

Wednesday, 29 June 2011

• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• [css3-speech] four properties with a nonsense "Percentages" entry L. David Baron
• voice-volume, absolute and relative volume units [css3-speech][css3-values][CSS-ISSUE-184] L. David Baron
• Re: css3-fonts: should not dictate usage policy with respect to origin Bjoern Hoehrmann
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Cameron McCormack
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Jeremie Patonnier
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Jonathan Kew
• Re: css3-fonts: should not dictate usage policy with respect to origin Bjoern Hoehrmann
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin L. David Baron
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Daggett
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: [css3-writing-modes] The writing-mode property: existing implementations and naming Alan Gresley
• RE: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Levantovsky, Vladimir
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: [css3-speech] :media-overlay-active Daniel Weck
• Re: [CSS] Concept of flows. Andrew Fedoniouk
• Re: css3-fonts: should not dictate usage policy with respect to origin Jonathan Kew
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Bjoern Hoehrmann
• RE: [css3-speech] :media-overlay-active Sylvain Galineau
• RE: [css3-writing-modes] The writing-mode property: existing implementations and naming Sylvain Galineau
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Adam Twardoch (List)
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Erik Dahlstrom
• Re: css3-fonts: should not dictate usage policy with respect to origin Bjoern Hoehrmann
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Mikko Rantalainen
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Robert O'Callahan
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Erik Dahlstrom
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Robert O'Callahan
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Erik Dahlstrom
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Robert O'Callahan
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Ryosuke Niwa
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Ryosuke Niwa
• Re: css3-fonts: should not dictate usage policy with respect to origin Liam R E Quin
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Robert O'Callahan
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Ryosuke Niwa
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Robert O'Callahan
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: [css3-images] List of changes since last WD Tab Atkins Jr.
• [css3-images] List of changes since last WD Tab Atkins Jr.
• Re: region intrinsic size and aspect ratio Vincent Hardy
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Robert O'Callahan
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: region intrinsic size and aspect ratio Alex Mogilevsky
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Ryosuke Niwa

Tuesday, 28 June 2011

• Re: [CSSOM] does CaretPosition need a "before/after" hint? Robert O'Callahan
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• [css3-images] List of changes since last WD Tab Atkins Jr.
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Cameron McCormack
• Re: [OpenType] SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Robert O'Callahan
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Robert O'Callahan
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Robert O'Callahan
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: [css3-images] image-rendering:optimizeSpeed should be like crisp-edges Tab Atkins Jr.
• Re: [css3-writing-modes] The writing-mode property: existing implementations and naming fantasai
• [css3-images] image-rendering:optimizeSpeed should be like crisp-edges L. David Baron
• Re: region intrinsic size and aspect ratio Brad Kemper
• RE: [OpenType] SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Levantovsky, Vladimir
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] John Hudson
• RE: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Levantovsky, Vladimir
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] John Hudson
• Re: [css3-speech] :media-overlay-active Daniel Weck
• Re: [css3-ui] text-overflow: ellipsis and :hover Tab Atkins Jr.
• Re: [CSS3-color] [css3-images] [css3-transitions] transparent transitions Tab Atkins Jr.
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: [css3-speech] :media-overlay-active Tab Atkins Jr.
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Boris Zbarsky
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Tab Atkins
• Re: css3-fonts: should not dictate usage policy with respect to origin Christine Bloomquist
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Simon Montagu
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: region intrinsic size and aspect ratio Vincent Hardy
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• [CSS] Concept of flows. Andrew Fedoniouk
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: [CSS3-color] [css3-images] [css3-transitions] transparent transitions Alan Gresley
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Cameron McCormack
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Robert O'Callahan
• Re: css3-fonts: should not dictate usage policy with respect to origin Boris Zbarsky
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: [CSS3-color] [css3-images] [css3-transitions] transparent transitions Alan Gresley
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams

Monday, 27 June 2011

• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: [css3-writing-modes] The writing-mode property: existing implementations and naming fantasai
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: [CSS3-color] [css3-images] [css3-transitions] transparent transitions Chris Lilley
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: [css3-speech] :media-overlay-active Daniel Weck
• RE: [CSS3-color] [css3-images] [css3-transitions] transparent transitions Brian Manthos
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Adam Twardoch (List)
• RE: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Levantovsky, Vladimir
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Adam Twardoch (List)
• RE: [css3-writing-modes] The writing-mode property: existing implementations and naming Sylvain Galineau
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Adam Twardoch (List)
• Re: [CSS3-color] [css3-images] [css3-transitions] transparent transitions L. David Baron
• Re: [css3-writing-modes] The writing-mode property: existing implementations and naming fantasai
• Re: [CSS3-color] [css3-images] [css3-transitions] transparent transitions fantasai
• RE: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Levantovsky, Vladimir
• Re: [css3-content] quotes issues inc. i18n & French quotes Oli Studholme
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Bram Pitoyo
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Chris Lilley
• Re: Specification for text-overflow? Philippe Wittenbergh
• Specification for text-overflow? Nathan D. Ryan
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Bram Pitoyo
• RE: [css3-writing-modes] The writing-mode property: existing implementations and naming Sylvain Galineau

Sunday, 26 June 2011

• Re: [css3-ui] text-overflow: ellipsis and :hover Robert O'Callahan
• RE: [css3-image] gradients from color to full alpha transparency (was Re: [CSS3] support for linear-gradients & radial-gradients) Brian Manthos
• RE: [css3-image] gradients from color to full alpha transparency (was Re: [CSS3] support for linear-gradients & radial-gradients) Brian Manthos
• Re: SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Thomas Phinney
• [css3-image] gradients from color to full alpha transparency (was Re: [CSS3] support for linear-gradients & radial-gradients) Alan Gresley
• SVG Fonts inside of OpenType fonts? [Cross-post from www-font@w3.org] Adam Twardoch (List)
• DOM 3 Events LC #2 Daniel Glazman
• RE: [css3-writing-modes] The writing-mode property: existing implementations and naming Koji Ishii
• [css3-ui] text-overflow: ellipsis and :hover Philippe Wittenbergh

Saturday, 25 June 2011

• Consistency between CSS OM and html Daniel Glazman
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Robert O'Callahan
• RE: region intrinsic size and aspect ratio Alex Mogilevsky
• RE: [css3-regions] region intrinsic size and aspect ratio Alex Mogilevsky
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams

Friday, 24 June 2011

• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• RE: region intrinsic size and aspect ratio Alex Mogilevsky
• RE: [css3-regions] region intrinsic size and aspect ratio Stephen Zilles
• Re: region intrinsic size and aspect ratio Edward O'Connor
• [css3-regions] region intrinsic size and aspect ratio Alex Mogilevsky
• Re: [CSS3] support for linear-gradients & radial-gradients Alan Gresley
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Ryosuke Niwa
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Robert O'Callahan

Thursday, 23 June 2011

• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: [css3-writing-modes] The writing-mode property: existing implementations and naming Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Liam R E Quin
• Re: [css3-writing-modes] The writing-mode property: existing implementations and naming fantasai
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Ryosuke Niwa
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Ojan Vafai
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Ryosuke Niwa
• Re: [css3-regions] New CSS Regions editor draft Vincent Hardy
• Re: [CSSOM] does CaretPosition need a "before/after" hint? Anne van Kesteren
• Re: [cssom] comments on MediaQueryList L. David Baron
• RE: css3-fonts: should not dictate usage policy with respect to origin Liam R E Quin
• Re: [CSSOM] CaretPosition Anne van Kesteren
• Re: [cssom] comments on MediaQueryList L. David Baron
• Re: [cssom] comments on MediaQueryList Ian Hickson
• Re: [cssom] comments on MediaQueryList Anne van Kesteren
• [css-animation~transitions][css-transforms] combining specs (was Re: [CSSWG] Minutes) Alan Gresley

Wednesday, 22 June 2011

• [css3-writing-modes] The writing-mode property: existing implementations and naming Sylvain Galineau
• RE: Unicode normalization in CSS [css3-namespace] Phillips, Addison
• Re: [css3] Suggestion: Selector variables or “synonyms” Jens O. Meiert
• Re: Unicode normalization in CSS [css3-namespace] fantasai
• Re: [css3-multicol] Intrinsic Widths of Multi-column elements (Take I) L. David Baron
• RE: [css3-regions] New CSS Regions editor draft Alex Mogilevsky
• [CSSWG] Minutes and Resolutions 2011-06-22 fantasai
• RE: [css3-lists] Published as WD! Håkon Wium Lie
• Re: [css3-lists] Published as WD! Håkon Wium Lie
• Re: Unicode normalization in CSS Anne van Kesteren
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: css3-fonts: should not dictate usage policy with respect to origin Florian Rivoal
• Re: css3-fonts: should not dictate usage policy with respect to origin John Daggett
• Re: css3-fonts: should not dictate usage policy with respect to origin John Daggett
• Re: Unicode normalization in CSS Martin J. Dürst

Tuesday, 21 June 2011

• Re: New design for W3’s CSS website/blog Alan Gresley
• [css3] is "default" a reserved keyword (RE: [css21] is 'initial' a valid counter name?) Alex Mogilevsky
• RE: Unicode normalization in CSS Phillips, Addison
• Re: Unicode normalization in CSS L. David Baron
• Re: New design for W3’s CSS website/blog Mark Ayers
• RE: Unicode normalization in CSS Phillips, Addison
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: New design for W3’s CSS website/blog L. David Baron
• Re: New design for W3’s CSS website/blog Tab Atkins Jr.
• Re: [css3-content] typo: «» became +; Tab Atkins Jr.
• Re: css3-fonts: should not dictate usage policy with respect to origin David Singer
• Re: css3-fonts: should not dictate usage policy with respect to origin Garrick Van Buren
• Re: New design for W3’s CSS website/blog Alan Gresley
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: [css3-content] typo: «» became +; Oli Studholme
• Re: Unicode normalization in CSS Daniel Glazman
• Re: Unicode normalization in CSS Martin J. Dürst
• Re: css3-fonts: should not dictate usage policy with respect to origin Florian Rivoal
• Re: New design for W3’s CSS website/blog Oli Studholme
• [css3-content] typo: «» became +; Oli Studholme
• Re: css3-fonts: <integer>, <length>, <number>, <percentage>, <string> used but not defined John Daggett
• Re: css3-fonts: inconsistent function name ornament() vs ornaments() John Daggett
• Re: css3-fonts: should not dictate usage policy with respect to origin Robert O'Callahan
• RE: [css3-lists] Published as WD! Belov, Charles

Monday, 20 June 2011

• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Tab Atkins
• Re: css3-fonts: should not dictate usage policy with respect to origin Jonathan Kew
• Re: css3-fonts: should not dictate usage policy with respect to origin Jonathan Kew
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: [css3-lists] Published as WD! Tab Atkins Jr.
• Re: [css3 box, cssom] flexibility in box-sizing and offset* properties Ojan Vafai
• Re: css3-fonts: should not dictate usage policy with respect to origin Jonathan Kew
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Jonathan Kew
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: css3-fonts: should not dictate usage policy with respect to origin Jonathan Kew
• Re: css3-fonts: should not dictate usage policy with respect to origin Tab Atkins
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: [CSS4 Selectors] :matches naming bikeshed fantasai
• Re: css template module (was Re: css3-fonts: <integer>, <length>, <number>, <percentage>, <string> used but not defined) fantasai
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• RE: css3-fonts: should not dictate usage policy with respect to origin Sylvain Galineau
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Robert O'Callahan
• Re: [CSS4 Selectors] :matches naming bikeshed Brian Kardell
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• RE: css3-fonts: should not dictate usage policy with respect to origin Levantovsky, Vladimir
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: Unicode normalization in CSS Anne van Kesteren
• Re: css3-fonts: should not dictate usage policy with respect to origin Florian Rivoal
• Re: css3-fonts: should not dictate usage policy with respect to origin Florian Rivoal
• Re: css3-fonts: should not dictate usage policy with respect to origin Florian Rivoal
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Florian Rivoal
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Florian Rivoal
• Re: css3-fonts: should not dictate usage policy with respect to origin Martin J. Dürst

Sunday, 19 June 2011

• Re: [CSS4 Selectors] :matches naming bikeshed Brian Kardell
• [css3-flexbox] status and issues Alex Mogilevsky
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Christoph Päper
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: Unicode normalization in CSS Phillips, Addison
• css template module (was Re: css3-fonts: <integer>, <length>, <number>, <percentage>, <string> used but not defined) John Daggett
• Re: [CSS4 Selectors] :matches naming bikeshed fantasai
• Re: css3-fonts: <integer>, <length>, <number>, <percentage>, <string> used but not defined fantasai
• Re: Unicode normalization in CSS Anne van Kesteren
• Re: [css3-lists] Published as WD! Håkon Wium Lie
• Re: Behaviour of getComputedStyle with box-sizing: border-box Anne van Kesteren
• Re: css3-fonts: should not dictate usage policy with respect to origin Christoph Päper

Thursday, 16 June 2011

• Re: [css3 box, cssom] flexibility in box-sizing and offset* properties Aron Allen

Sunday, 19 June 2011

• Re: css3-fonts: should not dictate usage policy with respect to origin Håkon Wium Lie

Saturday, 18 June 2011

• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Ben Weiner
• Re: [CSS4 Selectors] :matches naming bikeshed Brian Kardell
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Jonathan Kew
• Re: css3-fonts: should not dictate usage policy with respect to origin Ben Weiner
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Tab Atkins Jr.
• Re: [CSS4 Selectors] :matches naming bikeshed fantasai
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: [css3-images] Summary of recent gradient issues Alan Gresley
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams

Friday, 17 June 2011

• Re: [CSS4 Selectors] :matches naming bikeshed Robert O'Callahan
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Tab Atkins Jr.
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• Re: css3-fonts: should not dictate usage policy with respect to origin John Hudson
• Re: css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• css3-fonts: <integer>, <length>, <number>, <percentage>, <string> used but not defined Glenn Adams
• css3-fonts: should not dictate usage policy with respect to origin Glenn Adams
• css3-fonts: inconsistent function name ornament() vs ornaments() Glenn Adams
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• Re: [CSS4 Selectors] :matches naming bikeshed Brian Kardell
• Re: [css3-images] Summary of recent gradient issues Brad Kemper
• Re: [css3-images] Summary of recent gradient issues divya manian
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• Re: [css3-images] Summary of recent gradient issues divya manian
• Re: [CSS4 Selectors] :matches naming bikeshed Boris Zbarsky
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• Re: [css3-images] Summary of recent gradient issues Simon Fraser
• Re: [CSS4 Selectors] :matches naming bikeshed Ojan Vafai
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• Re: [CSS4 Selectors] :matches naming bikeshed Boris Zbarsky
• Re: [css3-images] Summary of recent gradient issues Brad Kemper
• Re: [CSS4 Selectors] :matches naming bikeshed Brian Kardell
• Re: CSS Regions / Exclusions Daniel Glazman
• Re: [css3-images] Summary of recent gradient issues divya manian
• CSS Regions / Exclusions Daniel Glazman
• Re: [css3-images] Summary of recent gradient issues Alan Gresley
• Re: [css3-images] Summary of recent gradient issues Florian Rivoal
• Re: [css3-images] Summary of recent gradient issues Alan Gresley
• Re: [CSS4 Selectors] :matches naming bikeshed fantasai
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• Re: [css3-images] Summary of recent gradient issues Brad Kemper
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• Re: [css3-images] Summary of recent gradient issues Brad Kemper
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• Re: [css3-images] Summary of recent gradient issues Eli Morris-Heft

Thursday, 16 June 2011

• [css3-selectors] feature request Tom
• [CSS4 Selectors] :matches naming bikeshed Ojan Vafai
• Re: [css3-images] Summary of recent gradient issues Simon Fraser
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• Re: [css3-images] Summary of recent gradient issues Simon Fraser
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• Re: [css3-images] Summary of recent gradient issues Brad Kemper
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• Re: [css3-images] Summary of recent gradient issues fantasai
• Re: [css3-images] Summary of recent gradient issues fantasai
• Re: [css21] is 'initial' a valid counter name? Tab Atkins Jr.
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• RE: [css21] is 'initial' a valid counter name? Alex Mogilevsky
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• Re: [css3-lists] list-style-position: outside Tab Atkins Jr.
• RE: [CSSWG] Minutes and Resolutions Kyoto F2F Fri: Transitions, IVS, CSS3 Text, Floats and Exclusions, Regions, Pagination Arron Eicholz
• Re: [css3-images] Summary of recent gradient issues Eli Morris-Heft
• Re: [css3-lists] list-style-position: outside Øyvind Stenhaug
• Re: [css3-images] Summary of recent gradient issues Alan Gresley
• Re: [css3-images] Summary of recent gradient issues Eli Morris-Heft
• Re: [css3-speech] tables and speak-header Daniel Weck
• Re: [css3-images] Summary of recent gradient issues Alan Gresley
• Re: Behaviour of getComputedStyle with box-sizing: border-box Boris Zbarsky
• Re: [CSSWG] Minutes and Resolutions Kyoto F2F Fri: Transitions, IVS, CSS3 Text, Floats and Exclusions, Regions, Pagination Masataka Yakura
• Behaviour of getComputedStyle with box-sizing: border-box Shane Stephens
• Re: [css3-speech] tables and speak-header Andrew Thompson
• Re: [css21] is 'initial' a valid counter name? Daniel Glazman

Wednesday, 15 June 2011

• Re: [css21] is 'initial' a valid counter name? Tab Atkins Jr.
• [css21] is 'initial' a valid counter name? Alex Mogilevsky
• [CSSWG] Minutes and Resolutions 2011-06-15 fantasai
• [CSSWG] Minutes: Kyoto Forum on the Future of CSS for Asian Text Layout fantasai
• Re: comment on DOM 3 Events LC #2 on WebApps WG's request Arthur Barstow
• Re: [css3-conditional] feature queries Boris Zbarsky
• Re: [css3-lists] list-style-position: outside Tab Atkins Jr.
• Re: [css3-conditional] feature queries Daniel Glazman
• comment on DOM 3 Events LC #2 on WebApps WG's request Daniel Glazman
• Re: [css3-conditional] feature queries Tab Atkins Jr.
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• [css3-lists] list-style-position: outside Øyvind Stenhaug
• RE: [CSSWG] Minutes and Resolutions Kyoto F2F Fri: Transitions, IVS, CSS3 Text, Floats and Exclusions, Regions, Pagination Brian Kardell
• Re: [css3-images] Summary of recent gradient issues Eli Morris-Heft
• Re: [css3-images] linear-gradient keywords and angles are opposite fantasai
• Re: [css3-speech] tables and speak-header Daniel Weck
• Re: [css3-images] Summary of recent gradient issues Alan Gresley
• Re: [css3-conditional] feature queries Alan Gresley
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• Re: [css3-images] Summary of recent gradient issues Brad Kemper
• Re: [css3-conditional] feature queries Boris Zbarsky
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-conditional] feature queries Alan Gresley
• Re: [css3-conditional] feature queries Alan Gresley
• [css3-speech] tables and speak-header Andrew Thompson
• Re: [css3-images] Summary of recent gradient issues Alan Gresley
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• Re: [css3-flexbox] other misc typos in latest flexbox editor's draft Tab Atkins Jr.
• Re: [css3-flexbox] error in flexbox editor's draft on "margin/padding: flex()" Tab Atkins Jr.
• RE: error in CSS1spec Sylvain Galineau
• Re: [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• Re: error in CSS1spec Tab Atkins Jr.

Tuesday, 14 June 2011

• Re: [css3-images] Summary of recent gradient issues Simon Fraser
• RE: [css3-images] Summary of recent gradient issues Brian Manthos
• Re: error in CSS1spec Linss, Peter
• [css3-flexbox] other misc typos in latest flexbox editor's draft Daniel Holbert
• Re: [css3-images] Summary of recent gradient issues Philippe Wittenbergh
• [css3-flexbox] error in flexbox editor's draft on "margin/padding: flex()" Daniel Holbert
• [css3-images] Summary of recent gradient issues Tab Atkins Jr.
• Re: error in CSS1spec Tab Atkins Jr.
• error in CSS1spec Alex Mogilevsky
• Re: [css3-lists] Recent changes, and request for new WD Tab Atkins Jr.
• Re: [css3-lists] Recent changes, and request for new WD L. David Baron
• Re: [css3-lists] Recent changes, and request for new WD Tab Atkins Jr.
• Re: [css3-lists] Recent changes, and request for new WD L. David Baron
• [css3-lists] Recent changes, and request for new WD Tab Atkins Jr.
• Re: [css3-speech] reading list-style markers fantasai
• Re: [css3-lists] Alignment of list markers Tab Atkins Jr.
• Re: [css3-conditional] feature queries Daniel Glazman
• Re: [css3-conditional] feature queries Tab Atkins Jr.
• Re: [CSS21] questions about Lex regexes used to define tokens Simon Montagu
• Re: [css3-speech] reading list-style markers Daniel Weck
• Re: [CSS21] questions about Lex regexes used to define tokens Mikko Rantalainen
• Re: [css3-speech] reading list-style markers fantasai
• Re: [css3-lists] Alignment of list markers fantasai
• Re: [css3-conditional] feature queries Alan Gresley

Friday, 10 June 2011

• Re: [css3-images] linear-gradient keywords and angles are opposite Sarah Forst

Tuesday, 14 June 2011

• Re: [css3-conditional] feature queries L. David Baron
• [css3-conditional] New Editor's Draft: Conditional Rules Module L. David Baron
• Conformance definitions in modules L. David Baron
• Re: [css3-speech] reading list-style markers Daniel Weck

Friday, 10 June 2011

• [css3-multicol] Pseudo-algorithm column-width expressions Rich Dougherty

Monday, 13 June 2011

• Re: [css3-lists] Alignment of list markers Tab Atkins Jr.
• Re: [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia Christoph Päper
• Re: [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia Vincent Hardy
• [CSS4 Selectors] :not,:never and limited ancestor Allan Sandfeld Jensen
• Re: [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia Tab Atkins Jr.
• RE: [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia John Jansen
• Implementation Reports for CSS2.1 John Jansen

Sunday, 12 June 2011

• Re: [css3-lists] Published as WD! Tab Atkins Jr.

Saturday, 11 June 2011

• Re: [css3-lists] Published as WD! Brad Kemper
• Re: [css3-lists] Alignment of list markers Brad Kemper
• Re: [CSS4 Selectors] :has() (was Re: [CSSWG] ... F2F Kyoto] Brad Kemper
• Re: [CSS4 Selectors] :has() (was Re: [CSSWG] ... F2F Kyoto] Brian Kardell
• [CSS4 Selectors] :has() (was Re: [CSSWG] ... F2F Kyoto] Alan Gresley
• RE: [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia Brian Kardell
• Re: [CSS4 Selectors] :matches() :not() comma-separated list (was Re: [CSSWG] ... F2F Kyoto]) Eli Morris-Heft
• [CSS4 Selectors] :matches() :not() comma-separated list (was Re: [CSSWG] ... F2F Kyoto]) Alan Gresley
• RE: [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia John Jansen

Friday, 10 June 2011

• Re: [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia Vincent Hardy
• Re: [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia Tab Atkins Jr.
• Re: [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia Daniel Glazman
• RE: [CSS21] questions about Lex regexes used to define tokens Jack Smiley
• Re: [css3-images] linear-gradient keywords and angles are opposite Tab Atkins Jr.
• Re: [CSS21] questions about Lex regexes used to define tokens Joshua Cranmer
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia fantasai
• [CSS21] questions about Lex regexes used to define tokens Jack Smiley
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-images] linear-gradient keywords and angles are opposite Simon Fraser
• [CSSWG] Minutes and Resolutions Kyoto F2F Fri: Transitions, IVS, CSS3 Text, Floats and Exclusions, Regions, Pagination fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite Simon Fraser
• [CSSWG] Minutes and Resolutions Kyoto F2F Thurs: Vertical Text, Bidi, Line Grid, Unencoded Characters fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Florian Rivoal
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-lists] Alignment of list markers Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Simon Fraser
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Rik Cabanier
• Re: [css3-images] linear-gradient keywords and angles are opposite Florian Rivoal
• Re: [css3-images] linear-gradient keywords and angles are opposite Florian Rivoal
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-flexbox] getting multiline flexbox back into the spec fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Rik Cabanier
• Re: [css3-speech] :media-overlay-active fantasai
• Re: [css3-lists] Alignment of list markers fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Florian Rivoal
• Re: [css3-images] linear-gradient keywords and angles are opposite Florian Rivoal
• Re: [css3-images] linear-gradient keywords and angles are opposite Florian Rivoal
• Re: [css3-images] linear-gradient keywords and angles are opposite Florian Rivoal
• Re: [css3-images] linear-gradient keywords and angles are opposite Florian Rivoal
• Re: [css3-images] linear-gradient keywords and angles are opposite fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite Eric A. Meyer
• Re: [css3-images] linear-gradient keywords and angles are opposite Philippe Wittenbergh
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-images] linear-gradient keywords and angles are opposite Simon Fraser

Thursday, 9 June 2011

• Re: CSS 2.1, CSS Color Module Level 3 and MathML for CSS Profile Linss, Peter
• Re: [css3-images] linear-gradient keywords and angles are opposite Tab Atkins Jr.
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-flexbox] what's the computed value of "width: flex(...)" in a non-flexbox context? Tab Atkins Jr.
• Re: [css3-flexbox] what's the computed value of "width: flex(...)" in a non-flexbox context? Tab Atkins Jr.
• Re: [css3-flexbox] what's the computed value of "width: flex(...)" in a non-flexbox context? L. David Baron
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• RE: [css3-flexbox] what's the computed value of "width: flex(...)" in a non-flexbox context? Alex Mogilevsky
• Re: [css3-flexbox] what's the computed value of "width: flex(...)" in a non-flexbox context? Tab Atkins Jr.
• Re: [css3-images] linear-gradient keywords and angles are opposite Alan Gresley
• RE: [css3-flexbox] what's the computed value of "width: flex(...)" in a non-flexbox context? Alex Mogilevsky
• [css3-regions] New WD CSS Regions Bert Bos
• Re: [css3-lists] Published as WD! Tab Atkins Jr.
• Re: [css3-lists] inline list items Tab Atkins Jr.
• Re: [css3-flexbox] getting multiline flexbox back into the spec Tab Atkins Jr.
• Re: [css3-flexbox] what's the computed value of "width: flex(...)" in a non-flexbox context? Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• Re: [css3-lists] Alignment of list markers Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Boris Zbarsky
• Re: HOW DO I GET OUT? Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• HOW DO I GET OUT? Asaf Chertkoff
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• Re: [css3-lists] Alignment of list markers Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Tab Atkins Jr.
• Re: Comments on CSS Exclusions Vincent Hardy
• Re: CSS 2.1, CSS Color Module Level 3 and MathML for CSS Profile Boris Zbarsky
• Re: CSS 2.1, CSS Color Module Level 3 and MathML for CSS Profile Chris Lilley
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• RE: CSS 2.1, CSS Color Module Level 3 and MathML for CSS Profile John Jansen
• Re: [css3-images] linear-gradient keywords and angles are opposite Alan Gresley
• Comments on CSS Exclusions Daniel Glazman
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-lists] Alignment of list markers Tab Atkins Jr.
• Re: [css3-lists] Alignment of list markers Tab Atkins Jr.
• Re: [css3-speech] :media-overlay-active Tab Atkins Jr.
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• Re: [css3-images] linear-gradient keywords and angles are opposite Alan Gresley
• Re: [css3-speech] :media-overlay-active Daniel Weck
• Re: [css3-images] linear-gradient keywords and angles are opposite fantasai
• [css3-text] [css3-linebox] typesetting defaults, auto values, and i18n fantasai
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• Re: Inline elements should be affected by 2D Transforms L. David Baron
• [css3-speech] :media-overlay-active fantasai
• Re: Inline elements should be affected by 2D Transforms fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite fantasai
• Re: [css3-images] linear-gradient keywords and angles are opposite fantasai
• [css3-lists] inline list items fantasai
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• Re: [css3-images] linear-gradient keywords and angles are opposite Philippe Wittenbergh
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper

Wednesday, 8 June 2011

• Re: [css3-images] linear-gradient keywords and angles are opposite Philippe Wittenbergh
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• RE: [CSS2.1] Column property limitations Jack Smiley
• Re: [css3-flexbox] getting multiline flexbox back into the spec Alan Gresley
• Re: [css-device-adaptation] Issues from Kyoto F2F meeting Rune Lillesveen
• Re: [css-device-adaptation] Issues from Kyoto F2F meeting Rune Lillesveen
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• [css3-flexbox] what's the computed value of "width: flex(...)" in a non-flexbox context? Daniel Holbert
• Re: [CSS2.1] Column property limitations Boris Zbarsky
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• RE: [css3-speech] reading list-style markers Belov, Charles
• Re: Inline elements should be affected by 2D Transforms Brad Kemper
• [CSS2.1] Column property limitations Jack Smiley
• RE: [css3-images] linear-gradient keywords and angles are opposite Sylvain Galineau
• Re: [css3-flexbox] getting multiline flexbox back into the spec Andrew Fedoniouk
• Re: [css3-lists] Alignment of list markers Brad Kemper
• Re: CSS 2.1, CSS Color Module Level 3 and MathML for CSS Profile Daniel Glazman
• Re: CSS 2.1, CSS Color Module Level 3 and MathML for CSS Profile Anthony Ricaud
• Re: [css3-lists] Alignment of list markers fantasai
• Re: "CSS Standard Boasts Unprecedented Interoperability": a different - much more nuanced - opinion Daniel Glazman
• Re: [css3-flexbox] getting multiline flexbox back into the spec Alan Gresley
• Thanks for Joining My Referral Network Lorenzo De Tomasi
• RE: [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Re: [css3-images] linear-gradient keywords and angles are opposite Alan Gresley
• Re: [css3-flexbox] getting multiline flexbox back into the spec Alan Gresley
• Re: [css3-images] linear-gradient keywords and angles are opposite Tab Atkins Jr.
• Re: [css3-lists] Alignment of list markers Tab Atkins Jr.
• Re: [css3-speech] reading list-style markers fantasai
• Re: [css3-flexbox] getting multiline flexbox back into the spec Andrew Fedoniouk
• Re: [css3-speech] reading list-style markers Daniel Weck
• Re: Inline elements should be affected by 2D Transforms fantasai
• Re: Inline elements should be affected by 2D Transforms fantasai
• Re: [css3-flexbox] getting multiline flexbox back into the spec fantasai
• Re: [css3-flexbox] getting multiline flexbox back into the spec Andrew Fedoniouk
• Re: [css3-speech] reading list-style markers fantasai
• Re: [css-device-adaptation] Issues from Kyoto F2F meeting fantasai
• RE: [css3-speech] reading list-style markers Belov, Charles

Tuesday, 7 June 2011

• Re: Inline elements should be affected by 2D Transforms Shane Stephens
• Re: "CSS Standard Boasts Unprecedented Interoperability": a different - much more nuanced - opinion Ian Jacobs
• "CSS Standard Boasts Unprecedented Interoperability": a different - much more nuanced - opinion Gérard Talbot
• Re: Inline elements should be affected by 2D Transforms Brian Blakely
• Re: [css3-speech] reading list-style markers Daniel Weck
• Re: [css3-images] linear-gradient keywords and angles are opposite Brad Kemper
• RE: [css3-speech] reading list-style markers Belov, Charles
• [css3-images] linear-gradient keywords and angles are opposite Brian Manthos
• Are you taking on new clients? Lorenzo De Tomasi
• Re: [css-device-adaptation] Issues from Kyoto F2F meeting Brad Kemper
• CSS 2.1, CSS Color Module Level 3 and MathML for CSS Profile Daniel Glazman
• Re: [css3-lists] Alignment of list markers Brad Kemper
• Re: [css3-flexbox] getting multiline flexbox back into the spec Alan Gresley
• Re: [css3-flexbox] getting multiline flexbox back into the spec Eric A. Meyer
• Re: [css3-speech] reading list-style markers Daniel Weck
• Re: [css3-flexbox] getting multiline flexbox back into the spec Alan Gresley
• Re: [css3-speech] voice family prohibition of spaces Daniel Weck
• [css-device-adaptation] Issues from Kyoto F2F meeting Rune Lillesveen
• Re: [css3-speech] reading list-style markers Daniel Weck
• Re: [css3-speech] voice family prohibition of spaces Daniel Weck
• [css3-lists] Alignment of list markers fantasai
• Re: [css3-flexbox] getting multiline flexbox back into the spec Alan Gresley
• Re: [css3-flexbox] getting multiline flexbox back into the spec Andrew Fedoniouk
• Re: [css3-flexbox] getting multiline flexbox back into the spec fantasai
• Re: [css3-speech] reading list-style markers fantasai
• Re: [css3-speech] voice family prohibition of spaces fantasai
• Re: [css3-regions] region name - why is it string, not indent? Vincent Hardy
• [css3-regions] region name - why is it string, not indent? Alex Mogilevsky

Monday, 6 June 2011

• Re: [css3-speech] reading list-style markers Daniel Weck
• RE: [css3-speech] reading list-style markers Belov, Charles
• Re: [css3-lists] [css3-speech] Purpose of the module Daniel Weck
• Re: [css3-speech] reading list-style markers Daniel Weck
• RE: [css3-flexbox] getting multiline flexbox back into the spec Alex Mogilevsky
• Re: [css3-speech] reading list-style markers Daniel Weck
• Re: [css3-speech] reading list-style markers Daniel Weck
• RE: [css3-flexbox] getting multiline flexbox back into the spec Eric A. Meyer
• RE: [css3-flexbox] getting multiline flexbox back into the spec Alex Mogilevsky
• Re: [css3-speech] voice family prohibition of spaces Daniel Weck
• Re: [css3-speech] voice family prohibition of spaces Daniel Weck
• RE: [css3-flexbox] getting multiline flexbox back into the spec Alex Mogilevsky
• Re: [css3-flexbox] getting multiline flexbox back into the spec Andrew Fedoniouk
• Re: [css3-lists] Published as WD! Brad Kemper
• [css3-fonts][css3-text] text-transform, font-variant-numeric, OT case Christoph Päper
• Re: [css3-flexbox] getting multiline flexbox back into the spec fantasai
• Re: [css3-flexbox] getting multiline flexbox back into the spec Andrew Fedoniouk
• Re: [css-animation] transform origin rotation chaos (was an...) Alan Gresley
• Re: [css3-lists] Published as WD! fantasai
• Re: [css3-lists] Published as WD! fantasai
• Re: [css3-flexbox] getting multiline flexbox back into the spec fantasai
• Re: CSS Hierarchies / Selector Nesting Proposal Boris Zbarsky
• Re: CSS Hierarchies / Selector Nesting Proposal Boris Zbarsky

Sunday, 5 June 2011

• [css3-mediaqueries] [min|max]{device-}aspect-radio 1/1 and oriantation Robert Vincenz
• Re: [css-animation] transform origin rotation chaos (was an...) Simon Fraser
• Re: [css-animation] transform origin rotation chaos (was an...) Alan Gresley
• Re: [css3-flexbox] getting multiline flexbox back into the spec Alan Gresley
• Re: [css3-flexbox] getting multiline flexbox back into the spec Andrew Fedoniouk
• Re: [CSS21] dangling LBRACE terminal in grammar.html Bert Bos

Saturday, 4 June 2011

• Re: [css3-speech] voice family prohibition of spaces Andrew Thompson
• Re: CSS Hierarchies / Selector Nesting Proposal Brad Kemper
• [css3-speech] voice family prohibition of spaces Andrew Thompson
• Re: [css-animation] transform origin rotation chaos (was an...) Alan Gresley
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Brad Kemper
• Re: Inline elements should be affected by 2D Transforms Brad Kemper
• RE: [css3-flexbox] getting multiline flexbox back into the spec Alex Mogilevsky
• Re: [css3-flexbox] getting multiline flexbox back into the spec Andrew Fedoniouk
• RE: [css3-flexbox] getting multiline flexbox back into the spec Alex Mogilevsky
• RE: [css3-writing-modes] Character's intrinsic orientation Koji Ishii
• Re: Inline elements should be affected by 2D Transforms Shane Stephens
• Re: Inline elements should be affected by 2D Transforms Shane Stephens
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• Re: Inline elements should be affected by 2D Transforms Brian Blakely
• Re: Inline elements should be affected by 2D Transforms Shane Stephens
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• [CSS21] dangling LBRACE terminal in grammar.html L. David Baron
• Re: [css3-writing-modes] Character's intrinsic orientation fantasai

Friday, 3 June 2011

• Re: [css3-writing-modes] Character's intrinsic orientation Eric Muller
• Re: [css-animation] animation-fill-mode and animation groups Rik Cabanier
• Re: Inline elements should be affected by 2D Transforms Brad Kemper
• Re: Inline elements should be affected by 2D Transforms Boris Zbarsky
• Re: Inline elements should be affected by 2D Transforms Brad Kemper
• Re: Inline elements should be affected by 2D Transforms Brad Kemper
• Re: Inline elements should be affected by 2D Transforms Boris Zbarsky
• Re: Inline elements should be affected by 2D Transforms Boris Zbarsky
• Re: CSS Hierarchies / Selector Nesting Proposal Andrew Fedoniouk
• Re: Inline elements should be affected by 2D Transforms Brad Kemper
• Re: Inline elements should be affected by 2D Transforms Brian Blakely
• Re: [css-animation] animation-fill-mode and animation groups Boris Zbarsky
• Re: [css-animation] animation-fill-mode and animation groups Alan Gresley
• Re: Inline elements should be affected by 2D Transforms Brian Blakely
• Re: CSS Hierarchies / Selector Nesting Proposal Boris Zbarsky
• Re: CSS Hierarchies / Selector Nesting Proposal Boris Zbarsky
• Re: CSS Hierarchies / Selector Nesting Proposal Eduard Pascual
• Margin collapsing and auto 'top' for abs pos (was Re: Transitioning top and bottom properties.) Øyvind Stenhaug
• Re: CSS Hierarchies / Selector Nesting Proposal Boris Zbarsky
• Re: [css-animation] animation-fill-mode and animation groups Boris Zbarsky
• Re: CSS Hierarchies / Selector Nesting Proposal Øyvind Stenhaug
• Re: [css-animations] new property suggestion: animation-iteration-delay Alan Gresley
• [css-animation] animation-fill-mode and animation groups Alan Gresley
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Andrew Fedoniouk
• Re: CSS Hierarchies / Selector Nesting Proposal Andrew Fedoniouk
• Re: [CSS OM] list of issues Boris Zbarsky
• Re: Inline elements should be affected by 2D Transforms Alan Gresley
• RE: [CSS OM] list of issues Sylvain Galineau
• Re: [css3-flexbox] getting multiline flexbox back into the spec Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• Re: CSS Hierarchies / Selector Nesting Proposal Andrew Fedoniouk
• Re: An Example showing value of automatic Tate-Chu-Yoko in Japanese text timeless
• RE: Inline elements should be affected by 2D Transforms Sylvain Galineau
• Re: Inline elements should be affected by 2D Transforms Edward O'Connor
• Re: Inline elements should be affected by 2D Transforms L. David Baron
• An Example showing value of automatic Tate-Chu-Yoko in Japanese text Stephen Zilles
• Re: Inline elements should be affected by 2D Transforms Robert O'Callahan
• Re: [css3-lists] [css3-speech] Purpose of the module fantasai
• Re: [css3-speech] reading list-style markers fantasai
• Re: [css3-lists] [css3-speech] Purpose of the module timeless
• Re: Inline elements should be affected by 2D Transforms Brad Kemper

Thursday, 2 June 2011

• Re: [css3-lists] [css3-speech] Purpose of the module Andrew Thompson
• Re: Inline elements should be affected by 2D Transforms Robert O'Callahan
• Re: [css3-lists] [css3-speech] Purpose of the module timeless
• Re: CSS Hierarchies / Selector Nesting Proposal Eli Morris-Heft
• Re: [css3-lists] [css3-speech] Purpose of the module Andrew Thompson
• Re: CSS Hierarchies / Selector Nesting Proposal Brad Kemper
• RE: [css3-speech] reading list-style markers Belov, Charles
• Re: Inline elements should be affected by 2D Transforms Brian Blakely
• Re: Inline elements should be affected by 2D Transforms Brian Blakely
• Re: CSS Hierarchies / Selector Nesting Proposal Boris Zbarsky
• Re: CSS Hierarchies / Selector Nesting Proposal Brad Kemper
• Re: Inline elements should be affected by 2D Transforms Brad Kemper
• Re: [CSS21] double bar regex syntax mozer
• RE: [CSS21] double bar regex syntax - Please disregard Jack Smiley
• Re: CSS Hierarchies / Selector Nesting Proposal Boris Zbarsky
• [CSS21] double bar regex syntax Jack Smiley
• Re: CSS Hierarchies / Selector Nesting Proposal Brad Kemper
• Re: CSS Hierarchies / Selector Nesting Proposal Boris Zbarsky
• Re: Inline elements should be affected by 2D Transforms Simon Fraser
• Re: CSS Hierarchies / Selector Nesting Proposal Brad Kemper
• Re: Inline elements should be affected by 2D Transforms Brian Blakely
• Re: Inline elements should be affected by 2D Transforms Boris Zbarsky
• Re: [css3-regions] New CSS Regions editor draft Robert O'Callahan
• Inline elements should be affected by 2D Transforms Brian Blakely
• [css3-flexbox] getting multiline flexbox back into the spec Alex Mogilevsky
• RE: [css3-regions] New CSS Regions editor draft Alex Mogilevsky
• Re: [css3-regions] New CSS Regions editor draft Robert O'Callahan
• Re: [css3-regions] New CSS Regions editor draft Robert O'Callahan
• RE: [css3-regions] New CSS Regions editor draft Alex Mogilevsky
• Re: CSS Hierarchies / Selector Nesting Proposal Andrew Fedoniouk
• Re: [css3-lists] Published as WD! Tab Atkins Jr.
• Re: [css3-regions] New CSS Regions editor draft Robert O'Callahan
• Re: [css3-lists] Published as WD! Brad Kemper
• Re: Transitioning top and bottom properties. Boris Zbarsky
• Re: [css3-regions] New CSS Regions editor draft Tab Atkins Jr.
• RE: [css3-regions] New CSS Regions editor draft Alex Mogilevsky
• Re: [css3-lists] Published as WD! Tab Atkins Jr.
• Re: [css3-regions] New CSS Regions editor draft Robert O'Callahan
• RE: [css3-regions] New CSS Regions editor draft Alex Mogilevsky
• CSS Hierarchies / Selector Nesting Proposal Tab Atkins Jr.
• [css3-speech] reading list-style markers fantasai
• Re: [css3-regions] New CSS Regions editor draft Robert O'Callahan
• RE: [css3-regions] New CSS Regions editor draft Alex Mogilevsky

Wednesday, 1 June 2011

• Re: Transitioning top and bottom properties. fantasai
• [css3-writing-modes] text-combine and tatechuyoko John Daggett
• Re: [css3-regions] New CSS Regions editor draft Vincent Hardy
• Re: [css3-text] ED reviewed Alan Stearns
• RE: [css3-lists] Published as WD! Belov, Charles
• Re: [css-image] gradients, animations and photosensitive epilepsy timeless
• Re: [css3-lists] [css3-speech] Purpose of the module timeless
• Re: Transitioning top and bottom properties. Alan Gresley
• Re: [css3-fonts] mutiple formats in src descriptor timeless
• Re: [CSS OM] list of issues Daniel Glazman
• Re: Transitioning top and bottom properties. Øyvind Stenhaug
• Re: [CSS OM] list of issues Boris Zbarsky
• Re: [css3-writing-modes] comments on the spec, part 1 fantasai
• Re: [css3-lists] Published as WD! Håkon Wium Lie
• RE: [CSS OM] list of issues Sylvain Galineau
• Re: [CSS OM] list of issues Daniel Glazman
• RE: [CSS OM] list of issues Sylvain Galineau
• Re: [css3-lists] Published as WD! Brad Kemper
• Re: [css3-lists] Published as WD! Tab Atkins Jr.

Last message date: Thursday, 30 June 2011 23:16:04 UTC