Searched refs:dragover (Results 1 - 7 of 7) sorted by relevance
/external/chromium_org/third_party/WebKit/Source/core/dom/ |
H A D | GlobalEventHandlers.h | 53 DEFINE_STATIC_ATTRIBUTE_EVENT_LISTENER(dragover);
|
/external/chromium_org/third_party/WebKit/Source/core/svg/ |
H A D | SVGElementInstance.cpp | 70 DEFINE_FORWARDING_ATTRIBUTE_EVENT_LISTENER(SVGElementInstance, correspondingElement(), dragover);
|
H A D | SVGElementInstance.h | 129 DECLARE_FORWARDING_ATTRIBUTE_EVENT_LISTENER(correspondingElement(), dragover); member in class:WebCore::SVGElementInstance
|
/external/chromium_org/third_party/WebKit/Source/core/events/ |
H A D | MouseEvent.cpp | 175 return t == EventTypeNames::dragenter || t == EventTypeNames::dragover || t == EventTypeNames::dragleave || t == EventTypeNames::drop
|
/external/chromium_org/third_party/WebKit/Source/core/html/ |
H A D | HTMLElement.cpp | 247 attributeNameToEventNameMap.set(ondragoverAttr.localName(), EventTypeNames::dragover);
|
/external/chromium_org/third_party/WebKit/Source/web/ |
H A D | WebPluginContainerImpl.cpp | 723 else if (event->type() == EventTypeNames::dragover)
|
/external/chromium_org/third_party/WebKit/Source/core/page/ |
H A D | EventHandler.cpp | 1836 // As per section 7.9.4 of the HTML 5 spec., we must always fire a drag event before firing a dragenter, dragleave, or dragover event. 1854 // two dragover events fired. So, we mark that we should only fire a dragover event on the next call to this function. 1863 // Note, when dealing with sub-frames, we may need to fire only a dragover event as a drag event may have been fired earlier. 1868 accept = dispatchDragEvent(EventTypeNames::dragover, newTarget.get(), event, clipboard);
|
Completed in 274 milliseconds