Re: [whatwg] Effect on window.opener when navigating an existing window using window.open

2014-04-02 Thread Ian Hickson
On Mon, 3 Mar 2014, Bob Owen wrote: The spec [...] seems to be fairly clear that if an existing window is navigated using window.open, by a browsing context that is not the original opener, then window.opener should remain unchanged. Currently, Trident (and incidentally Presto) seems to

Re: [whatwg] Media sink device selection on audio/video

2014-04-02 Thread Ian Hickson
On Mon, 3 Mar 2014, Ami Fischman wrote: Looks like we're back in business: Latest editor's draft: http://dev.w3.org/2011/webrtc/editor/getusermedia.html Thanks. As a user, this scares me a lot. Why isn't it up to me to control this? I don't understand the security model here at all. I

Re: [whatwg] More effective model for handling resources

2014-04-02 Thread Ian Hickson
On Thu, 13 Mar 2014, Tingan Ho wrote: Almost all web developer I know use externally linked CSS resource in their web projects. That means that the browser needs to (1) request the html page (2) parse the html (3) request for the CSS resource that is linked from the html document. The

Re: [whatwg] inverse property mechanism for Microdata?

2014-04-02 Thread Ian Hickson
On Wed, 19 Mar 2014, Dan Brickley wrote: This is what the example would look like if I'm understanding this right: div itemscope itemtype=http://schema.org/LocalBusiness; h1span itemprop=name(Entity A) Beachwalk Beachwear Giftware/span/h1 span itemprop=description A

Re: [whatwg] Effect on window.opener when navigating an existing window using window.open

2014-04-02 Thread Bob Owen
On 2 April 2014 18:43, Ian Hickson i...@hixie.ch wrote: On Mon, 3 Mar 2014, Bob Owen wrote: The spec [...] seems to be fairly clear that if an existing window is navigated using window.open, by a browsing context that is not the original opener, then window.opener should remain

[whatwg] Various autocomplete= topics

2014-04-02 Thread Ian Hickson
On Wed, 5 Mar 2014, Qebui Nehebkau wrote: On Tue, Mar 4, 2014 at 11:41 PM, Ian Hickson i...@hixie.ch wrote: I think the arguments you've presented so far suggest address-levelN for N=1..4, with 4=region and 3=locality, is probably the simplest thing to do. I was hoping there might be

Re: [whatwg] Effect on window.opener when navigating an existing window using window.open

2014-04-02 Thread Ian Hickson
On Wed, 2 Apr 2014, Bob Owen wrote: Did you receive any off-list feedback on this, or attempt to implement it and get any implementation experience? Thanks for getting back to me Ian. No, no other feedback. I have a patch for it, but haven't pursued it any further. I could investigate

Re: [whatwg] Effect on window.opener when navigating an existing window using window.open

2014-04-02 Thread Bob Owen
On 2 April 2014 22:00, Ian Hickson i...@hixie.ch wrote: It's worth noting that there are many many ways to navigate a browsing context beyond window.open(), e.g. a target=, window.location, drag-and-drop of a link, window.history.go(), etc. Absolutely, if we were to converge on the spec for

Re: [whatwg] More effective model for handling resources

2014-04-02 Thread Tingan Ho
Hi Ian, I believe this is being handled by the next-generation transport protocols (SPDY or whatever it's called now). I recommend approaching the relevant groups to check that your precise case has been handled. I just found out that SPDY Server Push and Cookies could accomplish the above