[prev in list] [next in list] [prev in thread] [next in thread] 

List:       webkit-dev
Subject:    Re: [webkit-dev] How loading a frame ought to work
From:       Adam Barth <abarth () webkit ! org>
Date:       2009-10-14 7:28:24
Message-ID: 7789133a0910140028s1de3d12aqf8a92bda2e5d647 () mail ! gmail ! com
[Download RAW message or body]

On Tue, Oct 13, 2009 at 3:00 PM, George Staikos <staikos@kde.org> wrote:
> Strongly support your suggested refactoring -- on the condition that you
> clearly document it on the wiki as you go.   This just gets more and more
> complex and I don't think we can risk more refactoring resulting in
> potentially even fewer people having a very clear idea of what is happening.

In general, the WebKit project seems to prefer easily understandable
code to external documentation.  When thing settle down some more,
I'll certainly add comments explaining what the role of each object
is.

> Also I wonder why fragment scroll isn't covered by the policy callback.  I
> haven't had a need to block that before but I can think of some cases right
> now where it might be handy.  I'm not advocating bloat without a cause, but
> perhaps if you're refactoring it we might un-special-case it.

This seems like a feature we can add in the future should we find a
need for it.  Certainly nothing I'm doing will preclude that.

Adam
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[prev in list] [next in list] [prev in thread] [next in thread]