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

Saturday, 31 October 2015

• Re: [css-device-adapt] New WD Florian Rivoal
• Re: [css-device-adapt] New WD Alan Stearns
• [css3-page] Additional page sizes Florian Rivoal
• [css-line-grid] line-grid:match-parent and orthogonal flows Florian Rivoal
• [css-device-adapt] New WD Florian Rivoal

Friday, 30 October 2015

• Re: range of non-overflown content Johannes Wilm
• Re: range of non-overflown content Alan Stearns
• range of non-overflown content Johannes Wilm

Thursday, 29 October 2015

• [bikeshed] Missing line break in code samples? François REMY
• [css-content] Request for note regarding selection, search, and accessibility of generated content Joanmarie Diggs

Wednesday, 28 October 2015

• Re: [css-animations] Initial summary of outstanding issues Brian Birtles
• Re: [css-text] animatibility of 'tab-size' Tab Atkins Jr.
• [css-fonts] updated wording for subscript/superscript glyph synthesis John Daggett

Tuesday, 27 October 2015

• Re: [css-break][css-masking][css-shapes] fragmentation fantasai
• [css-animations] Initial summary of outstanding issues Brian Birtles
• [css-color-4] "color adjuster" vs color-adjust L. David Baron
• [css-round-display] device-radius media query replacement L. David Baron
• [css-images] Contradiction in definition of <color-stop-list> Daniel Holbert
• [web compat] max-width and intrinsic sizes in a table scenario Karl Dubost

Sunday, 25 October 2015

• Re: [css-backgrounds][css-grid][css-logical] 2-axis positions vs. 4-direction shorthands Brad Kemper
• Re: [css-backgrounds][css-grid][css-logical] 2-axis positions vs. 4-direction shorthands Brad Kemper
• Re: [css-backgrounds][css-grid][css-logical] 2-axis positions vs. 4-direction shorthands Rachel Andrew
• Re: [css-snappoints][css-scroll-snap] 1D vs. 2D (diagonal) snapping Florian Rivoal
• [css-snappoints][css-scroll-snap] 1D vs. 2D (diagonal) snapping fantasai
• [css-backgrounds][css-grid][css-logical] 2-axis positions vs. 4-direction shorthands fantasai
• [css-snappoints][css-scroll-snap] Trapping snap coordinates from bubbling up to ancestor scrollers fantasai

Saturday, 24 October 2015

• Re: [css-round-display] part of abs-pos (was: Suggest 'polar-anchor' property for positioning elements without overflowing) Brad Kemper

Thursday, 22 October 2015

• Re: [css-animations] Multiple identifiers per @keyframes rule Lewis Dexter Litanzios / ldexterldesign

Friday, 23 October 2015

• Re: [css-fonts] font-weight-adjust Florian Rivoal
• Re: [css-fonts] font-weight-adjust John Daggett
• Re: [css-fonts] font-weight-adjust Florian Rivoal
• Re: [css-fonts] font-weight-adjust John Daggett
• RE: [css-snappoints] Various issues François REMY
• Re: [css-fonts] font-weight-adjust Florian Rivoal
• Re: [css-text-decor] Value syntax of text-emphasis shorthand Xidorn Quan
• [css-text-decor] Value syntax of text-emphasis shorthand Xidorn Quan

Thursday, 22 October 2015

• [css-text] animatibility of 'tab-size' L. David Baron
• [CSSWG] Minutes Telecon 2015-10-21 [css-round-display] [css-writing-modes] [css-text-3] [css-will-change] [css-variables] [css-cascade] Dael Jackson
• Re: [cssom-view] Propose to add attrs for getting max/min value of scroll coordinate attrs Simon Pieters
• [css-scroll-snap] "single mandatory" Florian Rivoal
• [css-text] computed value for word-spacing:<percentage> Cameron McCormack

Wednesday, 21 October 2015

