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 > 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. > Agreed, except I doubt it'll take that long. Once we have a good answer for how to properly fix your site, and have given some warning (we'll do evangelism of the new API with the Chrome 46 release), I think we'll be OK breaking a few sites here if necessary. 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. > We've got a couple high profile Google properties waiting to use this API (Eg. Google Search). I suspect the better user experience on browsers with this API will help motivate them :-). Majid >
