id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
26048	Switch selenium tests to use implicitly_wait() instead of custom wait functions.	Tim Graham	Tim Graham	"From the selenium docs, ""Dependent on several factors, including the OS/Browser combination, WebDriver may or may not wait for the page to load. In some circumstances, WebDriver may return control before the page has finished, or even started, loading. To ensure robustness, you need to wait for the element(s) to exist in the page using [http://docs.seleniumhq.org/docs/04_webdriver_advanced.jsp#explicit-and-implicit-waits-reference Explicit and Implicit Waits].""

Currently, we have a collection of [https://github.com/django/django/blob/7f7553dd30534d606c84952a3f6dcb64b396ce37/django/contrib/admin/tests.py#L49-L120 wait_for*] methods to accomplish this. The idea is to switch our code to call `self.selenium.implicitly_wait(10)` after initializing `self.selenium` which should allow us to remove many of these waiting calls."	Cleanup/optimization	closed	contrib.admin	dev	Normal	fixed		Florian Apolloner	Accepted	1	0	0	0	0	0