• Re: [css-animations] Multiple identifiers per @keyframes rule Lea Verou
• Re: [css-animations] Multiple identifiers per @keyframes rule Tab Atkins Jr.
• Re: [css-round-display] What is the % in device-radius relative to? Tab Atkins Jr.
• Re: [css-round-display] Miscellaneous suggestions Adenilson Cavalcanti
• Re: [css-snappoints] feedback on alternate model draft fantasai
• Re: [css-snappoints] Various issues Tab Atkins Jr.
• Re: [css-animations] Multiple identifiers per @keyframes rule Lea Verou
• Re: [css-animations] Multiple identifiers per @keyframes rule Simon Fraser
• Re: [csswg] Agenda conf call 21-Oct-2015 Chris Lilley
• RE: [css-text-3] word-break: break-all Phillips, Addison
• Re: [css-text-3] word-break: break-all 馬場孝夫
• Re: [css-text-3] word-break: break-all fantasai
• Re: [css-fonts] font-weight-adjust Jonathan Kew
• Re: [css-fonts] font-weight-adjust Florian Rivoal
• Re: [cssom-view][css-writing-modes] Behavior of scrollLeft in RTL or vertical-rl mode Xidorn Quan
• [cssom-view] Propose to add attrs for getting max/min value of scroll coordinate attrs Xidorn Quan
• Re: [cssom-view][css-writing-modes] Behavior of scrollLeft in RTL or vertical-rl mode Simon Pieters
• Re: [css-round-display] What is the % in device-radius relative to? Florian Rivoal
• [css-round-display] Propose 'polar-orientation' property for aligning elements Jihye Hong
• Re: [css-animations] Multiple identifiers per @keyframes rule Lea Verou

Tuesday, 20 October 2015

• Re: [css-animations] Multiple identifiers per @keyframes rule Xidorn Quan
• [css-animations] Multiple identifiers per @keyframes rule Lea Verou
• [csswg] Agenda conf call 21-Oct-2015 Daniel Glazman
• Re: [css-round-display] Miscellaneous suggestions Adenilson Cavalcanti
• Re: [css-round-display] What is the % in device-radius relative to? Tab Atkins Jr.
• Re: [css-overflow] overflow-x, overflow-y and tables Robert Hogan
• RE: [css-snappoints][css-scroll-snap] Fragment ID and scroll-snapping Matt Rakow
• Re: [css-shapes] Shapes, margin clipping, and misleading examples Alan Stearns
• Re: [css-shapes] Shapes, margin clipping, and misleading examples Eric A. Meyer
• RE: [css-round-display] Miscellaneous suggestions Hyojin Song
• Re: [css-snappoints] Befine behaviour when content is larger than scroll container fantasai
• [css-snappoints][css-scroll-snap] Fragment ID and scroll-snapping fantasai

Monday, 19 October 2015

• Re: [css-round-display] Miscellaneous suggestions Adenilson Cavalcanti
• Re: [css-snappoints] repeat(calc(<value>)) clamping behaviour Tab Atkins Jr.
• Re: [css-snappoints] repeat(calc(<value>)) clamping behaviour fantasai
• Re: [css-overflow] overflow-x, overflow-y and tables L. David Baron
• Re: [css-overflow] overflow-x, overflow-y and tables Robert Hogan
• Re: [css-fonts] font-weight-adjust Jonathan Kew
• RE: [css-fonts] font-weight-adjust Levantovsky, Vladimir
• Re: [css-fonts] font-weight-adjust Florian Rivoal
• Re: [css-text-3] word-break: break-all Koji Ishii
• Re: [css-fonts] font-weight-adjust Florian Rivoal
• RE: [css-fonts] font-weight-adjust Levantovsky, Vladimir
• Re: [css-fonts] font-weight-adjust Jonathan Kew
• [css-fonts] font-weight-adjust Florian Rivoal
• Re: [css-transitions] style change terminology Ojan Vafai

Saturday, 17 October 2015

• RE: [css-round-display] What is the % in device-radius relative to? Hyojin Song

Friday, 16 October 2015

• Re: [css-shapes] Shapes, margin clipping, and misleading examples Alan Stearns
• Re: [css-shapes] Shapes, margin clipping, and misleading examples L. David Baron
• Re: [css-shapes] Shapes, margin clipping, and misleading examples Alan Stearns
• Re: [CSS21][CSS22] Request to clarify the section 6.4.3. Gérard Talbot
• Re: [css-round-display] part of abs-pos (was: Suggest 'polar-anchor' property for positioning elements without overflowing) Florian Rivoal

Wednesday, 14 October 2015

• [CSS-2015] Two minor comments on CSS Snapshot 2015 Momdo Nakamura
• [CSS21][CSS22] Request to clarify the section 6.4.3. Momdo Nakamura

