If you're using proxies with requests-html and rendering JS sites is all good. Once you render a website pyppeteer don't know about this proxies and will expose your IP. This is an undesired behavior when scraping with proxies.

The idea is that whenever someone passes in proxies to the session object or any method call, make pyppeteer also use these proxies. #265

Here's an interesting one...

<a href="#linktarget">Link</a> works.

<a href="#linktarget(thing)">Link</a> doesn't work.

Adding brackets into the link target breaks the link in the PDF (works in Chrome).

I have analyzed video problems and below is the summary. All tested with examples/http_server.py from the pywebview-3 branch.

Windows

• CEF / MSHTML / EdgeHTML. No problems with either. CEF supports only WebM and Ogg out of the box (MP4 not supported).

Cocoa

• Only video frame is displayed, video not playing. Youtube works fine. There are a bunch of flags related to media in WKWeb

User story

What did you do?
1.Goto a RTL version of MDN ste. eg: https://developer.mozilla.org/fa/

2.Look at small arrows on side of Web Technologies; Learn web development; Developer Tools

3.Look at cat that shows "Help us build better CSS debugging tools!
Which CSS bugs are the worst?
Take the Survey"

4-Look at location of Arrow of "Sign Up now" button

5-From Refrences and

Why isn't the yahoo finance API listed in the Data Readers list, but it is available as get_data_yahoo()? Will the get_data_yahoo() function be deprecated in future versions?