Issue 239 in robotframework-seleniumlibrary: Document that keywords Element Should (Not) Be Visible do not work with Chrome in Windows

[robotframework-...@googlecode.com]

Status: Accepted
Owner: robotfr...@gmail.com
Labels: Type-Documentation Target-2.10 Priority-Medium

New issue 239 by robotfr...@gmail.com: Document that keywords Element
Should (Not) Be Visible do not work with Chrome in Windows
http://code.google.com/p/robotframework-seleniumlibrary/issues/detail?id=239

We discovered in our acceptance tests that the mentioned keywords fail in
Windows, and in some cases inflict significant resource usage for the rest
of the test run (CPU consumption of the server process jumps to ~100 after
either of these keywords is run)

The keywords themselves do not seem to work even with older versions of
selenium-server, so we are just going to document this behavior.

[robotframework-...@googlecode.com]

Updates:
Status: Invalid
Owner: ---
Labels: -Target-2.10

Comment #1 on issue 239 by pekka.klarck: Document that keywords Element

Should (Not) Be Visible do not work with Chrome in Windows
http://code.google.com/p/robotframework-seleniumlibrary/issues/detail?id=239

The problem was actually caused by our test data that didn't work too well
with Chrome on Windows. visibility.html file didn't contain content type
information and for some reason that caused Chrome to hang. Not sure was
the reason in our test infra (perhaps the test server sends conflicting
content type) but adding the content type to the file fixed the problem.
The visibility keywords started to work and tests executed much faster than
earlier.