[Webkit-unassigned] [Bug 47256] Adding C api for <select> popups

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Oct 7 01:55:07 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=47256





--- Comment #14 from Luiz Agostini <luiz at webkit.org>  2010-10-07 01:55:06 PST ---
(In reply to comment #13)
> (In reply to comment #11)
> > I’m not sure this is the right direction. We should not land anything here until we hear from Sam Weinig, Anders Carlsson, and Maciej Stachowiak. Do we really need API for this?
> > 
> > The term “combo box” is a Windows-specific one that I don’t see at all in HTML specifications and doesn’t make sense to me for a cross-platform API. I’d prefer that we not include this phrase in our function names.
> 
> This is definitely seems like the wrong direction to go.  Much like the reset of the UI elements in a web page, the <select> element should be handled by the engine, not the embedder.  Can you explain a bit more why you think this should not just be implemented in WebKit itself?

This is because users of QtWebKit may provide customizations for the <select> popups.

In mobile platforms, for example, we want all our <select> elements to be rendered as menu lists, even multiple selection ones and the ones which have size > 1. But for it to work we need to provide a menu list popup that is big enough to provide a good user experience and that is capable of handling multiple selections. Something similar goes on in iPhone.

Today we have a plugin mechanism that can be used to provide menu list popup customizations. If a plugin is provided then the popup handling is delegated to the plugin. If no plugin is provided then we use the standard popup implementation. Different platforms may decide how to implement their own popups in their own way. We already have some different implementations for meego, symbian, etc.

The objective of this api is to provide a way to do the same in WebKit2.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list