From kapinos at twobytesoftware.com Mon Apr 10 10:02:59 2017 From: kapinos at twobytesoftware.com (Pavel Kapinos) Date: Mon, 10 Apr 2017 10:02:59 -0700 Subject: [webkit-help] WebKitLegacy on iOS Message-ID: Hi, I git WebKit from webkit.org build it for device and embedded WebKitLegacy and WebCore into iOS app. Then loaded and run app on device no problem! App instantiates WebView and loads URL into it and it all works great - except I can't add that instance of WebView as subview to UIView as it is a WAKView apparently Did I miss something here or when compiling and building WebKit? I need WebView as opposed to UIWebView WKWebView as WebView give access to DOM which is what I need. Thank you very much! Cheers, Pavel. From annulen at yandex.ru Fri Apr 21 05:17:28 2017 From: annulen at yandex.ru (Konstantin Tokarev) Date: Fri, 21 Apr 2017 15:17:28 +0300 Subject: [webkit-help] Triggering icon load after FrameLoaderClient::dispatchDidChangeIcons event Message-ID: <3597211492777048@web34j.yandex.ru> Hello, I'm trying to support dynamic updates of favicon in WebKit1 (Qt port), like what happens in the following example: I've found that FrameLoaderClient::dispatchDidChangeIcons() is called in this case, however FrameLoaderClient::dispatchDidReceiveIcon() is not, and icon inside IconDatabase is not updated. I've found that doing the following call in my overload of dispatchDidChangeIcons fixes things: m_frame->loader().icon().startLoader(); (where m_frame is WebCore::Frame) Is it the right thng to do? I see startLoader is called only inside Document, this makes me wonder if there is any layering violation here. Thanks in advance! -- Regards, Konstantin From mkaisercross at gmail.com Thu Apr 27 10:28:54 2017 From: mkaisercross at gmail.com (Michael Kaiser-Cross) Date: Thu, 27 Apr 2017 13:28:54 -0400 Subject: [webkit-help] Plans to support HTML5 fullscreen API? In-Reply-To: References: Message-ID: Is there any plans for webkit to support the HTML5 fullscreens API? -------------- next part -------------- An HTML attachment was scrubbed... URL: From annulen at yandex.ru Thu Apr 27 10:33:55 2017 From: annulen at yandex.ru (Konstantin Tokarev) Date: Thu, 27 Apr 2017 20:33:55 +0300 Subject: [webkit-help] Plans to support HTML5 fullscreen API? In-Reply-To: References: Message-ID: <495191493314435@web30j.yandex.ru> 27.04.2017, 20:29, "Michael Kaiser-Cross" : > Is there any plans for webkit to support the HTML5 fullscreens API? WebKit supports latest W3C edition of HTML5 fullscreens API since year 2012. -- Regards, Konstantin From jer.noble at apple.com Thu Apr 27 10:49:44 2017 From: jer.noble at apple.com (Jer Noble) Date: Thu, 27 Apr 2017 10:49:44 -0700 Subject: [webkit-help] Plans to support HTML5 fullscreen API? In-Reply-To: <495191493314435@web30j.yandex.ru> References: <495191493314435@web30j.yandex.ru> Message-ID: <092F817E-CE32-4CCC-9557-A14F06E92CC5@apple.com> > On Apr 27, 2017, at 10:33 AM, Konstantin Tokarev wrote: > > > 27.04.2017, 20:29, "Michael Kaiser-Cross" : >> Is there any plans for webkit to support the HTML5 fullscreens API? > > WebKit supports latest W3C edition of HTML5 fullscreens API since year 2012. Not entirely true. Our fullscreen support is still prefixed because we have not yet implemented the “topmost stacking context” part of the fullscreen specification. -Jer