public-whatwg-archive@w3.org from February 2014 by date

Friday, 28 February 2014

• Re: [whatwg] iframe scrolling attribute Ian Hickson

Wednesday, 26 February 2014

• Re: [whatwg] Guessing the fallback encoding from the top-level domain name before trying to guess from the browser localization Henri Sivonen
• Re: [whatwg] <keygen> and X509 client cert mime type henry.story@bblfish.net

Tuesday, 25 February 2014

• [whatwg] <keygen> and X509 client cert mime type henry.story@bblfish.net
• Re: [whatwg] Supporting more address levels in autocomplete Jürg Lehni

Monday, 24 February 2014

• Re: [whatwg] Supporting more address levels in autocomplete Evan Stade
• Re: [whatwg] Supporting more address levels in autocomplete Dan Brickley
• Re: [whatwg] Supporting more address levels in autocomplete Charles McCathie Nevile
• Re: [whatwg] Supporting more address levels in autocomplete Jukka K. Korpela

Sunday, 23 February 2014

• [whatwg] New feature: better integration with browser find interface Mitar

Saturday, 22 February 2014

• Re: [whatwg] hit regions: limited set of elements for fallback content Nils Dagsson Moskopp
• Re: [whatwg] hit regions: limited set of elements for fallback content Steve Faulkner
• Re: [whatwg] Supporting more address levels in autocomplete Ian Hickson
• Re: [whatwg] Supporting more address levels in autocomplete Kevin Marks
• Re: [whatwg] Supporting more address levels in autocomplete Ian Hickson
• Re: [whatwg] Supporting more address levels in autocomplete Kevin Marks
• Re: [whatwg] Supporting more address levels in autocomplete Ian Hickson

Friday, 21 February 2014

• [whatwg] Supporting more address levels in autocomplete Dan Beam
• Re: [whatwg] hit regions: limited set of elements for fallback content Nils Dagsson Moskopp
• Re: [whatwg] hit regions: limited set of elements for fallback content Charles McCathie Nevile
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• Re: [whatwg] hit regions: limited set of elements for fallback content Charles McCathie Nevile
• Re: [whatwg] hit regions: limited set of elements for fallback content Steve Faulkner
• Re: [whatwg] Proposal: requestBackgroundProcessing() Robert O'Callahan
• Re: [whatwg] Proposal: requestBackgroundProcessing() Glenn Maynard

Thursday, 20 February 2014

• Re: [whatwg] Proposal: requestBackgroundProcessing() Ashley Gullen
• Re: [whatwg] Proposal: requestBackgroundProcessing() Glenn Maynard
• Re: [whatwg] Proposal: requestBackgroundProcessing() David Young
• Re: [whatwg] hit regions: limited set of elements for fallback content Nils Dagsson Moskopp
• Re: [whatwg] Proposal: requestBackgroundProcessing() Ashley Gullen
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• Re: [whatwg] MetaExtensions for HTML5 vs. custom tagging Michael[tm] Smith
• Re: [whatwg] hit regions: limited set of elements for fallback content Dominic Mazzoni
• Re: [whatwg] Proposal: requestBackgroundProcessing() Maciej Stachowiak
• Re: [whatwg] Proposal: requestBackgroundProcessing() Glenn Maynard
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• Re: [whatwg] Proposal: requestBackgroundProcessing() Rik Cabanier
• Re: [whatwg] Proposal: requestBackgroundProcessing() Glenn Maynard
• Re: [whatwg] Proposal: requestBackgroundProcessing() Ashley Gullen
• Re: [whatwg] Proposal: requestBackgroundProcessing() James Robinson
• Re: [whatwg] <input type=number> for year input Nils Dagsson Moskopp
• Re: [whatwg] Proposal: requestBackgroundProcessing() Boris Zbarsky
• Re: [whatwg] Proposal: requestBackgroundProcessing() Tab Atkins Jr.
• Re: [whatwg] Proposal: requestBackgroundProcessing() Ashley Gullen
• Re: [whatwg] Proposal: requestBackgroundProcessing() Tab Atkins Jr.
• [whatwg] Proposal: requestBackgroundProcessing() Ashley Gullen
• Re: [whatwg] <input type=number> for year input Jonathan Watt
• Re: [whatwg] hit regions: limited set of elements for fallback content Dominic Mazzoni
• Re: [whatwg] <input type=number> for year input Qebui Nehebkau
• Re: [whatwg] <input type=number> for year input TAMURA, Kent

