[webkit-dev] Apple's feature and performance goals for WebKit
mjs at apple.com
Fri Nov 30 15:28:12 PST 2007
On Nov 30, 2007, at 12:27 PM, Rob Napier wrote:
> On Nov 29, 2007 8:59 PM, Nicholas Shanks <contact at nickshanks.com>
> On 30 Nov 2007, at 00:27, Maciej Stachowiak wrote:
> >> • Ability to right-click on an element and remove it from flow
> >> (probably by adding a display: none attribute; so the DOM tree is
> >> intact)
> > The API capabilities needed for this are there. Can't comment on it
> > as a UI feature request.
> I thought contextual menus were handled by WebKit. Again, this isn't
> something that should only be in one client app, but ought to be
> everywhere HTML is rendered, so that the user experience is consistent
> and the feature doesn't get mis-implemented or simply left missing
> from some client.
> As a developer using WebKit, I definitely don't want my rendering to
> magically change just because the user wanted to change something in
> Safari. Some of the places I use WebKit aren't obviously "HTML" to
> the user (in an IM chat window for instance), so the fact that we
> would then render incorrectly would be exceedingly confusing.
> There's no way he would think "oh, that's a WebKit configuration I
> made." I'm very appreciative that WebKit keeps this stuff out of the
> Framework so my non-browser apps don't become dependent on Safari or
> any other web browser.
The WebKit API on Mac provides some built-in context menu items, but
gives applications full customization over the context menu items. So
you can either add custom context menu items, for instance to add the
feature Nicholas wants, or remove existing items.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev