On Wed, Aug 12, 2015 at 12:37 PM, Majid Valipour maji...@chromium.org
wrote:
Does anybody know if there was any specific reasons behind the current
order?
Are the reasons you discovered yourself not sufficient?
They are pretty compelling but was wondering if there is anything I am
On Wed, Aug 12, 2015 at 3:31 AM, Olli Pettay o...@pettay.fi wrote:
There are two options to get an interop solution:
Option 1. Change the spec to reverse order, making the workaround
supported
officially.
Does anybody know if there was any specific reasons behind the current
order?
If we
On 08/11/2015 05:08 PM, Majid Valipour wrote:
According to HTML5 spec persisted user state (scroll, scale, form values,
etc)
should be restored before dispatching popstate event. (See steps 9 and 14 in
history traversal algorithm[1]).
Gecko and IE follow the spec order for scroll position but
Does anybody know if there was any specific reasons behind the current
order?
Are the reasons you discovered yourself not sufficient?
They are pretty compelling but was wondering if there is anything I am
missing.
I guess the
question is whether Chrome can still change at this point
