public-whatwg-archive@w3.org from September 2012 by date

Sunday, 30 September 2012

• [whatwg] isAnyProtocolHandlerRegistered Brett Zamir

Saturday, 29 September 2012

• Re: [whatwg] CanvasRenderingContext2D with addPath, currentPath Rik Cabanier

Friday, 28 September 2012

• Re: [whatwg] CanvasRenderingContext2D with addPath, currentPath Dirk Schulze
• Re: [whatwg] CanvasRenderingContext2D with addPath, currentPath Rik Cabanier
• [whatwg] Proposal: new Table Parser Algorithm - new Table API - removal of the headers attribute - removal of the scope attribute Pierre Dubois
• Re: [whatwg] URL: javascript URLs Ian Hickson
• Re: [whatwg] URL: javascript URLs Boris Zbarsky
• Re: [whatwg] URL: javascript URLs Ian Hickson
• Re: [whatwg] URL: javascript URLs Boris Zbarsky
• Re: [whatwg] URL: javascript URLs Anne van Kesteren
• Re: [whatwg] URL: javascript URLs Boris Zbarsky
• Re: [whatwg] URL: javascript URLs Boris Zbarsky
• Re: [whatwg] URL: javascript URLs Anne van Kesteren
• Re: [whatwg] URL: javascript URLs Boris Zbarsky
• [whatwg] URL: javascript URLs Anne van Kesteren
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Boris Zbarsky
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Cameron McCormack
• Re: [whatwg] Elements feedback Ian Yang

Thursday, 27 September 2012

• [whatwg] Elements feedback Ian Hickson
• Re: [whatwg] TextTrack and addCue Philip Jägenstedt
• Re: [whatwg] metadata attribute for media Philip Jägenstedt
• Re: [whatwg] TextTrack and addCue Cyril Concolato
• Re: [whatwg] TextTrack and addCue Philip Jägenstedt

Wednesday, 26 September 2012

• [whatwg] TextTrack and addCue Cyril Concolato
• [whatwg] Proposal: HTMLCanvasElement.printCallback API Julian Viereck
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Anne van Kesteren
• [whatwg] Font Resize Event Hugh Guiney
• Re: [whatwg] New URL Standard Ian Hickson
• Re: [whatwg] New URL Standard Boris Zbarsky
• Re: [whatwg] New URL Standard Glenn Maynard
• Re: [whatwg] New URL Standard Boris Zbarsky
• Re: [whatwg] New URL Standard Glenn Maynard
• Re: [whatwg] New URL Standard Boris Zbarsky
• Re: [whatwg] New URL Standard Glenn Maynard
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Boris Zbarsky
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Cameron McCormack
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Boris Zbarsky
• Re: [whatwg] New URL Standard Boris Zbarsky
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Cameron McCormack
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Boris Zbarsky
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Adam Barth

Tuesday, 25 September 2012

• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Cameron McCormack
• Re: [whatwg] New URL Standard Glenn Maynard
• Re: [whatwg] New URL Standard Alexandre Morgaut
• Re: [whatwg] New URL Standard David Sheets
• Re: [whatwg] New URL Standard Glenn Maynard
• Re: [whatwg] Blending, filtering Rik Cabanier
• [whatwg] Blending, filtering Ian Hickson
• Re: [whatwg] Proposal for Links to Unrelated Browsing Contexts Charlie Reis
• Re: [whatwg] New URL Standard Anne van Kesteren
• Re: [whatwg] New URL Standard Ian Hickson
• Re: [whatwg] New URL Standard David Sheets
• Re: [whatwg] New URL Standard David Sheets
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Adam Barth
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Boris Zbarsky
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Adam Barth
• Re: [whatwg] New URL Standard Anne van Kesteren
• Re: [whatwg] New URL Standard Silvia Pfeiffer
• Re: [whatwg] New URL Standard Alexandre Morgaut
• Re: [whatwg] New URL Standard Robin Berjon
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Adam Barth
• Re: [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Boris Zbarsky
• [whatwg] Spec for location object needs to make some properties unforgeable; need supporting WebIDL changes Boris Zbarsky
• Re: [whatwg] New URL Standard Ian Hickson
• Re: [whatwg] DOM Keyboard Event Level 3 questions about proposal Ojan Vafai
• Re: [whatwg] New URL Standard David Sheets
• Re: [whatwg] Proposal for Links to Unrelated Browsing Contexts Boris Zbarsky
• Re: [whatwg] Proposal for Links to Unrelated Browsing Contexts Mihai Parparita
• Re: [whatwg] <canvas> and high-density displays Glenn Maynard
• Re: [whatwg] New URL Standard Ian Hickson
• Re: [whatwg] New URL Standard David Sheets

Monday, 24 September 2012

• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Dirk Schulze
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Tab Atkins Jr.
• [whatwg] <canvas> and high-density displays Ian Hickson
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Ian Hickson
• Re: [whatwg] New URL Standard Glenn Maynard
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Tab Atkins Jr.
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Dirk Schulze
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Ian Hickson
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Tab Atkins Jr.
• Re: [whatwg] New URL Standard David Sheets
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Ian Hickson
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Ian Hickson
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Jonas Sicking
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Tab Atkins Jr.
• Re: [whatwg] Proposal for Links to Unrelated Browsing Contexts Ian Hickson
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Ian Hickson
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Rick Waldron
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Tab Atkins Jr.
• Re: [whatwg] New URL Standard Tab Atkins Jr.
• Re: [whatwg] New URL Standard Boris Zbarsky
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Rick Waldron
• Re: [whatwg] New URL Standard Jukka K. Korpela
• Re: [whatwg] New URL Standard Karl Dubost
• Re: [whatwg] New URL Standard Alexandre Morgaut
• Re: [whatwg] New URL Standard Alexandre Morgaut
• Re: [whatwg] New URL Standard Jukka K. Korpela
• Re: [whatwg] New URL Standard Karl Dubost
• Re: [whatwg] New URL Standard Anne van Kesteren
• Re: [whatwg] New URL Standard Tobie Langel
• Re: [whatwg] New URL Standard Anne van Kesteren
• Re: [whatwg] Drag-and-drop folders/files support with directory structure using DirectoryEntry Kinuko Yasuda
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Tab Atkins Jr.
• Re: [whatwg] New URL Standard Maciej Stachowiak

Sunday, 23 September 2012

• Re: [whatwg] Covert sharing of user agent state. Ian Hickson
• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Ian Hickson
• Re: [whatwg] [canvas] Path object Charles Pritchard
• [whatwg] [canvas] Path object Elliott Sprehn

Saturday, 22 September 2012

• [whatwg] DOM Keyboard Event Level 3 questions about proposal Егор Николаев
• [whatwg] Covert sharing of user agent state. Fred Andrews
• [whatwg] [canvas] CanvasRenderingContext2D with addPath, currentPath Dirk Schulze
• Re: [whatwg] New URL Standard Alexandre Morgaut
• Re: [whatwg] [canvas] matrix based changes on bitmaps Rob Manson
• Re: [whatwg] [canvas] inner shadows Rik Cabanier

Friday, 21 September 2012

• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Tab Atkins Jr.
• Re: [whatwg] [canvas] matrix based changes on bitmaps Tab Atkins Jr.
• Re: [whatwg] New URL Standard Julian Reschke
• Re: [whatwg] New URL Standard Boris Zbarsky
• Re: [whatwg] [canvas] matrix based changes on bitmaps Tyler Larson
• [whatwg] New URL Standard Anne van Kesteren
• Re: [whatwg] c.c.rampley6778@gmail.com Tim Leverett
• [whatwg] c.c.rampley6778@gmail.com Chad Rampley
• Re: [whatwg] [canvas] inner shadows Tyler Larson
• [whatwg] c.c.rampley6778@gmail.com Chad Rampley
• [whatwg] (no subject) Chad Rampley
• [whatwg] Send whatwg mailing list submissions to Chad Rampley
• Re: [whatwg] [canvas] matrix based changes on bitmaps Rik Cabanier
• Re: [whatwg] isPointInPath on Path object Rik Cabanier
• Re: [whatwg] [canvas] matrix based changes on bitmaps Jussi Kalliokoski
• [whatwg] Path object with transform function (was: isPointInPath on Path object) Dirk Schulze
• Re: [whatwg] canvas miterLimit property Michael Day
• Re: [whatwg] canvas miterLimit property Ian Hickson
• Re: [whatwg] canvas miterLimit property Michael Day
• Re: [whatwg] isPointInPath on Path object Ian Hickson

Thursday, 20 September 2012

• Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Ian Hickson
• Re: [whatwg] canvas miterLimit property Ian Hickson
• Re: [whatwg] metadata attribute for media Rick Waldron
• Re: [whatwg] metadata attribute for media Ralph Giles
• Re: [whatwg] New canvas additions Ian Hickson
• Re: [whatwg] [canvas] matrix based changes on bitmaps Rob Manson
• Re: [whatwg] [canvas] inner shadows Ian Hickson
• Re: [whatwg] [canvas] letter-spaceing Ian Hickson
• Re: [whatwg] [canvas] matrix based changes on bitmaps Ian Hickson
• [whatwg] isPointInPath on Path object Dirk Schulze

Wednesday, 19 September 2012

• Re: [whatwg] URL: .origin Anne van Kesteren
• Re: [whatwg] URL: .origin Adam Barth
• [whatwg] URL: .origin Anne van Kesteren
• Re: [whatwg] Wasn't there going to be a strict spec? Henri Sivonen
• Re: [whatwg] Features for responsive Web design Henri Sivonen
• Re: [whatwg] Deferring javascript download and execution until after onload Andy Davies
• Re: [whatwg] Navigation and history traversal issues Ian Hickson
• Re: [whatwg] Navigation and history traversal issues Justin Lebar
• Re: [whatwg] Navigation and history traversal issues Ian Hickson
• Re: [whatwg] Navigation and history traversal issues Justin Lebar
• [whatwg] Navigation and history traversal issues Ian Hickson

Tuesday, 18 September 2012

• Re: [whatwg] [Web-storage] subdomains / cooperation and limits Ian Hickson
• Re: [whatwg] [Web-storage] subdomains / cooperation and limits Brian Kardell
• Re: [whatwg] Deferring javascript download and execution until after onload Jonas Sicking
• Re: [whatwg] Deferring javascript download and execution until after onload Tab Atkins Jr.
• Re: [whatwg] Deferring javascript download and execution until after onload Rick Waldron
• Re: [whatwg] Deferring javascript download and execution until after onload Jonas Sicking
• Re: [whatwg] exposing metadata on replaced elements (was: <video> feedback) Rick Waldron
• Re: [whatwg] exposing metadata on replaced elements (was: <video> feedback) Silvia Pfeiffer
• Re: [whatwg] exposing metadata on replaced elements (was: <video> feedback) Rick Waldron
• [whatwg] exposing metadata on replaced elements (was: <video> feedback) Silvia Pfeiffer
• Re: [whatwg] [Web-storage] subdomains / cooperation and limits Ian Hickson

Monday, 17 September 2012

• Re: [whatwg] [Web-storage] subdomains / cooperation and limits Brian Kardell
• Re: [whatwg] StringEncoding open issues Glenn Maynard
• Re: [whatwg] StringEncoding open issues Joshua Bell
• Re: [whatwg] [Web-storage] subdomains / cooperation and limits Ian Hickson
• Re: [whatwg] StringEncoding open issues Anne van Kesteren
• Re: [whatwg] StringEncoding open issues Joshua Bell
• [whatwg] [Web-storage] subdomains / cooperation and limits Brian Kardell
• [whatwg] <video> feedback Ian Hickson
• Re: [whatwg] MediaController feedback Ian Hickson
• [whatwg] Rename the 7-arg arcTo() to ellipseTo()? Tab Atkins Jr.
• [whatwg] Deferring javascript download and execution until after onload Andy Davies
• [whatwg] Two session history issues caused by navigating while a load is pending Justin Lebar

Sunday, 16 September 2012

• Re: [whatwg] Submitting contentEditable Content In A Form Jonas Sicking

Saturday, 15 September 2012

• Re: [whatwg] Regarding "Examples for rel=tag" Hugh Guiney
• Re: [whatwg] Regarding "Examples for rel=tag" Hugh Guiney

Friday, 14 September 2012

• Re: [whatwg] Regarding "Examples for rel=tag" Ian Hickson
• Re: [whatwg] Submitting contentEditable Content In A Form Alain Couthures
• Re: [whatwg] Submitting contentEditable Content In A Form Markus Ernst
• [whatwg] Regarding "Examples for rel=tag" Hugh Guiney
• Re: [whatwg] Drag-and-drop folders/files support with directory structure using DirectoryEntry Simon Pieters
• Re: [whatwg] Should editable elements have placeholder attribute? Simon Pieters

Thursday, 13 September 2012

• Re: [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element Silvia Pfeiffer
• Re: [whatwg] Drag-and-drop folders/files support with directory structure using DirectoryEntry Ian Hickson
• Re: [whatwg] Including HTML more directly into SVG Tab Atkins Jr.
• Re: [whatwg] Submitting contentEditable Content In A Form Ojan Vafai
• Re: [whatwg] Should editable elements have placeholder attribute? Ojan Vafai
• Re: [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element Kevin Deamandel
• Re: [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element Scott González
• Re: [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element Jukka K. Korpela
• Re: [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element Tab Atkins Jr.
• Re: [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element Jukka K. Korpela
• Re: [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element Tim Leverett
• [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element Kevin Deamandel
• [whatwg] Incomplete user-input in some input types TAMURA, Kent

Wednesday, 12 September 2012

• Re: [whatwg] DOM4: createHTMLDocument argument Anne van Kesteren
• Re: [whatwg] Canvas arcTo method Michael Day
• Re: [whatwg] canvas miterLimit property Michael Day

Tuesday, 11 September 2012

• Re: [whatwg] Including HTML more directly into SVG Elliott Sprehn
• Re: [whatwg] DOM4: createHTMLDocument argument Ojan Vafai
• Re: [whatwg] Including HTML more directly into SVG Tab Atkins Jr.
• Re: [whatwg] Including HTML more directly into SVG Elliott Sprehn
• Re: [whatwg] DOM4: createHTMLDocument argument Anne van Kesteren
• Re: [whatwg] DOM4: createHTMLDocument argument Ojan Vafai
• Re: [whatwg] Including HTML more directly into SVG Tab Atkins Jr.
• Re: [whatwg] Including HTML more directly into SVG Tab Atkins Jr.
• Re: [whatwg] [canvas] Proposal for supportsContext Glenn Maynard
• Re: [whatwg] canvas miterLimit property Rik Cabanier
• Re: [whatwg] Including HTML more directly into SVG David Carlisle
• Re: [whatwg] DOM4: createHTMLDocument argument Simon Pieters
• Re: [whatwg] [canvas] Proposal for supportsContext Tobie Langel
• Re: [whatwg] Including HTML more directly into SVG Benjamin Hawkes-Lewis
• Re: [whatwg] Including HTML more directly into SVG Elliott Sprehn
• Re: [whatwg] [canvas] Proposal for supportsContext Simon Pieters
• Re: [whatwg] Including HTML more directly into SVG Robin Berjon
• Re: [whatwg] DOM4: createHTMLDocument argument Elliott Sprehn
• Re: [whatwg] Including HTML more directly into SVG Elliott Sprehn
• Re: [whatwg] DOM4: createHTMLDocument argument Simon Pieters
• Re: [whatwg] Including HTML more directly into SVG Elliott Sprehn
• [whatwg] canvas miterLimit property Michael Day
• Re: [whatwg] WebIDL nested interfaces Tobie Langel
• Re: [whatwg] Exposing visible string of an input field TAMURA, Kent
• Re: [whatwg] WebIDL nested interfaces Cameron McCormack

Monday, 10 September 2012

• [whatwg] Including HTML more directly into SVG Tab Atkins Jr.
• Re: [whatwg] WebIDL nested interfaces Tobie Langel
• Re: [whatwg] [canvas] Proposal for supportsContext Paul Irish
• Re: [whatwg] WebIDL nested interfaces Boris Zbarsky
• Re: [whatwg] WebIDL nested interfaces Glenn Maynard
• [whatwg] WebIDL nested interfaces Tobie Langel
• Re: [whatwg] [canvas] Proposal for supportsContext Glenn Maynard
• Re: [whatwg] I believe source rectangles for HTML5 Canvas drawImage are specified incorrectly Jeff Muizelaar
• Re: [whatwg] [canvas] Proposal for supportsContext Ashley Gullen
• Re: [whatwg] [canvas] Proposal for supportsContext Mike Taylor
• Re: [whatwg] I believe source rectangles for HTML5 Canvas drawImage are specified incorrectly Justin Novosad
• Re: [whatwg] I believe source rectangles for HTML5 Canvas drawImage are specified incorrectly Jeff Muizelaar
• Re: [whatwg] [canvas] Proposal for supportsContext Dean Jackson
• Re: [whatwg] [canvas] Proposal for supportsContext Rick Waldron
• Re: [whatwg] [canvas] Proposal for supportsContext Tobie Langel
• Re: [whatwg] [canvas] Proposal for supportsContext Dean Jackson
• Re: [whatwg] [canvas] Proposal for supportsContext Tobie Langel
• Re: [whatwg] I believe source rectangles for HTML5 Canvas drawImage are specified incorrectly Vladimir Vukicevic
• Re: [whatwg] [canvas] Proposal for supportsContext Dean Jackson
• Re: [whatwg] [canvas] Proposal for supportsContext Ashley Gullen
• Re: [whatwg] [canvas] Proposal for supportsContext Dean Jackson
• Re: [whatwg] [canvas] Proposal for supportsContext Tobie Langel
• [whatwg] [canvas] Proposal for supportsContext Dean Jackson
• [whatwg] DOM4: createHTMLDocument argument Erik Arvidsson
• Re: [whatwg] Exposing visible string of an input field Kang-Hao (Kenny) Lu
• Re: [whatwg] Encoding sniffing algorithm Leif Halvard Silli

Sunday, 9 September 2012

• Re: [whatwg] "content" element, which we need in our documents Ian Yang
• Re: [whatwg] "content" element, which we need in our documents Steve Faulkner

Saturday, 8 September 2012

• Re: [whatwg] Features for responsive Web design Fred Andrews
• Re: [whatwg] Features for responsive Web design Smylers
• Re: [whatwg] Features for responsive Web design Fred Andrews
• Re: [whatwg] Features for responsive Web design Maciej Stachowiak

Friday, 7 September 2012

• Re: [whatwg] Features for responsive Web design Mathew Marquis
• Re: [whatwg] Submitting contentEditable Content In A Form Alain Couthures
• Re: [whatwg] Security restriction allows content thievery Adam Barth
• Re: [whatwg] srcset isn't future-friendly to screen size differences Tab Atkins Jr.
• Re: [whatwg] srcset isn't future-friendly to screen size differences Hans Muller
• Re: [whatwg] input type=barcode? Glenn Maynard
• Re: [whatwg] input type=barcode? Tobie Langel
• Re: [whatwg] Should editable elements have placeholder attribute? Aryeh Gregor
• Re: [whatwg] input type=barcode? Anne van Kesteren
• Re: [whatwg] srcset isn't future-friendly to screen size differences Fred Andrews
• Re: [whatwg] Submitting contentEditable Content In A Form Mikko Rantalainen
• Re: [whatwg] input type=barcode? Mikko Rantalainen
• [whatwg] Exposing visible string of an input field TAMURA, Kent
• Re: [whatwg] srcset isn't future-friendly to screen size differences Simon Pieters
• [whatwg] Submitting contentEditable Content In A Form Hugh Guiney
• Re: [whatwg] srcset isn't future-friendly to screen size differences Markus Ernst
• Re: [whatwg] Conformance checking of missing alternative content for images Benjamin Hawkes-Lewis
• Re: [whatwg] data URLs and XMLHttpRequest Anne van Kesteren
• Re: [whatwg] Conformance checking of missing alternative content for images Ian Hickson
• Re: [whatwg] Wasn't there going to be a strict spec? Michael[tm] Smith
• Re: [whatwg] Security restriction allows content thievery Ian Hickson
• Re: [whatwg] input type=barcode? Ian Hickson
• Re: [whatwg] Wasn't there going to be a strict spec? Ian Hickson
• Re: [whatwg] iframe sandbox and indexedDB Ian Hickson
• Re: [whatwg] iframe sandbox and indexedDB Ian Hickson
• Re: [whatwg] srcset isn't future-friendly to screen size differences Fred Andrews
• [whatwg] srcset isn't future-friendly to screen size differences Tab Atkins Jr.
• Re: [whatwg] Security restriction allows content thievery Fred Andrews

Thursday, 6 September 2012

• Re: [whatwg] Encoding sniffing algorithm Ian Hickson
• Re: [whatwg] whatwg Digest, Vol 102, Issue 19 Elton Hilsdorf Neves
• Re: [whatwg] data URLs and XMLHttpRequest Ian Hickson
• Re: [whatwg] Security restriction allows content thievery Ian Hickson
• Re: [whatwg] Should editable elements have placeholder attribute? Ojan Vafai
• [whatwg] Proposal about the table cell relationship combined with the column grouping and the row grouping Pierre Dubois
• Re: [whatwg] Why do HTML*Collection's nameItem need to return 5 different objects? Ojan Vafai
• Re: [whatwg] Should editable elements have placeholder attribute? Tab Atkins Jr.
• Re: [whatwg] Features for responsive Web design Simon Pieters
• Re: [whatwg] content editing (was Re: Request for new DOM property textarea.selectionText) Aryeh Gregor
• Re: [whatwg] Should editable elements have placeholder attribute? Aryeh Gregor
• Re: [whatwg] Why do HTML*Collection's nameItem need to return 5 different objects? Simon Pieters
• Re: [whatwg] content editing (was Re: Request for new DOM property textarea.selectionText) Simon Pieters
• Re: [whatwg] Quirks mode handling of rowspan="0" Simon Pieters
• Re: [whatwg] Features for responsive Web design Glenn Maynard
• Re: [whatwg] Features for responsive Web design Nils Dagsson Moskopp
• Re: [whatwg] Features for responsive Web design David Singer
• Re: [whatwg] Features for responsive Web design Glenn Maynard

Wednesday, 5 September 2012

• Re: [whatwg] Features for responsive Web design Aaron Gustafson
• Re: [whatwg] Features for responsive Web design Nils Dagsson Moskopp
• Re: [whatwg] Features for responsive Web design Nils Dagsson Moskopp
• Re: [whatwg] Features for responsive Web design Aaron Gustafson
• Re: [whatwg] register*Handler and Web Intents Greg Billock
• Re: [whatwg] Features for responsive Web design Kornel Lesiński
• Re: [whatwg] Adaptive Image Element Proposal Kornel Lesiński
• Re: [whatwg] Should editable elements have placeholder attribute? Ojan Vafai
• Re: [whatwg] Why do HTML*Collection's nameItem need to return 5 different objects? Ian Hickson
• [whatwg] content editing (was Re: Request for new DOM property textarea.selectionText) David Young
• Re: [whatwg] Features for responsive Web design Miguel Garcia
• Re: [whatwg] Features for responsive Web design Mathew Marquis
• Re: [whatwg] HTMLForms: Implicit Submission with {display:none} button Ian Hickson
• Re: [whatwg] Features for responsive Web design Nils Dagsson Moskopp
• Re: [whatwg] Hardware accelerated canvas Benoit Jacob
• Re: [whatwg] Hardware accelerated canvas Jonas Sicking
• Re: [whatwg] Features for responsive Web design Fred Andrews
• Re: [whatwg] Hardware accelerated canvas Charles Pritchard
• Re: [whatwg] Hardware accelerated canvas Rik Cabanier

Tuesday, 4 September 2012

• Re: [whatwg] Web Intents: Proposed modifications to the spec regarding registration Greg Billock
• Re: [whatwg] Adaptive Image Element Proposal Kornel Lesiński
• Re: [whatwg] Adaptive Image Element Proposal Kornel Lesiński
• Re: [whatwg] Hardware accelerated canvas Jussi Kalliokoski
• Re: [whatwg] Hardware accelerated canvas Boris Zbarsky
• Re: [whatwg] Hardware accelerated canvas Oliver Hunt
• Re: [whatwg] Features for responsive Web design Ian Hickson
• Re: [whatwg] Hardware accelerated canvas Jussi Kalliokoski
• Re: [whatwg] Hardware accelerated canvas Boris Zbarsky
• Re: [whatwg] Hardware accelerated canvas Glenn Maynard
• Re: [whatwg] Hardware accelerated canvas Jussi Kalliokoski
• Re: [whatwg] Hardware accelerated canvas Erik Möller
• Re: [whatwg] Hardware accelerated canvas Kornel Lesiński
• Re: [whatwg] Hardware accelerated canvas Kornel Lesiński
• Re: [whatwg] Hardware accelerated canvas Erik Möller
• Re: [whatwg] Hardware accelerated canvas Justin Novosad
• Re: [whatwg] Hardware accelerated canvas Ashley Gullen
• Re: [whatwg] Hardware accelerated canvas Justin Novosad
• Re: [whatwg] Hardware accelerated canvas Boris Zbarsky
• Re: [whatwg] Hardware accelerated canvas David Geary
• Re: [whatwg] Hardware accelerated canvas Ian Hickson
• Re: [whatwg] Hardware accelerated canvas Szymon Piłkowski
• Re: [whatwg] Hardware accelerated canvas Mark Callow
• Re: [whatwg] Hardware accelerated canvas Glenn Maynard
• Re: [whatwg] Hardware accelerated canvas Boris Zbarsky
• Re: [whatwg] Hardware accelerated canvas Boris Zbarsky
• Re: [whatwg] Hardware accelerated canvas Tab Atkins Jr.
• Re: [whatwg] Hardware accelerated canvas David Geary
• Re: [whatwg] Hardware accelerated canvas David Geary
• Re: [whatwg] Hardware accelerated canvas Boris Zbarsky
• Re: [whatwg] Hardware accelerated canvas Boris Zbarsky
• Re: [whatwg] Canvas arcTo method Ian Hickson
• Re: [whatwg] Hardware accelerated canvas James Robinson
• Re: [whatwg] Canvas arcTo method Justin Novosad
• Re: [whatwg] Hardware accelerated canvas Erik Möller
• Re: [whatwg] Hardware accelerated canvas Robert O'Callahan
• [whatwg] Hardware accelerated Canvas Saurabh Jain

Monday, 3 September 2012

• Re: [whatwg] Hardware accelerated canvas Tobie Langel
• Re: [whatwg] Hardware accelerated canvas Rik Cabanier
• Re: [whatwg] Hardware accelerated canvas David Geary
• Re: [whatwg] Hardware accelerated canvas Glenn Maynard
• Re: [whatwg] Hardware accelerated canvas Ian Hickson
• Re: [whatwg] Canvas arcTo method Ian Hickson
• Re: [whatwg] Canvas roundedRect Ian Hickson
• Re: [whatwg] Quirks mode handling of rowspan="0" Boris Zbarsky
• Re: [whatwg] Quirks mode handling of rowspan="0" Boris Zbarsky
• Re: [whatwg] Hardware accelerated canvas Benoit Jacob
• Re: [whatwg] Hardware accelerated canvas Benoit Jacob
• Re: [whatwg] Hardware accelerated canvas Erik Möller
• Re: [whatwg] Hardware accelerated canvas Erik Möller
• Re: [whatwg] Quirks mode handling of rowspan="0" Simon Pieters
• Re: [whatwg] Quirks mode handling of rowspan="0" Jukka K. Korpela
• Re: [whatwg] Quirks mode handling of rowspan="0" Kang-Hao (Kenny) Lu
• Re: [whatwg] Hardware accelerated canvas Rik Cabanier
• Re: [whatwg] Hardware accelerated canvas Charles Pritchard
• Re: [whatwg] Hardware accelerated canvas Glenn Maynard
• [whatwg] Quirks mode handling of rowspan="0" Boris Zbarsky

Sunday, 2 September 2012

• Re: [whatwg] Hardware accelerated canvas Rik Cabanier
• Re: [whatwg] Hardware accelerated canvas Benoit Jacob
• Re: [whatwg] Hardware accelerated canvas Ian Hickson
• Re: [whatwg] Hardware accelerated canvas Glenn Maynard
• Re: [whatwg] Hardware accelerated canvas Ashley Gullen
• Re: [whatwg] "content" element, which we need in our documents Charles McCathie Nevile
• [whatwg] Hardware accelerated canvas Erik Möller
• Re: [whatwg] gradient edge case Rik Cabanier
• Re: [whatwg] gradient edge case Rik Cabanier
• Re: [whatwg] gradient edge case David Dailey
• [whatwg] gradient edge case Rik Cabanier
• Re: [whatwg] Proposal for HTML5: Motion sensing input device (Kinect, SoftKinetic, Asus Xtion) Jesús Ruiz García

Saturday, 1 September 2012

• Re: [whatwg] Proposal for HTML5: Motion sensing input device (Kinect, SoftKinetic, Asus Xtion) Jesús Ruiz García
• Re: [whatwg] Should editable elements have placeholder attribute? David Young

Last message date: Sunday, 30 September 2012 03:39:44 UTC