1/************************************************************** 2 * 3 * Licensed to the Apache Software Foundation (ASF) under one 4 * or more contributor license agreements. See the NOTICE file 5 * distributed with this work for additional information 6 * regarding copyright ownership. The ASF licenses this file 7 * to you under the Apache License, Version 2.0 (the 8 * "License"); you may not use this file except in compliance 9 * with the License. You may obtain a copy of the License at 10 * 11 * http://www.apache.org/licenses/LICENSE-2.0 12 * 13 * Unless required by applicable law or agreed to in writing, 14 * software distributed under the License is distributed on an 15 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 16 * KIND, either express or implied. See the License for the 17 * specific language governing permissions and limitations 18 * under the License. 19 * 20 *************************************************************/ 21 22 23 24#ifndef __com_sun_star_xml_dom_events_EventType_idl__ 25#define __com_sun_star_xml_dom_events_EventType_idl__ 26 27module com { module sun { module star { module xml { module dom { module events { 28 29enum EventType 30{ 31 DOMFocusIn, 32 /* 33 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. 34 * Bubbles: Yes 35 * Cancelable: No 36 * Context Info: None 37 */ 38 39 DOMFocusOut, 40 /* 41 The DOMFocusOut event occurs when a 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. 42 * Bubbles: Yes 43 * Cancelable: No 44 * Context Info: None 45 */ 46 47 DOMActivate, 48 /* 49 The activate event occurs when an element is activated, for instance, thru a mouse click or a keypress. 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 hyperactivation (for instance a double click or Shift Enter). 50 * Bubbles: Yes 51 * Cancelable: Yes 52 * Context Info: detail (the numerical value) 53 */ 54 55 click, 56 /* 57 The click event occurs when the pointing device button is clicked over an element. 58 A click is defined as a mousedown and mouseup over the same screen location. 59 The sequence of these events is: 60 61 mousedown 62 mouseup 63 click 64 65 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. 66 67 * Bubbles: Yes 68 * Cancelable: Yes 69 * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, button, detail 70 */ 71 72 mousedown, 73 /* 74 The mousedown event occurs when the pointing device button is pressed over an element. This event is valid for most elements. 75 * Bubbles: Yes 76 * Cancelable: Yes 77 * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, button, detail 78 */ 79 80 mouseup, 81 /* 82 The mouseup event occurs when the pointing device button is released over an element. This event is valid for most elements. 83 * Bubbles: Yes 84 * Cancelable: Yes 85 * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, button, detail 86 */ 87 88 mouseover, 89 /* 90 The mouseover event occurs when the pointing device is moved onto an element. This event is valid for most elements. 91 * Bubbles: Yes 92 * Cancelable: Yes 93 * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, relatedTarget indicates the EventTarget the pointing device is exiting. 94 */ 95 96 mousemove, 97 /* 98 The mousemove event occurs when the pointing device is moved while it is over an element. This event is valid for most elements. 99 * Bubbles: Yes 100 * Cancelable: No 101 * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey 102 */ 103 104 mouseout, 105 /* 106 The mouseout event occurs when the pointing device is moved away from an element. This event is valid for most elements.. 107 * Bubbles: Yes 108 * Cancelable: Yes 109 * Context Info: screenX, screenY, clientX, clientY, altKey, ctrlKey, shiftKey, metaKey, relatedTarget indicates the EventTarget the pointing device is entering. 110 */ 111 112 DOMSubtreeModified, 113 /* 114 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. 115 * Bubbles: Yes 116 * Cancelable: No 117 * Context Info: None 118 */ 119 120 DOMNodeInserted, 121 /* 122 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. 123 * Bubbles: Yes 124 * Cancelable: No 125 * Context Info: relatedNode holds the parent node 126 */ 127 128 DOMNodeRemoved, 129 /* 130 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. 131 * Bubbles: Yes 132 * Cancelable: No 133 * Context Info: relatedNode holds the parent node 134 */ 135 136 DOMNodeRemovedFromDocument, 137 /* 138 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. 139 * Bubbles: No 140 * Cancelable: No 141 * Context Info: None 142 */ 143 144 DOMNodeInsertedIntoDocument, 145 /* 146 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. 147 * Bubbles: No 148 * Cancelable: No 149 * Context Info: None 150 */ 151 152 DOMAttrModified, 153 /* 154 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. 155 * Bubbles: Yes 156 * Cancelable: No 157 * Context Info: attrName, attrChange, prevValue, newValue, relatedNode 158 */ 159 160 DOMCharacterDataModified 161 /* 162 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. 163 * Bubbles: Yes 164 * Cancelable: No 165 * Context Info: prevValue, newValue 166 */ 167}; 168}; }; }; }; }; }; 169 170#endif 171