Wednesday, 19 February 2014

• [whatwg] URL spec and IDN Joshua Cranmer
• Re: [whatwg] <input type=number> for year input Nils Dagsson Moskopp
• Re: [whatwg] <input type=number> for year input Qebui Nehebkau
• Re: [whatwg] <input type=number> for year input Smylers
• Re: [whatwg] <input type=number> for year input Jukka K. Korpela
• Re: [whatwg] <input type=number> for year input Domenic Denicola
• Re: [whatwg] <input type=number> for year input Cameron Jones
• Re: [whatwg] <input type=number> for year input Nils Dagsson Moskopp
• Re: [whatwg] <input type=number> for year input Smylers
• Re: [whatwg] <input type=number> for year input Qebui Nehebkau
• Re: [whatwg] <input type=number> for year input Jukka K. Korpela
• Re: [whatwg] <input type=number> for year input Nils Dagsson Moskopp
• Re: [whatwg] <input type=number> for year input David Dailey
• Re: [whatwg] <input type=number> for year input David Dailey
• Re: [whatwg] <input type=number> for year input Jonathan Watt
• Re: [whatwg] <input type=number> for year input Karl Dubost
• Re: [whatwg] <input type=number> for year input Michael[tm] Smith
• Re: [whatwg] <input type=number> for year input Jukka K. Korpela

Tuesday, 18 February 2014

• Re: [whatwg] <input type=number> for year input Ian Hickson
• Re: [whatwg] <input type=number> for year input Mike Taylor
• Re: [whatwg] <input type=number> for year input Mike Taylor
• Re: [whatwg] <input type=number> for year input Jonathan Watt
• Re: [whatwg] <input type=number> for year input Jonathan Watt
• Re: [whatwg] <input type=number> for year input Ian Hickson
• [whatwg] <input type=number> for year input Jonathan Watt
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• Re: [whatwg] Drawing shapes on canvas Rik Cabanier
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• Re: [whatwg] hit regions: limited set of elements for fallback content Dominic Mazzoni
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• Re: [whatwg] hit regions: limited set of elements for fallback content Dominic Mazzoni
• Re: [whatwg] hit regions: limited set of elements for fallback content Rik Cabanier
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• Re: [whatwg] hit regions: limited set of elements for fallback content Dominic Mazzoni
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• Re: [whatwg] hit regions: limited set of elements for fallback content Dominic Mazzoni
• Re: [whatwg] hit regions: limited set of elements for fallback content Rik Cabanier
• Re: [whatwg] hit regions: limited set of elements for fallback content Ian Hickson
• [whatwg] hit regions: limited set of elements for fallback content Rik Cabanier

Saturday, 15 February 2014

• [whatwg] Shared storage Brett Zamir

Friday, 14 February 2014

• [whatwg] Notifications: createTime property Michael Henretty

Monday, 10 February 2014

• Re: [whatwg] iframes, more sandbox Chris Coyier
• Re: [whatwg] microdata questions Eric Devine

Saturday, 8 February 2014

• Re: [whatwg] hit regions: moving an element out of the shadow tree Ian Hickson
• Re: [whatwg] Guessing the fallback encoding from the top-level domain name before trying to guess from the browser localization Henri Sivonen
• Re: [whatwg] hit regions: moving an element out of the shadow tree Rik Cabanier
• Re: [whatwg] Media sink device selection on <audio>/<video> Ian Hickson

Friday, 7 February 2014

• Re: [whatwg] Media sink device selection on <audio>/<video> Ami Fischman
• Re: [whatwg] Guessing the fallback encoding from the top-level domain name before trying to guess from the browser localization Ian Hickson
• Re: [whatwg] Media sink device selection on <audio>/<video> Ian Hickson
• Re: [whatwg] iframes, more sandbox David Bruant
• Re: [whatwg] [Canvas] Behavior on non-invertable CTM Justin Novosad

Thursday, 6 February 2014

