Custom popups & Content API (standard)

[fddima]

By this comment https://code.google.com/p/chromium/issu ... =155761#c7 - it is will be near possible to create own-handled popups. I think that CEF is must support this.
I thinking about this long time, but my hands are short.
I.e. in general - idea, as, i'm understand - same as with input type=date - it is regular html, which rendered as part of document (i.e. not new browser/frame), but rendered as really native POPUP window - it is very-very-very cool. Since any other html-only solutions - are doesn't allow create native popups (i.e. windows like in dropdowns) - it is will be very cool to get some support of this functionality with CEF.
I.e. i mean, that CEF user will be can own own popup window with HTML markup without additional browsers / etc (also OSR affected). Since while standard select element very limited - it is very cool function. Same with input type=date/other (date are implemented, but permanently banned by me and my company - it is very specific, and uncontrolled ).
For embedded appls - i want own hosted popups!!! It was be ideas for last 2 years...

[magreenblatt]

Proposed APIs (and of course implementations ) are welcome. The initial use case is off-screen rendering (http://code.google.com/p/chromiumembedd ... ail?id=518).

[fddima]

Oh. I mean, that i thinking about not initial use-case - i.e. about in native rendering, i.e. allow way by CEF API making own controls, like input type=date. After this patch it is probably will be simplier. My question may be more likely about - it is interesting thing, or no too likely by peoples... In any case personally i'm can't work on it feat just now (and probably can't work on it later - i'm actually doesn't have experience for this).

[fddima]

And, yeah, i'm precisely look before to impl of input type=date - main difficult that it is doesn't have any adequate content api - but in general - same way can be adopted to any element. I.e. task was be around make some (many?) calls to provide content for popup, and main question it is activate popup window, but it may be can be easily done by external actions (unlike input type=date - which handles this itself). I.e. as for me - more interest it is have handle of popup window + html source of content + handling, instead of predefined elements. But, it is task for third look - too complex to me - i'm not specialist for chromium arch - i really doesn't have idea how it must work, how it will be usable. I just wrote 'cause may be it is interested not just for me, and may be some also can join. I can do some work, but i'm doesn't feel to complete it at all by self.

[magreenblatt]

It seems like your idea is theoretically possible. However, the WebContentsView interface is pretty large and implementations tend to be platform-specific. I'm not sure how feasable it would be to develop a single CEF API that addresses all (most?) of the possible widget types.