Scott Babcock

To add this information to **every** resource would indeed be a huge task, but to tackle this for a few truly useful resources like `xml` would be helpful in many...

This is almost certainly a transitive dependency problem. For my own project, I exclude all of the drivers brought in by `selenium-server` to avoid the potential conflicts: ``` org.seleniumhq.selenium selenium-server...

The existing documentation includes descriptions of many of the settings interspersed within the text, but there's no single comprehensive list of available settings. The page I'm visualizing here will document...

To clarify, the issue here is that collections can represent elements that no longer exist, or that collections will fail to represent elements that have appeared since the collection was...

It may be sufficient to repopulate collections whenever element references they contain go stale. The current behavior merely refreshes existing references as they are used, ignoring the larger implications of...

The methods used to retrieve elements from collections would need to perform the check for referential integrity, rebuilding the collection if a stale reference is detected. Each item in the...

I don't know for certain, but I think the code needed to rebuild collections would just need to be extracted from the constructors for `ContainerList` and `ContainerMap`. These would be...

Another thing to consider is how to handle map entries that no longer exist. These should probably throw **StaleElementReferenceException** for entries that once existed but no longer do after the...

I'm not sure that this issue is solvable for component lists, save to determine that the size of the collection has changed. The reason is that the component container element...

Collection integrity checks will be performed when we switch to the search context of a member of a collection. If the size of the list or the composition of the...