Element Interaction

The click target is covered: another element sits over its centre point and would receive the click. The driver's message names that intercepting element, usually its opening tag with id and class, so read it.

Selenium runs the string as the body of an anonymous function in the current frame, so you need an explicit return to get a value; without one you get null. Values passed after the script appear as arguments[0], arguments[1].

Selenium's Select class offers selectByVisibleText, which matches an option's rendered text; selectByValue, which matches its value attribute exactly; and selectByIndex, which matches its zero-based position. Each throws NoSuchElementException when nothing matches.

You may pass numbers, booleans, strings, WebElements, and lists or String-keyed maps of those; anything else throws IllegalArgumentException. Results come back as Boolean, Long, Double, String, List, Map, WebElement or null, and always need a cast.

Selenium's Select constructor reads the element's tag name and accepts only a select tag. A styled listbox made of div and span elements has no option children and no multiple attribute, so the wrapper rejects it at construction.

The field lives as long as the page object while the node lives only until the next re-render. The constructor mints one reference, so the first redraw kills that field for the rest of the object's life.

A re-render detaches one node while the document stays live, so re-finding on the same page works. A navigation replaces the whole document, so every earlier reference dies at once and only the new page can supply one.

getDomAttribute reads the value the page's HTML declared. getDomProperty reads the element's live DOM property, so it sees what the user typed or ticked. getAttribute is the older combined call: it prefers the property and falls back to the attribute.

Selenium's Actions never releases a modifier for you. A keyDown with no matching keyUp leaves the key depressed in the driver's input state, which outlives the chain and any new Actions object. Release it with keyUp, sendKeys(Keys.NULL), or resetInputState.

Read the interceptor's tag out of the message, then find that element in the application and ask why it was there at that moment. Its identity separates fixed page chrome, a leftover toast, and an open dialog.

Selecting by text or value stops selecting every match instead of just the first, the whole deselect family becomes legal, and isMultiple reports true. Selenium's Select reads that attribute once, in the constructor, and caches the answer.

The instance is bound to one reference the browser has already declared dead, and Selenium documents that all future calls on it fail. Recovery needs a new lookup, and a repeated write needs proof the first one did not land.

It runs a bundled Selenium script that approximates visibility by walking the element tree: display none, visibility hidden, zero opacity, zero size and unscrollable overflow all make it false. The W3C specification only recommends this approach in an appendix.

Click the real control by default, press Enter when the case covers the keyboard journey, and avoid submit. In Selenium 4 submit runs an injected script, so it skips every scroll and interactability check the click command performs.

Treat it as a semantic audit, not a rename. Group call sites by the name being read, move markup-only names first, turn boolean flags into isSelected and isEnabled, change live-value reads last, then ban the old call.

Find the input type=file element and send it the file's absolute path with sendKeys. Selenium sets the file directly on the input and never opens or drives the operating system's file-chooser dialog.

It means the node that handle points at is no longer part of the page the browser is showing. Selenium re-checks the reference before every element command, so that handle is dead and the element has to be found again.

Actions collects each step into a per-device sequence, and perform() posts them all as one WebDriver actions command. Steps sharing a tick run together across devices, and the browser waits for that tick's longest duration before the next one.

It calls scrollIntoView with instant behaviour, block end and inline nearest, so the bottom of the element is aligned with the bottom of the viewport. It skips the scroll when the element is already in view.

Send Keys never resets the field. When the input is not already focused the driver focuses it and puts the caret after the existing text, then types character by character, so the new characters land on the end.

Interception means something is painted over the target. Not-interactable means the target itself cannot be reached at all: not rendered, not scrollable into view, or not focusable for typing. In Selenium 4 the intercepted class extends the not-interactable one.

It clicks the option element. Selenium's Select checks the option is enabled, compares its current selectedness with the state you asked for, and clicks only when they differ, so re-selecting an already-chosen option sends nothing at all.

Because it returns rendered text, not markup text. Anything the browser did not draw contributes nothing, so an element hidden by display none or visibility hidden yields an empty string even though its characters are in the page.

Clear resets the value through the HTML clear algorithm and dispatches no key events at all. A component that keeps its own copy of the field's value and updates it from typing can miss the reset, so its copy stays stale.

Selenium clicks the in-view centre point: the centre of the intersection between the element's first client rectangle and the viewport, floored to whole pixels. Whatever is painted at that one coordinate receives the click.

Java's RemoteWebDriver starts with a UselessFileDetector, so sendKeys forwards your local path as plain text and the browser's own machine has no such file. Call setFileDetector with a LocalFileDetector so the client ships the file first.

Element Click scrolls the target into view before acting; a pointer move does not. Actions computes the element's in-view centre point plus your offsets and fails when the result lands outside the viewport.

The injected click fires straight at the node, so it works even when a banner covers the button or the button is invisible. The test goes green while a real user, whose pointer hits whatever sits on top, cannot submit.

getOptions runs a fresh search for the select's option elements and returns a snapshot list, not a live collection. getAllSelectedOptions filters that list by asking each option whether it is selected, so it costs one find plus one command per option.