Difference between focus and blur in fireevent - selenium

What is the difference between focus and blur in fireEvent of Selenium?
Kindly,help.
In which situations do we use it?

This is not a Selenium specific question...
The focus event is fired when an element gains focus.
The blur event is fired when an element loses focus.

Related

Blur on clear all values with React-Select

Does anyone know how to blur the element after the clear all values has been clicked?
There isn't a prop that allows me to capture the clear all click except for the onChange.
The clear all method calls focus and overrides my blur unless I timeout for 600+ seconds and then call blur...but there has to be a better way.
thanks

When using Selenium's click_and_hold method exactly what conditions or actions cause the mouse click to release?

I've had several occasions in my selenium tests where I decided to use Selenium's click_and_hold() (source code here) method on some element. The source code makes it look like it will stay pressed indefinitely but there are definitely some actions, such as a simple click, that cause the held click to be released. Obviously calling release will release the held click too, but does anyone have a grasp on exactly what actions/conditions (either from the script or the page itself) will cause the held click to be released?
I've linked to the documentation for the python bindings, but I assume this would be the same no matter what language is used to write the script. Please let me know if this assumption is incorrect!
release()
release(on_element) releases a held mouse button on an element. If on_element is None releases on current mouse position which is defined as:
def release(self, on_element=None):
"""
Releasing a held mouse button on an element.
:Args:
- on_element: The element to mouse up.
If None, releases on current mouse position.
"""
if on_element:
self.move_to_element(on_element)
if self._driver.w3c:
self.w3c_actions.pointer_action.release()
self.w3c_actions.key_action.pause()
else:
self._actions.append(lambda: self._driver.execute(Command.MOUSE_UP, {}))
return self
release() is invoked by default by different methods of the ActionChains implementation. Some of them are as follows:
release(): Releasing a held mouse button on an element.
drag_and_drop(source, target): Holds down the left mouse button on the source element, then moves to the target element and releases the mouse button.
drag_and_drop_by_offset(source, xoffset, yoffset): Holds down the left mouse button on the source element, then moves to the target offset and releases the mouse button.
click_and_hold()
click_and_hold() holds down the left mouse button on an element.
So you saw it right, the source code confirms the same that it will stay pressed indefinitely unless release() is directly invoked or invoked through other methods. However there can be other actions / events which may cause the hold down left mouse button to be released implicitly. These actions / events can be a result of any of the HTML DOM Events. HTML DOM events allow JavaScript / AjaxCalls to register different event handlers on elements in an HTML document. Some of the mostly encountered events are:
HTML DOM UiEvent: Events that are triggered from the user interface belongs to the UiEvent Object.
onload Event: The onload event occurs when an object has been loaded.
onresize Event: The onresize event occurs when the browser window has been resized.
onscroll Event: The onscroll event occurs when an element's scrollbar is being scrolled.
HTML DOM FocusEvent: Events that occur when elements gets or loses focus, belongs to the FocusEvent Object.
onblur Event: The event occurs when an element loses focus
onfocus Event: The event occurs when an element gets focus
onfocusin Event: The event occurs when an element is about to get focus
onfocusout Event: The event occurs when an element is about to lose focus
The Event Object: All event objects in the DOM are based on the Event Object.
onchange Event: The onchange event occurs when the value of an element has been changed.
HTML DOM MouseEvent: Events that occur when the mouse interacts with the HTML document belongs to the MouseEvent Object.
onmousedown Event: The onmousedown event occurs when a user presses a mouse button over an element.
onmouseup Event: The onmouseup event occurs when a user releases a mouse button over an element.
HTML DOM DragEvent: Events that occur when elements are dragged and/or dropped, belongs to the DragEvent Object.
ondrag Event: The ondrag event occurs when an element or text selection is being dragged.
ondragstart Event: The ondragstart event occurs when the user starts to drag an element or text selection.
HTML DOM TransitionEvent: Events that occur when a CSS transition runs, belongs to the TransitionEvent Object.
transitionend Event: The event occurs when a CSS transition has completed
key_up()
The key_up() method also releases a modifier key. As an example:
ActionChains(driver).key_down(Keys.CONTROL).send_keys('c').key_up(Keys.CONTROL).perform()
This usecase
Without any visibility to your usecase of implementing click_and_hold() it is to be noted that, key_down() is a method which performs a modifier key press and it does not release the modifier key and subsequent interactions may assume it's kept pressed. Note that the modifier key is never released implicitly. Either key_up(theKey) or send_keys(Keys.NULL) must be called to release the modifier.
Generally any action that results in a mouse up event being called.
Click will call a mouse down event and then a mouse up event (As shown in the Code)
Click_and_hold() will only perform the mouse down part. If you then call anything else that triggers the mouse up event, the mouse click will be released.
Remember selenium is just passing a list of actions over to the driver binary that is controlling the browser using the JSON wire protocol. The commands you use in code are translated into JavaScript actions before being passed over the wire so the driver binary controlling the browser probably doesn't have much in the way of context of exactly what the original commands before they were broken down were.

How to set focus to Grid UIElement in winrt?

A Grid UIElement in winrt is receiving the GotFocus and LostFocus events, which are useful - but apparently Focus() is not a method available to Grid. How can the element be capable of having focus but not be capable of setting it? I am trying to restore keyboard focus to the main Grid of the app's UI when it is lost due to other interactions. Does anyone know how one might programmatically restore focus to a Grid that has just reported losing it? Thanks.

How to delay the disappearance of elementui tooltip components,

I used the elementui tooltip component, and I saw that only delayed display by 'open-delay', how to make it delay disappear
Have you tried hide-after property ? Here is an example : https://jsfiddle.net/budgw/58mdw0et/
If you want to delay when the mouse leaves the element, first use the manual property on el-tooltip. Then use mousenter and mouseleave envents (in case of an el-button) to show/hide the tooltip. You can use for example debounce method from lodash in order to delay the hide method. Here is a jsfiddle : https://jsfiddle.net/budgw/qrt3pbqm/
Hope it helps.

How to pass MouseMoved event to WebView content?

We are using the webview control in a WinRT XAML app. The problem we are facing is that MouseMove event is not passed to the html when using touch, while it is normally passed when using mouse.
When using touch the events passed during touch-move-release are:
MouseDown
MouseUp
while with mouse they are:
MouseDown
MouseMove
MouseUp
Is there a way to solve this problem?