This widget may lead to CPU usage reach 100% on Mac OS.
HTTP/HTTPS Cookies
This test case is used to test if CEPHtmlEngine support HTTP/HTTPS persistent cookies.
When you load the test website first time, it will require you to enter your name. This name will store in cookies.
When you reclick "Show Test Website" or click the button "Submit Code" on the website, it will pop up a dialog with your name which you entered before.
Close all Html extensions, then delete cookies file.
Cookies Path on Windows: "C:\Users\[yourusername]\AppData\Local\Temp\cep_cache"
Cookies Path on Mac: "/Users/[yourusername]/Library/Caches/CSXS/cep_cache"
Reclick "Show Test Website", it will require you to enter your name again. This means this test case has passed for persistent cookies
File Cookies
This test case is used to test if CEPHtmlEngine supports session and persistent file cookies.
Enter a cookie name and value (or keep with the defaults) and click Set Cookie.
Click Get Cookie to confirm it has been set.
Restart Application.
Return to File Cookies tab and click Get Cookie. No Cookie should be returned.
Now check Add expiry and click Set Cookie.
Restart Application and return to File Cookies tab.
Click Get Cookie. Your cookie value should be returned.
Add expiry (e.g. persistent cookie)
Run it on any machine with camera and network on.
It's normal that render process causes high CPU usage while capturing.
For webRTC official demo, run the url above https://apprtc.appspot.com/?r=######### in chrome. It's OK if alert dialog shows up in extension with message 'RTCPeerConnection is not supported'. Because RTCPeerConnection is supported after CEF3.1547.