You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The website doesn't seem to recognise that htmlunit is running with JavaScript enabled. As this example shows, the website returns a warning that it doesn't think the client browser can handle JavaScript, then simply returns the JavaScript unprocessed with all of the tabular information about energy missing.
This seems to happen for every website I try that requires JavaScript to run for the website's data values to display.
Am I doing something wrong? Or does htmlunit only ever return web pages like the one above, never managing to return a fully JavaScript-rendered web page equivalent to what you get in a manual browser?
The text was updated successfully, but these errors were encountered:
Usually this is the case if some js feature required for this page is not supported. Will have a look but I'm on vacation right now. Please be a bit patient...
I can't get htmlunit to return javascript-rendered web pages even when I ensure webClient.getOptions().setJavaScriptEnabled(true) has been called.
For example, calling .getPage() to get the NemWatch web page for live supply and demand figures for national energy (https://ausrealtimefueltype.global-roam.com/expanded) returns the following web page:
The website doesn't seem to recognise that htmlunit is running with JavaScript enabled. As this example shows, the website returns a warning that it doesn't think the client browser can handle JavaScript, then simply returns the JavaScript unprocessed with all of the tabular information about energy missing.
This seems to happen for every website I try that requires JavaScript to run for the website's data values to display.
Am I doing something wrong? Or does htmlunit only ever return web pages like the one above, never managing to return a fully JavaScript-rendered web page equivalent to what you get in a manual browser?
The text was updated successfully, but these errors were encountered: