Re: [whatwg] Proposal: navigator.cores

2014-07-01 Thread Rik Cabanier
On Wed, Jul 2, 2014 at 2:19 AM, Ryosuke Niwa wrote: > On May 3, 2014, at 10:49 AM, Adam Barth wrote: > > > Over on blink-dev, we've been discussing [1] adding a property to > navigator > > that reports the number of cores [2]. As far as I can tell, this > > functionality exists in every other p

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

2014-07-01 Thread Boris Zbarsky
On 7/1/14, 10:18 PM, Ryosuke Niwa wrote: Could you point me to a specific test case that demonstrates the difference? http://fiddle.jshell.net/t4sgd/show/ Chrome and Firefox alert "true"; IE alerts "false". The spec says "false" should be alerted. -Boris

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

2014-07-01 Thread Ryosuke Niwa
Could you point me to a specific test case that demonstrates the difference? On Mar 3, 2014, at 3:04 AM, Bob Owen wrote: > Hi, > > The spec at [1] and [2] seems to be fairly clear that if an existing window > is navigated using window.open, by a browsing context that is not the > original opene

Re: [whatwg] Move contentEditable/isContentEditable from HTMLElement to Element?

2014-07-01 Thread Ryosuke Niwa
On May 15, 2014, at 10:01 AM, Elliott Sprehn wrote: > On Tue, May 13, 2014 at 11:21 AM, Ian Hickson wrote: > >> I would feel more comfortable putting things on SVG, MathML, and HTML >> explicitly. >> > I don't think we want contenteditable in SVG or MathML. Almost all of the > operations don't

Re: [whatwg] Proposal: Inline pronounce element (Tab Atkins Jr.)

2014-07-01 Thread Ryosuke Niwa
On Jun 6, 2014, at 12:04 PM, Charles McCathie Nevile wrote: > On Fri, 06 Jun 2014 14:22:48 +0200, Koji Ishii > wrote: > >> On Jun 5, 2014, at 22:08, Tab Atkins Jr. wrote: >> >>> On Thu, Jun 5, 2014 at 11:29 AM, Nils Dagsson Moskopp >>> wrote: Brett Zamir writes: > On 6/5/20

Re: [whatwg] Proposal: navigator.cores

2014-07-01 Thread Ryosuke Niwa
On May 3, 2014, at 10:49 AM, Adam Barth wrote: > Over on blink-dev, we've been discussing [1] adding a property to navigator > that reports the number of cores [2]. As far as I can tell, this > functionality exists in every other platform (including iOS and Android). > Some of the use cases for

Re: [whatwg] Proposal: navigator.cores

2014-07-01 Thread Nils Dagsson Moskopp
Eli Grey writes: > We want to claim 6 in that situation. If the API claimed less than 6 > on Samsung's Exynos 5 Hexa (2x A15 cores + 4x A7 cores), then the > cores will be underutilized. Implying it is right for any application to utilize all cores available in a multi-process environment that m