I have been developing an AJAX application using jQuery and Microsoft Seadragon technology.
I need to have access to the html5 canvas function toDataURL.
With Google Chrome, the same origin rule applies to this function which means that a page run locally (with the file:///
in the URL) failed to satisfy the same origin rule and an exception is thrown.
With Chrome 7, starting the application with --allow-file-access-from-files
option, allows to call canvas.toDataURL()
from local files.
However, it seems that starting the Chrome Beta 8 with the same option (--allow-file-access-from-files
) does not allow the call canvas.toDataURL()
on the local file.
Does Chrome gave up on the --allow-file-access-from-files
option or it has just been disabled since it is a Beta release and not a full release?
Thanks!
Looking at the issues for this shows that the whole --allow-file-access-from-files
thing was rushed.
On to your Problem
Indeed it seems that this is something special to the beta, I'm using Chrome 8.0.552.5 dev
here and --allow-file-access-from-files
works like expected, I've also tested this with Chromium 9.0.592.0 (66889)
were it also works as expected.
I suspect there have been some changes on the dev branch. Unfortunately, finding something on chromium's issue tracker is nearly impossible.
Did you close all chrome instances before opening with the command line argument? You have to do that to make that parameter work.
To summarize all answers so far.
Before running chrome, make sure there are no chrome processes running.
Windows
-allow-file-access-from-files
(with one dash)
Linux
--allow-file-access-from-files
(with two dashes)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With