GSoC frames idea

[Chris Young]

On Thu, 26 Mar 2009 19:06:40 +0000, John-Mark Bell wrote:

> On Thu, 2009-03-26 at 19:01 +0100, Chris Young wrote:
> > On Thu, 26 Mar 2009 18:43:02 +0000, John-Mark Bell wrote:
> > 
> > > Obviously, when navigating between pages, scrollbar widgets should be
> > > removed/added as appropriate by the core. Thus, the frame object should
> > > probably store the current offsets etc so it can recreate the widget if
> > > the user navigates back to the page.
> > 
> > The tabs system also needs improving as at the moment there is no way
> > of telling the core when you are switching tabs, so it can
> > destroy/create scrollbars as appropriate - unless the platform code
> > can keep track of which scrollbars are on which page?
> 
> Given the point is to make things simpler for the frontends, I'm not
> entirely sure what the best solution is here. It would be useful to have
> input from the other frontend implementors. TBH, it's a very long time
> since I went near the core/frontend interface in anger. So, regardless
> of what I think, other people are significantly better placed to design
> this API.

Michael's "get scrollbars for browser window" sounds like it will do
the trick.

If the scrollbars are going to have to be clippable, that's me stuffed
anyway (I think) - so I'd have to use the core rendered ones.

Chris