Tuesday, 13 October 2015

• Re: [css-values] Line-height relative length units 'lh' and 'rlh' wadev@mailbox.hu

Friday, 16 October 2015

• Re: [css-round-display] Suggest 'polar-anchor' property for positioning elements without overflowing Brad Kemper
• Re: [css-round-display] part of abs-pos (was: Suggest 'polar-anchor' property for positioning elements without overflowing) Brad Kemper
• Re: [css-round-display] part of abs-pos (was: Suggest 'polar-anchor' property for positioning elements without overflowing) Florian Rivoal
• Re: [css-round-display] What is the % in device-radius relative to? Florian Rivoal
• [css-shapes] Shapes, margin clipping, and misleading examples Eric A. Meyer
• RE: [css-transitions] style change terminology François REMY

Thursday, 15 October 2015

• Re: [css-round-display] part of abs-pos (was: Suggest 'polar-anchor' property for positioning elements without overflowing) Brad Kemper
• Re: An invitation from PF Tab Atkins Jr.
• RE: An invitation from PF Rossen Atanassov
• Re: [css-round-display] What is the % in device-radius relative to? Tab Atkins Jr.
• Re: [css-text-3] word-break: break-all Koji Ishii
• Re: [css-round-display] Suggest 'polar-anchor' property for positioning elements without overflowing Jihye Hong
• Re: [css-text-3] word-break: break-all Florian Rivoal

Wednesday, 14 October 2015

• [css-round-display] Miscellaneous suggestions Adenilson Cavalcanti
• Re: [css-align] in which cases does 'left'/'right' compute to 'start' exactly? Mats Palmgren
• [csswg][css-2015] Updated CSS Snapshot and Prefix Policy fantasai
• [css-text-3] word-break: break-all Koji Ishii
• Re: [css-grid] About the meaning of being "sized under min|max-content constraint" Sergio Villar Senin
• [css-align][css-grid] Baseline Content-Alignment subjects in Grid Layout Javier Fernandez
• Re: An invitation from PF Daniel Glazman

Tuesday, 13 October 2015

• Re: [css-text] CSS Text Module Level 4 Ambrose LI
• Re: [css-text] CSS Text Module Level 4 timeless
• Re: [css-flexbox] Textarea as a flex container Boris Zbarsky
• Re: [css-flexbox] Textarea as a flex container John Waterson
• Re: [css-flexbox] Textarea as a flex container Boris Zbarsky
• [css-flexbox] Textarea as a flex container John Waterson
• Re: [css-round-display] Suggest 'polar-anchor' property for positioning elements without overflowing Alan Stearns
• Re: [css-round-display] Suggest 'polar-anchor' property for positioning elements without overflowing Jihye Hong
• Re: [mediaqueries] CSS "prefers-" media features (from TPAC discussion) James Craig
• Re: [css-text] CSS Text Module Level 4 John Hudson
• Re: [css-text] CSS Text Module Level 4 Liam Quin

Monday, 12 October 2015

• Re: [css-text] CSS Text Module Level 4 timeless
• RE: [css-round-display] What is the % in device-radius relative to? Hyojin Song

Sunday, 11 October 2015

• An invitation from PF Janina Sajka

Saturday, 10 October 2015

• [css-transitions] style change terminology L. David Baron
• Proposing ::contents pseudo-element‏‏ Oriol Bugzilla
• Re: [mediaqueries] CSS "prefers-" media features (from TPAC discussion) Tab Atkins Jr.

Friday, 9 October 2015

• Re: [css-text] CSS Text Module Level 4 Ambrose LI
• [css-text] CSS Text Module Level 4 timeless
• Re: [css-align] implementability of computed value rules for align/justify-self/items Ojan Vafai
• Re: [css-round-display] Suggest ‘polar-anchor’ property for positioning elements without overflowing Brad Kemper
• [css-flexbox] available space and max-height Christian Biesinger
• Re: [css-grid] How to resolve lines for absolutely positioned grid items Mats Palmgren
• Re: [mediaqueries] CSS "prefers-" media features (from TPAC discussion) James Craig

Thursday, 8 October 2015

