[Webkit-unassigned] [Bug 72708] New: [GTK] Accessibility API tests failing because of using non-WebKit GtkWidgets

[bugzilla-daemon at webkit.org]

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

           Summary: [GTK] Accessibility API tests failing because of using
                    non-WebKit GtkWidgets
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Keywords: Gtk
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: msanchez at igalia.com


The ATK unit tests testWebkitAtkParentForRootObject() and testWebkitAtkSetParentForObject() has been failing in the bots lately and it seems it's because they are the only one using GtkWidget's not provided by WebKit (GtkWindow and GtkBox), so when the test asks for the AtkObject's associated to them (through gtk_widget_get_accessible()) the returned object is not the expected one, but a dummy AtkNoOpObject, since the accessibility implementation of Gtk is not being loaded along with the tests.

And this results on errors like this:

  TEST: /home/slave/webkitgtk/gtk-linux-64-debug/build/WebKitBuild/Debug/Programs/unittests/testatk... (pid=25379)
  **
  ERROR:../../Source/WebKit/gtk/tests/testatk.c:1629:testWebkitAtkParentForRootObject: assertion failed: (axBoxChild)

One possible solution is to only use GtkWidget's provided by WebKitGTK+ instead of GtkWindow and GtkBox, to use them as parent containers. And this is a very good option since WebKitWebView widget inherits from GtkContainer, so that makes it suitable for that task.

Will attach a patch soon.

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