W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2015

Re: [whatwg] Proposal: Allow disabling of default scroll restoration behavior

From: Anne van Kesteren <annevk@annevk.nl>
Date: Sat, 11 Jul 2015 19:51:11 +0200
Message-ID: <CADnb78jhG34M2x+A5+nCh+6D9fmt3bjYhXyAvVOMqkM8SPRcmQ@mail.gmail.com>
To: Majid Valipour <majidvp@chromium.org>
Cc: WHATWG <whatwg@whatwg.org>, Olli Pettay <olli@pettay.fi>, Ian Hickson <ian@hixie.ch>, Jonas Sicking <jonas@sicking.cc>, Rick Byers <rbyers@chromium.org>
On Fri, Jul 10, 2015 at 10:54 PM, Majid Valipour <majidvp@chromium.org> wrote:
> Minor bikeshed:
> I have put scrollRestoration on history.options instead of directly history
> itself in order to use history.options as an interface to contain any other
> restoration related attributes which have similar semantics (e.g., recorder
> scroll position, scale restoration, recorded scale).

Is the History object Document-bound in all implementations? Otherwise
adding new dependent objects will be problematic security-wise. Also,
History isn't that full and can easily contain a bunch of properties.
What's the use of a new object, can you use it independently somehow?

Received on Saturday, 11 July 2015 17:51:38 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:34 UTC