• Re: [css-align] implementability of computed value rules for align/justify-self/items Daniel Holbert
• Re: [css-align] implementability of computed value rules for align/justify-self/items L. David Baron
• Re: [css-align] implementability of computed value rules for align/justify-self/items Tab Atkins Jr.
• Re: [css-align] implementability of computed value rules for align/justify-self/items Boris Zbarsky
• Re: [transitions] unfinished transitions v. elapsedTime Shane Stephens
• Re: [css-align] implementability of computed value rules for align/justify-self/items Tab Atkins Jr.
• Re: [css-align] implementability of computed value rules for align/justify-self/items L. David Baron
• Re: [css-grid] How to resolve lines for absolutely positioned grid items Tab Atkins Jr.
• Re: [css-grid] How to resolve lines for absolutely positioned grid items Mats Palmgren
• Re: [css-round-display] Suggest ‘polar-anchor’ property for positioning elements without overflowing Alan Stearns
• Re: [css-transforms] How should scrollbars react to a scaled-down element? Robert O'Callahan
• [CSSWG] Minutes Telecon 2015-10-07 [css-2015] [css-text] [cssom-view] [css-writing-modes] [css-logical-properties] [css-grid] [css-flexbox] [css-break] Dael Jackson
• RE: [css-round-display] Suggest ‘polar-anchor’ property for positioning elements without overflowing Jihye Hong
• Re: [css-fonts] ready attribute vs function Dominik Röttsches
• RE: [css-break] Breaking inside an inline-block element? François REMY
• Re: [css-break] Breaking inside an inline-block element? fantasai
• Re: [css-fonts] Shape of the CSSFontFaceRule interface John Daggett
• Re: [css-fonts] ready attribute vs function John Daggett
• Re: [css-transforms] How should scrollbars react to a scaled-down element? Tab Atkins Jr.
• Re: [css-transforms] How should scrollbars react to a scaled-down element? Robert O'Callahan

Wednesday, 7 October 2015

• Re: [css-images] API for authors to request concrete object size & position, for replaced element w/ "object-fit"/"object-position" Daniel Holbert
• [css-round-display] What is the % in device-radius relative to? Tab Atkins Jr.
• RE: [css-fonts] Shape of the CSSFontFaceRule interface Greg Whitworth
• [css-transforms] How should scrollbars react to a scaled-down element? Tab Atkins Jr.
• Re: [css-grid] Implicit Named Areas Tab Atkins Jr.
• Re: [css-fonts] ready attribute vs function Rik Cabanier
• Re: [css-fonts] ready attribute vs function Tab Atkins Jr.
• Re: [css-grid] Implicit Named Areas Mats Palmgren
• Re: [css-grid] Implicit Named Areas Mats Palmgren
• Re: [css-images] API for authors to request concrete object size & position, for replaced element w/ "object-fit"/"object-position" Tab Atkins Jr.
• Re: [css-grid] Implicit Named Areas Sergio Villar Senin
• Re: [css-images] API for authors to request concrete object size & position, for replaced element w/ "object-fit"/"object-position" Robert O'Callahan
• Re: [css-fonts] ready attribute vs function Dominik Röttsches
• Re: [css-fonts] ready attribute vs function Dominik Röttsches
• [csswg] Agenda conf call 07-Oct-2015 Daniel Glazman
• [css-images] API for authors to request concrete object size & position, for replaced element w/ "object-fit"/"object-position" Daniel Holbert

Tuesday, 6 October 2015

• Re: [css-fonts] ready attribute vs function Rik Cabanier
• Re: [css-fonts] ready attribute vs function Tab Atkins Jr.
• Re: [css-fonts] ready attribute vs function Rik Cabanier
• Re: [css-fonts] ready attribute vs function Tab Atkins Jr.
• Re: [css-fonts] ready attribute vs function Rik Cabanier
• Re: [css-fonts] ready attribute vs function Tab Atkins Jr.
• Re: [css-fonts] ready attribute vs function Rik Cabanier
• Re: [css-fonts] ready attribute vs function Tab Atkins Jr.
• Re: [css-grid] Implicit Named Areas Tab Atkins Jr.
• Re: [css-logical-properties] the 'inline-{start,end}' values for 'float' and 'clear' fantasai
• Re: CSS Tab Atkins Jr.
• Re: [CSS Abstract] What kind of lenguage is CSS? Tab Atkins Jr.
• Re: [CSS Abstract] What kind of lenguage is CSS? Zack Weinberg
• [CSS Abstract] What kind of lenguage is CSS? Kseso
• [css-sizing][css-grid] Doubt about definite/indefinite size Manuel Rego Casasnovas
• Re: CSS Lars Knudsen

