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
Trying to open screenshots in report by mouseClick:
Problem : it is impossible to open screenshots in generated report by mouseClick().
"protractor-beautiful-reporter": "1.3.0"
Google Chrome: Version 76.0.3809.132 (Official Build) (64-bit)
Console error:
Error text:
angular.min.js:110 Access to XMLHttpRequest at 'file:///C:/Users/.../Downloads/.../pbr-screenshot-modal.html' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https.
As I understand the problem appears after new functionality was added in 1.3.0 version. New functionality related to the next files:
Problem disappears if version is reversed to 1.2.9.
Is it possible to find problem solution with new functionality added in 1.3.0?
Regards, Sergei.
The text was updated successfully, but these errors were encountered:
@zhukovsv First of all thank for the precise description :-) Update: It is fixed now...just use version 1.3.1
It think it did not test opening the files with from a local folder, but with a temporary web server.
So i did not detect that it does not work when you open the report directly from file system.
Chrome just blocks ajax request for file protocol, so the report cannot load the pbrmodal files if open directly from the files system.
While I search for a solution you can do the following in the meantime:
open a shell (e.g. cmd in windows)
install a simple http server via npm install -g http-server.
Trying to open screenshots in report by mouseClick:
angular.min.js:110 Access to XMLHttpRequest at 'file:///C:/Users/.../Downloads/.../pbr-screenshot-modal.html' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https.
As I understand the problem appears after new functionality was added in 1.3.0 version. New functionality related to the next files:
Problem disappears if version is reversed to 1.2.9.
Is it possible to find problem solution with new functionality added in 1.3.0?
Regards, Sergei.
The text was updated successfully, but these errors were encountered: