Some special cases not handled correctly when resolving URLs
First of all, thanks for the quick fix, Ronald! With respect to BrowserVersion, I agree that probably no one will really need to customize the setup of a certain browser version except for the header configuration. It may even be advantageous to make BrowserVersion immutable (solves the issue of BrowserVersion as map key). But then the header customization must be possible elsewhere, for example in WebClientOptions. This is of course a breaking change and maybe there is another way. But whatever...
I noticed that BrowserVersion objects are also used as key in hash maps. So messing around with the writable fields of BrowserVersion may lead to undesired effects, such as entries not found or creating additional entries for each modification. Not sure if resorting to the base browser type (nick) as key would be a solution.
Added test case.
Wrong JS engine setup in case of modified browser version
Dafür sind wir doch da ... ;-)
See also the attached patch that adds some test cases and tries to fix this issue.
Base URL may be wrong
Parsing invalid numeric character references may fail the page load
Double-checked this once again. Yes, I do use 2.26 release (unless Maven fools me)....
Can't select multiple options in a multi-select
A quick-fix could be to add a similar special handling for CSS resources as it already...
HtmlUnit does no longer process CSS files read from a file URL
Basic authentication credentials in the URL could get lost
Processing base URLs with leading whitespace fails
Unquoted cookie value is sent back quoted
Strange. I simply replaced PUT with POST in the isPreflight() methods in the latest...
CORS: check for simple request methods wrong
I see the need for PATCH as well. More and more companies design their web services...
Element lookup by CSS class name does not always work
Looks really good. Cheers!
The test is green now, thanks. I have a couple of remarks regarding your changes:...
Page not loaded if the URL ends with "#"
Thanks, Carsten and Ronald. The issue is fixed now.
Unexpected POST parameters in case of malformed HTML
Since this issue is marked as closed already, I wanted to raise your attention to...
Regarding the left-over postponed action: in the test case no background JavaScript...
Thanks, Ahmed. I had a quick look at your changes. Some questions come to mind: Why...
Me, neither... But the good news is: the fix works like a charm. Thanks.
To be more precise: The thread local map for the current thread, the main thread,...
Memory leak when adding a frame to a page by JS
Hi Ahmed, when rechecking your fix I wasn't careful enough. I did only check that...
Hey, Ronald, works like a charm. Thanks!
Socket timeout is 0 during connection establishment
The issue is gone now. Thanks, Ahmed!
Hi Ahmed, I would like to re-open this issue. The current implementation uses a static...
Excessive usage of network resources
Hi Ronald, rechecked with the latest build from this morning. The issue is gone....
Hi Ronald, just a short update: I tried one of yesterday's snapshot builds, but the...