[Webkit-unassigned] [Bug 25831] New: [GTK] events missing when a document is (re)loaded

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 15 21:08:53 PDT 2009


           Summary: [GTK] events missing when a document is (re)loaded
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Accessibility
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: joanmarie.diggs at gmail.com
                CC: xan.lopez at gmail.com, William.Walker at sun.com,
                    apinheiro at igalia.com

When a document is (re)loaded, the following events should be emitted:

1) object:state-changed:busy with detail1 == 1

2) document:reload (Only if the existing document is being reloaded.)

.....page contents change.....

3) document:load-complete or document:load-stopped

4) object:state-changed:busy with detail1 == 0

See http://library.gnome.org/devel/atk/unstable/AtkDocument.html

In addition, the current implementation of WebKit replaces the top level object
(ROLE_DOCUMENT_FRAME) with a new object when a page is loaded. When this
occurs, it would be helpful if the following events were emitted:

1) object:state-changed:defunct emitted by the top level object/document frame
only (i.e. This event should NOT be emitted for all of the AtkObjects from the
old page as that will potentially bombard ATs with too many events.)

2) object:children-changed:remove emitted by the parent (ROLE_SCROLL_PANE) of
the top level object.

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

More information about the webkit-unassigned mailing list