Description
Reviews (31 cached)
doesn't work
Used to be the ONLY extension that works with my client's app, but after the recent update it does not work at all. Automatically turns off when I reload the page. Now I have zero extensions that work for me :(
Just after the new update does not work as well as before anymore It has become so complicated and I get errors with cors. Can you please downgrade again. Please fix. It was a five star extension.
WHY YOU UPDATED !!!! what did you do !! It was my fav extension , after update it is not working unfortunately , on local files it gets auto off when i reload.
not working for me
doesn't work for me.
doesnt work
Not working when CORS header is ignored b/c coming through a unsecure request (http). "The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead."
Don't work
not work
Not working
It doesn't work ! Avoid this extension
Didn't work. Simple as that.
This does not work for local html & local file. Sample html is below: --- <html> <body> <script type="text/javascript" src="https://mozilla.github.io/pdf.js/build/pdf.js"></script> <script type="text/javascript" src="https://mozilla.github.io/pdf.js/build/pdf.worker.js"></script> <script type="text/javascript"> var url = "file:///Users/amagaiwork/Desktop/sample.pdf"; var pages = [], heights = [], width = 0, height = 0, currentPage = 1; var scale = 1.5; function draw() { var canvas = document.createElement('canvas'), ctx = canvas.getContext('2d'); canvas.width = width; canvas.height = height; for(var i = 0; i < pages.length; i++) ctx.putImageData(pages[i], 0, heights[i]); document.body.appendChild(canvas); } pdfjsLib.disableWorker = true; // due to CORS const loadingTask = pdfjsLib.getDocument(url); loadingTask.promise.then(function (pdf) { getPage(); function getPage() { pdf.getPage(currentPage).then(function(page) { console.log("Printing " + currentPage); var viewport = page.getViewport(scale); var canvas = document.createElement('canvas') , ctx = canvas.getContext('2d'); var renderContext = { canvasContext: ctx, viewport: viewport }; canvas.height = viewport.height; canvas.width = viewport.width; page.render(renderContext).then(function() { pages.push(ctx.getImageData(0, 0, canvas.width, canvas.height)); heights.push(height); height += canvas.height; if (width < canvas.width) width = canvas.width; if (currentPage < pdf.numPages) { currentPage++; getPage(); } else { draw(); } }); }); } }); </script> </body> </html>
OK!! it work with cors, but your extension broke another site :|
Doesn't work
Does not run on Chrome 79.
It doesn't work!
not working
Does not work
This seems to always modify your requests, not only when it's "active". Headache of a bugfix that was actually machine confinguration
Did not work. Only replaced the error I was receiving with a different one.
Doesn't work. I'm using Version 89.0.4389.114 (Official Build) (64-bit).
Be careful this breaks other apps, like Hangouts inside Gmail. It is supposed to unblock, not to block content. Not recommended, but if you really need to use it for development purposes, enable it only after clicking on it on specific websites. Your general web surfing will be affected otherwise.
not working on my side
Was working, then stopped.
It has a BIG BUG when "credentials": "includes" exists in fetch request. The extension puts wildcard * in Access-Control-Allow-Methods and this make CORS to block the request.
It works 60% of the time that's why 3 stars, other times I get "has been blocked by CORS policy: Request header field content-type is not allowed by Access-Control-Allow-Headers in preflight response."
It did its job, but make sure to disable it completely when you don't use it. It caused whatsapp web to stop functioning, even when it was not running.
Breaks drive.google.com for me if enabled for all sites.
Not in this case "The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute" in this case (and, in fact it will work better everywhere), header should be origin of request.
Permissions (3)
Permissions
Details
| Version | 0.5.2 |
| Updated | Jun 3, 2025 |
| Size | 198KiB |
| First Seen | Mar 22, 2026 |
More by balvin.perrie
Popular in developer
Popular Extensions
