On 8 July 2014 17:20, Ryosuke Niwa wrote:
> Yes, our behavior is same as Firefox and Chrome.
Thanks for confirming.
> I'm somewhat concerned about the backwards compatibility given behaviors
of
> Chrome, Firefox, and Safari match and only Internet Explorer matches the
spec.
>
> But perhaps it's
On Jul 2, 2014, at 5:43 AM, Bob Owen wrote:
> On 2 July 2014 03:18, Ryosuke Niwa wrote:
>>
>> Could you point me to a specific test case that demonstrates the
> difference?
>
> Sure, here you go:
> https://people.mozilla.org/~bowen/openerTest/openerTest.html
>
> In IE you get "firstOpener" al
On Jul 1, 2014, at 9:45 PM, Boris Zbarsky wrote:
> 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"
>
On 2 July 2014 03:18, Ryosuke Niwa wrote:
>
> Could you point me to a specific test case that demonstrates the
difference?
Sure, here you go:
https://people.mozilla.org/~bowen/openerTest/openerTest.html
In IE you get "firstOpener" alerted both times, which is as spec.
In Firefox and Chrome "sec
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
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
On 3 April 2014 19:28, Charlie Reis wrote:
> For what it's worth, I think we'd be open to changing Blink to match the
spec as well, if you don't find any compat issues.
I'd say it's worth a lot, thanks Charlie.
On Wed, Apr 2, 2014 at 3:09 PM, Bob Owen wrote:
> On 2 April 2014 22:00, Ian Hickson wrote:
>
> > It's worth noting that there are many many ways to navigate a browsing
> > context beyond window.open(), e.g. , window.location,
> > drag-and-drop of a link, window.history.go(), etc.
>
> Absolutely
On 2 April 2014 22:00, Ian Hickson wrote:
> It's worth noting that there are many many ways to navigate a browsing
> context beyond window.open(), e.g. , window.location,
> drag-and-drop of a link, window.history.go(), etc.
Absolutely, if we were to converge on the spec for the current opener an
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 i
On 2 April 2014 18:43, Ian Hickson 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 unchanged.
>
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) seem
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 opener, then window.opener should remain unchanged.
Currently, Trident (and incidentally Presto) seems to have the correct
behaviour, but
13 matches
Mail list logo
