Yeah, but WebView and WebParser are different things. WebView is basically placing the original webpage into the skin, accessing it is done by the Edge browser, and the webpage area will not behave like a skin but as a browser tab. WebParser has nothing to do with browsing, it just parses the text in the webpage source and looks for the desired regex pattern in it (it also doesn't support cookies or other session-based authentication, so it cannot be used to retrieve information from web sites requiring a login, except through HTTP authentication like https://myname:mypassword@somesite.com - which might explain your cloudflare / captcha problem).Kotofanchik wrote: ↑March 29th, 2024, 6:32 am I thought maybe there were ways to bypass cloudflare. I have an idea, but lack the knowledge to implement it. There is a skin PluginWebViewExample. He successfully accesses the Gismeteo website. WebWiev2, which is the basis of this skin, can save the page to a txt file. This txt file can be parsed and information can be retrieved. It works manually. I have not yet seen a captcha request in WebWiev2. If sometimes a request appears, you can answer it.
To see if WebParser can retrieve the desired data when accessing an URL address, all you have to do is open that address in your browser and left click to show its Page Source from the right click context menu (at least, that's how you do it in Chrome). In the page source text page that opens, if you find your desired data using CTRL + F (aka Find), then WebParser will find it as well. If not, then you have to use alternatives like WebView and instead "navigate" that page just as you'd do it in a browser, but from your skin.
The main inconvenience with WebView is that you're not parsing any text in the page source, you're simply showing the page in the skin, which means that any action on the browsing area (like clicking, dragging, etc.) will have nothing to do with the skin, only with the browser itself (Edge) and the webpage you're on and its HTML / CSS / JavaScript code.