Re: [whatwg] iframe scrolling attribute

2014-02-28 Thread Ian Hickson
On Thu, 9 Jan 2014, Mats Palmgren wrote: The current spec[1] for the scrolling attribute of [i]frame elements does not reflect what is implemented by a majority of UAs. We intend to change Firefox to implement the behavior of IE/Chrome/Safari and would like to see the spec changed to

[whatwg] Size of non-rendered viewports

2014-02-28 Thread Ian Hickson
On Tue, 7 Jan 2014, Boris Zbarsky wrote: On 1/7/14 2:24 PM, Ian Hickson wrote: It's probably just a matter of saying, in the rendering section, that nested browsing contexts that aren't _being_rendered_ (or that are frames outside framesets) get a 0x0 viewport. That doesn't seem

Re: [whatwg] Supporting more address levels in autocomplete

2014-02-28 Thread Ian Hickson
On Mon, 24 Feb 2014, Jukka K. Korpela wrote: 2014-02-22 3:03, Ian Hickson wrote: (Note that a lot of people in the UK have no idea how to write their address according to current standards. For example, people often include the county, give the real town rather than the post town,

Re: [whatwg] Supporting more address levels in autocomplete

2014-02-28 Thread Evan Stade
On Fri, Feb 28, 2014 at 5:47 PM, Ian Hickson i...@hixie.ch wrote: On Mon, 24 Feb 2014, Jukka K. Korpela wrote: 2014-02-22 3:03, Ian Hickson wrote: (Note that a lot of people in the UK have no idea how to write their address according to current standards. For example, people often

[whatwg] hit regions: event bubbling

2014-02-28 Thread Rik Cabanier
Reading the hit region spec [1] on event handling, I was wondering how event bubbling is supposed to be handled. Let's say you have the following markup: canvas id=cnv a id=a href=.../a a id=b href=.../a /canvas and the following code: var ctx = document.getElementById(cnv).getContext(2d);