Committers Panel
summary
Committers explain how bugs get fixed: prioritize issues with include a minimal test case and stars, volunteers fix what they hit, bribery helps rarely; file downloads and OS dialogs are offloaded to HTTP clients or Firefox prefs; Shadow DOM planned via WebDriver W3C spec, CSS transforms and animations create timing headaches; stale element errors come from DOM replacements so wait for staleness or re-find elements; Grid runs on the JVM (Linux common), language choice follows team skills, and a W3C face‑to‑face is scheduled to push the spec forward.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:05Committers panel intro
- 3:35Bug fix decisions in Selenium
- 7:11Page Factory strategies
- 8:35Start contributing to Selenium
- 9:57SVG automation with CSS
- 13:16jQuery selectors future
- 15:45WebDriver file downloads
- 19:38Shadow DOM handling
- 25:22ID lookup performance
- 27:09WebDriver hover/drag limits
- 29:16Conference resources
- 30:18Avoiding useless Selenium tests
- 32:27Flaky test handling
- 36:00Safari driver status
- 36:43Timeout behavior quirks
- 37:46Stale element exceptions
- 44:11WebElement locator access
- 46:42Modifying tests for redesigns
- 48:26Custom vs JUnit/TestNG
- 51:24Right language for bindings
- 56:44Dynamic element handling
- 58:31Boston Meetup update
- 1:01:19Proxy objects for requests
- 1:03:50Selenium Grid on Windows
- 1:05:58Closing remarks
- 1:06:19W3C WebDriver update
