IUIAutomation6::RemoveActiveTextPositionChangedEventHandler method (uiautomationclient.h)
Removes an active text position changed event handler.
Microsoft UI Automation clients should use the IUIAutomationEventHandlerGroup interface methods to register event listeners instead of individual event registration methods defined here and in the various IUIAutomation interface namespaces.
HRESULT RemoveActiveTextPositionChangedEventHandler( IUIAutomationElement *element, IUIAutomationActiveTextPositionChangedEventHandler *handler );
A pointer to the UI Automation element associated with the event handler.
A pointer to the object that handles the active text position changed event.
This method does not return a value.
Before implementing an event handler, you should be familiar with the threading issues described in Understanding Threading Issues.
Active text position is indicated by a navigation event within or between read-only text elements (such as web browsers, Portable Document Format (PDF) documents, or EPUB documents) using bookmarks (or fragment identifiers to refer to a location within a resource). Examples include:
- Navigating to a bookmark within the same web page
- Navigating to a bookmark on a different web page
- Activating a link to a different location within the same PDF
- Activating a link to a different location within the same EPUB
Use this event handler to sync the visual location of the bookmark/target with the focus location in a read-only text element, which can diverge when using bookmarks or fragment identifiers.
For example, when a same page anchor (
<a href="#C4">Jump to Chapter 4</a> ...<h1><a name="C4">Chapter 4</a></h1>) is invoked, the visual location is updated, but the UI Automation client remains at the original location. This results in actions such as text reading or move next item commands starting from the original location, not the new location.
Similarly, activating a new page URI (with a fragment identifier: (
<a href="www.blah.com#C4">Jump to Chapter 4</a>) loads the new page and jumps to the specified bookmark, but leaves the UI Automation clients at the top of the page.
It is possible for an event to be delivered to an event handler after the handler has been unsubscribed, if the event is received simultaneously with the request to unsubscribe the event. The best practice is to follow the Component Object Model (COM) standard and avoid destroying the event handler object until its reference count has reached zero. Destroying an event handler immediately after unsubscribing for events may result in an access violation if an event is delivered late.
|Minimum supported client||Windows 10, version 1809 [desktop apps only]|
|Minimum supported server||Windows Server, version 1709 [desktop apps only]|
|Header||uiautomationclient.h (include UIAutomation.h)|