org.safs.selenium.webdriver.lib

Class Component.EmbeddedObject

java.lang.Object

org.safs.selenium.webdriver.lib.Component.EmbeddedObject

All Implemented Interfaces:

Component.Supportable

Direct Known Subclasses:

CheckBox.AbstractCheckable, ComboBox.HtmlSelect, TabControl.AbstractTabbable

Enclosing class:

Component

protected abstract class Component.EmbeddedObject
extends java.lang.Object
implements Component.Supportable

Field Summary

Fields

Modifier and Type	Field and Description
protected WebElement	element The embedded WebElement object. This element may become stale, see stale_element If the element is stale, we need to refresh it by getting it again (by id or css or other ways)

Constructor Summary

Constructors

Constructor and Description
Component.EmbeddedObject(WebElement element)

Method Summary

Methods

Modifier and Type	Method and Description
void	refresh(boolean checkStale) A stale element reference exception is thrown in one of two cases, the first being more common than the second: 1.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface org.safs.selenium.webdriver.lib.Component.Supportable

getSupportedClassNames, isSupported

Field Detail

element

protected WebElement element

The embedded WebElement object.
This element may become stale, see stale_element
If the element is stale, we need to refresh it by getting it again (by id or css or other ways)

See Also:

#refresh()

Constructor Detail

Component.EmbeddedObject

public Component.EmbeddedObject(WebElement element)
                         throws SeleniumPlusException

Throws:

SeleniumPlusException

Method Detail

refresh

public void refresh(boolean checkStale)

A stale element reference exception is thrown in one of two cases, the first being more common than the second:
1. The element has been deleted entirely.
The most frequent cause of this is that page that the element was part of has been refreshed,
or the user has navigated away to another page. A less common, but still common cause is
where a JS library has deleted an element and replaced it with one with the same ID or attributes.
In this case, although the replacement elements may look identical they are different;
the driver has no way to determine that the replacements are actually what's expected.
2. The element is no longer attached to the DOM.

If some native javascript APIs are called, the web element may become stale. In this case, this
refresh() method needs to be called.

Parameters:

checkStale - boolean, if true then check if the element is stale or not before refresh; ohterwise, then refresh the element directly. The check will spend some time, if you don't want to waste time, use false.