I can test "visibility" and "hidden" states with GTK+ widget visibility and probably "prerender" state with off screen loading of the page. But to make layout tests pass and make some testing for WebKit2 it still might be desirable to add test api to set visibility state in DumpRenderTreeSupportGtk and new InjectedBundlePageSetVisibilityClient APi in WebKit2. What do you think?
-----Original Message----- From: martin.james.robin...@gmail.com [mailto:martin.james.robin...@gmail.com] On Behalf Of Martin Robinson Sent: 28 January 2013 15:36 To: Anton Obzhirov Cc: webkit-gtk@lists.webkit.org Subject: Re: [webkit-gtk] Bug 97324 - [GTK] Add support for Page Visibility On Mon, Jan 28, 2013 at 3:27 AM, Anton Obzhirov <a.obzhi...@samsung.com> wrote: > Do I need to implement WebKit1 GTK API as well – to un skip page > visibility tests in layout tests for example? You don't have to add WebKit1 API. You might consider not adding API at all though and tying it directly to GTK+ widget visibility. This might make the integration into WKTR/DumpRenderTree harder, but would probably be more natural for people making applications. --Martin _______________________________________________ webkit-gtk mailing list webkit-gtk@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-gtk
