LibreOffice
LibreOffice 24.2 SDK API Reference
EventType.idl
Go to the documentation of this file.
1 /* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
2 /*
3  * This file is part of the LibreOffice project.
4  *
5  * This Source Code Form is subject to the terms of the Mozilla Public
6  * License, v. 2.0. If a copy of the MPL was not distributed with this
7  * file, You can obtain one at http://mozilla.org/MPL/2.0/.
8  *
9  * This file incorporates work covered by the following license notice:
10  *
11  * Licensed to the Apache Software Foundation (ASF) under one or more
12  * contributor license agreements. See the NOTICE file distributed
13  * with this work for additional information regarding copyright
14  * ownership. The ASF licenses this file to you under the Apache
15  * License, Version 2.0 (the "License"); you may not use this file
16  * except in compliance with the License. You may obtain a copy of
17  * the License at http://www.apache.org/licenses/LICENSE-2.0 .
18  */
19 
20 module com { module sun { module star { module xml { module dom { module events {
21 
23 {
25  /*
26  The DOMFocusIn event occurs when an EventTarget receives focus, for instance via a pointing device being moved onto an element or by tabbing navigation to the element. Unlike the HTML event focus, DOMFocusIn can be applied to any focusable EventTarget, not just FORM controls.
27  * Bubbles: Yes
28  * Cancelable: No
29  * Context Info: None
30  */
31 
33  /*
34  The DOMFocusOut event occurs when an EventTarget loses focus, for instance via a pointing device being moved out of an element or by tabbing navigation out of the element. Unlike the HTML event blur, DOMFocusOut can be applied to any focusable EventTarget, not just FORM controls.
35  * Bubbles: Yes
36  * Cancelable: No
37  * Context Info: None
38  */
39 
41  /*
42  The activate event occurs when an element is activated, for instance, through a mouse click or a key press. A numerical argument is provided to give an indication of the type of activation that occurs: 1 for a simple activation (e.g. a simple click or Enter), 2 for hyper activation (for instance a double click or Shift Enter).
43  * Bubbles: Yes
44  * Cancelable: Yes
45  * Context Info: detail (the numerical value)
46  */
47 
49  /*
50  The click event occurs when the pointing device button is clicked over an element.
51  A click is defined as a mousedown and mouseup over the same screen location.
52  The sequence of these events is:
53 
54  mousedown
55  mouseup
56  click
57 
58  If multiple clicks occur at the same screen location, the sequence repeats with the detail attribute incrementing with each repetition. This event is valid for most elements.
59 
60  * Bubbles: Yes
61  * Cancelable: Yes
62  * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, button, detail
63  */
64 
66  /*
67  The mousedown event occurs when the pointing device button is pressed over an element. This event is valid for most elements.
68  * Bubbles: Yes
69  * Cancelable: Yes
70  * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, button, detail
71  */
72 
74  /*
75  The mouseup event occurs when the pointing device button is released over an element. This event is valid for most elements.
76  * Bubbles: Yes
77  * Cancelable: Yes
78  * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, button, detail
79  */
80 
82  /*
83  The mouseover event occurs when the pointing device is moved onto an element. This event is valid for most elements.
84  * Bubbles: Yes
85  * Cancelable: Yes
86  * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, relatedTarget indicates the EventTarget the pointing device is exiting.
87  */
88 
90  /*
91  The mousemove event occurs when the pointing device is moved while it is over an element. This event is valid for most elements.
92  * Bubbles: Yes
93  * Cancelable: No
94  * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey
95  */
96 
98  /*
99  The mouseout event occurs when the pointing device is moved away from an element. This event is valid for most elements...
100  * Bubbles: Yes
101  * Cancelable: Yes
102  * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, relatedTarget indicates the EventTarget the pointing device is entering.
103  */
104 
106  /*
107  This is a general event for notification of all changes to the document. It can be used instead of the more specific events listed below. It may be fired after a single modification to the document or, at the implementation's discretion, after multiple changes have occurred. The latter use should generally be used to accommodate multiple changes which occur either simultaneously or in rapid succession. The target of this event is the lowest common parent of the changes which have taken place. This event is dispatched after any other events caused by the mutation have fired.
108  * Bubbles: Yes
109  * Cancelable: No
110  * Context Info: None
111  */
112 
114  /*
115  Fired when a node has been added as a child of another node. This event is dispatched after the insertion has taken place. The target of this event is the node being inserted.
116  * Bubbles: Yes
117  * Cancelable: No
118  * Context Info: relatedNode holds the parent node
119  */
120 
122  /*
123  Fired when a node is being removed from its parent node. This event is dispatched before the node is removed from the tree. The target of this event is the node being removed.
124  * Bubbles: Yes
125  * Cancelable: No
126  * Context Info: relatedNode holds the parent node
127  */
128 
130  /*
131  Fired when a node is being removed from a document, either through direct removal of the Node or removal of a subtree in which it is contained. This event is dispatched before the removal takes place. The target of this event is the Node being removed. If the Node is being directly removed the DOMNodeRemoved event will fire before the DOMNodeRemovedFromDocument event.
132  * Bubbles: No
133  * Cancelable: No
134  * Context Info: None
135  */
136 
138  /*
139  Fired when a node is being inserted into a document, either through direct insertion of the Node or insertion of a subtree in which it is contained. This event is dispatched after the insertion has taken place. The target of this event is the node being inserted. If the Node is being directly inserted the DOMNodeInserted event will fire before the DOMNodeInsertedIntoDocument event.
140  * Bubbles: No
141  * Cancelable: No
142  * Context Info: None
143  */
144 
146  /*
147  Fired after an Attr has been modified on a node. The target of this event is the Node whose Attr changed. The value of attrChange indicates whether the Attr was modified, added, or removed. The value of relatedNode indicates the Attr node whose value has been affected. It is expected that string based replacement of an Attr value will be viewed as a modification of the Attr since its identity does not change. Subsequently replacement of the Attr node with a different Attr node is viewed as the removal of the first Attr node and the addition of the second.
148  * Bubbles: Yes
149  * Cancelable: No
150  * Context Info: attrName, attrChange, prevValue, newValue, relatedNode
151  */
152 
154  /*
155  Fired after CharacterData within a node has been modified but the node itself has not been inserted or deleted. This event is also triggered by modifications to PI elements. The target of this event is the CharacterData node.
156  * Bubbles: Yes
157  * Cancelable: No
158  * Context Info: prevValue, newValue
159  */
160 };
161 }; }; }; }; }; };
162 
163 /* vim:set shiftwidth=4 softtabstop=4 expandtab: */
Definition: EventType.idl:73
Definition: Ambiguous.idl:20
EventType
Definition: EventType.idl:22
Definition: EventType.idl:48
Definition: EventType.idl:97