• Re: [whatwg] [Canvas] Behavior on non-invertable CTM Rik Cabanier
• Re: [whatwg] [Canvas] Behavior on non-invertable CTM Ian Hickson
• Re: [whatwg] [Canvas] Behavior on non-invertable CTM Justin Novosad
• Re: [whatwg] iframes, more sandbox Shane Hudson
• [whatwg] iframes, more sandbox Chris Coyier
• Re: [whatwg] Feedback on seamless iframe attribute Ryosuke Niwa

Wednesday, 5 February 2014

• [whatwg] content model for MathML <annotation-xml encoding="text/html"> [was: Document.title for SVG documents] Michael[tm] Smith
• Re: [whatwg] Document.title for SVG documents Simon Pieters
• Re: [whatwg] Document.title for SVG documents David Carlisle
• Re: [whatwg] Document.title for SVG documents Simon Pieters
• Re: [whatwg] Proposal: Specify SHA512 hash of JavaScript files in <script> tag Yoav Weiss
• Re: [whatwg] Proposal: Specify SHA512 hash of JavaScript files in <script> tag Igor Minar

Tuesday, 4 February 2014

• Re: [whatwg] Proposal: Specify SHA512 hash of JavaScript files in <script> tag Ian Hickson
• Re: [whatwg] Document.title for SVG documents Dirk Schulze
• Re: [whatwg] hit regions: moving an element out of the shadow tree Ian Hickson
• Re: [whatwg] hit regions: moving an element out of the shadow tree Rik Cabanier
• Re: [whatwg] Document.title for SVG documents Ian Hickson
• Re: [whatwg] hit regions: moving an element out of the shadow tree Ian Hickson
• Re: [whatwg] Document.title for SVG documents Anne van Kesteren
• [whatwg] hit regions: moving an element out of the shadow tree Rik Cabanier
• Re: [whatwg] Document.title for SVG documents Cameron McCormack
• Re: [whatwg] Document.title for SVG documents Jonas Sicking
• Re: [whatwg] Document.title for SVG documents Cameron McCormack

Monday, 3 February 2014

• Re: [whatwg] inputmode feedback Ian Hickson
• Re: [whatwg] onclose events for MessagePort Ian Hickson
• Re: [whatwg] onclose events for MessagePort Jonas Sicking
• Re: [whatwg] Comments on <dialog> Ian Hickson
• Re: [whatwg] Document.title for SVG documents Ian Hickson
• Re: [whatwg] Document.activeElement should return the root element in non-HTML documents when no element has focus Ian Hickson
• Re: [whatwg] Comments on <dialog> Brian Blakely
• Re: [whatwg] Document.activeElement should return the root element in non-HTML documents when no element has focus Ian Hickson
• [whatwg] Feedback on seamless iframe attribute Ben Vinegar
• Re: [whatwg] Document.activeElement should return the root element in non-HTML documents when no element has focus Simon Pieters
• Re: [whatwg] Document.activeElement should return the root element in non-HTML documents when no element has focus Boris Zbarsky
• Re: [whatwg] Document.activeElement should return the root element in non-HTML documents when no element has focus Anne van Kesteren
• Re: [whatwg] inputmode feedback Michael[tm] Smith
• Re: [whatwg] Document.activeElement should return the root element in non-HTML documents when no element has focus Cameron McCormack

Sunday, 2 February 2014

• Re: [whatwg] IE10 inconsistency with Blob / createObjectURL Jonas Sicking
• Re: [whatwg] Document.activeElement should return the root element in non-HTML documents when no element has focus Anne van Kesteren
• Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement? Cameron McCormack
• Re: [whatwg] Document.title for SVG documents Cameron McCormack
• Re: [whatwg] Document.title for SVG documents Dirk Schulze
• Re: [whatwg] Document.title for SVG documents Cameron McCormack
• [whatwg] Document.title for SVG documents Cameron McCormack
• [whatwg] Document.activeElement should return the root element in non-HTML documents when no element has focus Cameron McCormack

Saturday, 1 February 2014

• [whatwg] IE10 inconsistency with Blob / createObjectURL K. Gadd
• Re: [whatwg] Comments on <dialog> Ian Hickson

Last message date: Friday, 28 February 2014 23:28:26 UTC