Monday, 5 October 2015

• CSS Cristi Bloj

Tuesday, 6 October 2015

• Re: [css-fonts] ready attribute vs function Rik Cabanier

Monday, 5 October 2015

• Re: [css-logical-properties] the 'inline-{start,end}' values for 'float' and 'clear' Koji Ishii
• [css-page-floats] Re: [css-logical-properties] the 'inline-{start,end}' values for 'float' and 'clear' Johannes Wilm
• [css-grid] Implicit Named Areas Mats Palmgren
• Re: [css-logical-properties] the 'inline-{start,end}' values for 'float' and 'clear' Jonathan Kew
• Re: [css-logical-properties] the 'inline-{start,end}' values for 'float' and 'clear' Koji Ishii
• Re: [css-grid] A few questions on Grid gutters (grid-column-gap, grid-row-gap, and grid-gap properties) Sergio Villar Senin
• Re: [css-grid] Containing block for abs.pos. grid items when the grid overflows Manuel Rego Casasnovas
• Re: [css-fonts] ready attribute vs function John Daggett

Sunday, 4 October 2015

• [css-grid] Grid Placement Conflict Handling is now missing the equal start/end line case Mats Palmgren
• [css-grid] Clamping Overlarge Grids - error in example and typos Mats Palmgren
• Re: [web-animations] Should computedTiming return a live object? Brian Birtles
• Re: [web-animations] Should computedTiming return a live object? Brian Birtles

Saturday, 3 October 2015

• [css-align] Two editorial nits Mats Palmgren
• Re: [css-align] definition of 'align-content'/'justify-content' should define computed value for 'auto' Mats Palmgren
• [css-grid] A few questions on Grid gutters (grid-column-gap, grid-row-gap, and grid-gap properties) Mats Palmgren
• [css-fonts] ready attribute vs function Rik Cabanier

Friday, 2 October 2015

• Re: [css-grid][css-align] Default alignment of grid tracks Javier Fernandez
• Re: [css-align] implementability of computed value rules for align/justify-self/items Tab Atkins Jr.
• Re: [css-align] computed value of 'align-self: auto' fantasai
• Re: [css-align] definition of 'align-content'/'justify-content' should define computed value for 'auto' Tab Atkins Jr.
• [css-grid][css-align] Default alignment of grid tracks fantasai
• Re: [will-change] Editorial: will-change: all example is invalid Tab Atkins Jr.
• Re: [css-color] L4 spec changes don't mention device-cmyk() Tab Atkins Jr.
• RE: [web-animations] Should computedTiming return a live object? Domenic Denicola
• Re: [web-animations] Should computedTiming return a live object? Anne van Kesteren
• Re: Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value Richard Ishida
• Re: [css-logical-properties] the 'inline-{start,end}' values for 'float' and 'clear' Jonathan Kew
• Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value Tab Atkins Jr.

Thursday, 1 October 2015

• Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value fantasai
• Re: [css-writing-modes] computed value for text-orientation: sideways or sideways-right Jonathan Kew
• [CSSWG] Minutes Telecon 2015-09-30 [css-round-display] [css-animations] [css-transforms] [css-selectors] [css-ruby] Dael Jackson
• Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value Koji Ishii
• Re: Styling <input type=text> Anne van Kesteren
• Re: [css-writing-modes] Computed values of obsolete writing-mode values Gérard Talbot
• [web-animations] Should computedTiming return a live object? Brian Birtles
• Re: [css-writing-modes] Computed values of obsolete writing-mode values Koji Ishii
• Re: [css-animations][css-transitions] What is the intended use of elapsedTime? Brian Birtles
• Re: [css-writing-modes] Propose to weaken upright rendering of horizontal-only scripts fantasai
• Re: [css-writing-modes] Propose to weaken upright rendering of horizontal-only scripts fantasai
• Re: [css-writing-modes] computed value for text-orientation: sideways or sideways-right Gérard Talbot
• Re: [css-writing-modes] Computed values of obsolete writing-mode values Gérard Talbot
• Re: [css-writing-modes] float interaction when line-left and line-right swap fantasai
• Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value Tab Atkins Jr.

Last message date: Saturday, 31 October 2015 15:01:34 UTC