- From: Majid Valipour <majidvp@chromium.org>
- Date: Wed, 12 Aug 2015 16:37:45 +0000
- To: Anne van Kesteren <annevk@annevk.nl>, Majid Valipour <majidvp@chromium.org>
- Cc: WHATWG <whatwg@whatwg.org>
> > > 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 and what > will happen to Safari. > > I am optimistic that this is possible to fix in Chrome once a widely supported, inter-operable, and reliable alternative solution is in place. It requires evangelism and will take some time to deprecate. AFAICT the workaround use is still limited and they have considerable drawbacks which helps drive their deprecation in favor of a better solution. As for what will happen to Safari, I am also curious to find out as well. I have filed a webkit bug <https://bugs.webkit.org/show_bug.cgi?id=147782> to see if they are interested in implementing scrollRestoration. I am waiting to see if I there is enough traction there to be hopeful. Majid
Received on Wednesday, 12 August 2015 16:38:27 UTC