SeleniumHQ / SeleniumHQ/htmlunit-driver
Threading problem when using multiple frames
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 266
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
Concurrent access when using iframes.
The same error described here for firefox happens with htmlunit-driver:
https://bugzilla.mozilla.org/show_bug.cgi?id=1833637
and here
https://github.com/gwtproject/gwt/pull/9800
The proposed bugfix for GWT works, but the problem seems to be deeper in the Thread handling of the browser engine, allowing 2 threads to run simultaneously.
Chromium based browsers don't show the problem.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the concurrent iframe behavior described here with Mozilla Bugzilla 1833637 and GWT pull request 9800. Reproduce the problem using htmlunit-driver with multiple threads and frames, then trace the browser engine's thread handling. Done means concurrent frame access no longer permits unsafe simultaneous execution while Chromium behavior remains unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100