- From: Majid Valipour <majidvp@chromium.org>
- Date: Thu, 13 Aug 2015 11:25:04 +0000
- To: Jonas Sicking <jonas@sicking.cc>, Olli Pettay <olli@pettay.fi>
- Cc: WHATWG <whatwg@whatwg.org>, Majid Valipour <majidvp@chromium.org>
On Wed, Aug 12, 2015 at 11:47 PM Jonas Sicking <jonas@sicking.cc> wrote: > On Wed, Aug 12, 2015 at 3:31 AM, Olli Pettay <olli@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 do this, I think popstate event should also become cancelable, so > that > > web page could easily > > prevent scrolling (in that case there wouldn't be need to play with > > scrollRestoration always) > > Is there an advantage to having two ways to prevent scoll restoration? > I think it will be confusing. Note that history.scrollRestoration works also for cross-document history navigation which cannot be done with popstate. Majid
Received on Thursday, 13 August 2015 11:25:50 UTC