- From: Philip Jägenstedt <philipj@opera.com>
- Date: Thu, 16 Jul 2015 17:21:09 +0200
- To: Majid Valipour <majidvp@google.com>
- Cc: Rick Byers <rbyers@chromium.org>, WHATWG <whatwg@whatwg.org>, Olli Pettay <olli@pettay.fi>, Majid Valipour <majidvp@chromium.org>, Ian Hickson <ian@hixie.ch>, Jonas Sicking <jonas@sicking.cc>
On Mon, Jul 13, 2015 at 5:56 PM, Majid Valipour <majidvp@google.com> wrote: > On Mon, Jul 13, 2015 at 10:55 AM Philip Jägenstedt <philipj@opera.com> >> If the StateOptions interface could be implemented with no internal >> reference back to its owning History object it seems pretty harmless, >> a mere holder of values, > > I think a reference to History may be needed because changing scrollState > needs to update current entry with the new effective value. So it is not a > simple value holder. I somewhat suspected that, and it would make StateOptions a tear-off from History, and tear-offs are a bit annoying IMHO :) Philip
Received on Thursday, 16 July 2015 15:21:36 UTC