-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Safari: no result shown #27
Comments
@maurocicio, it looks like Safari fails on line 80 of qrcode.js. In your example, it is line 3063 of qr.js. I got it to work in Safari by commenting out that line and rebuilding. |
Perfect, thanks!
Mauro
…On 2 December 2016 at 19:47, James Lin ***@***.***> wrote:
@maurocicio <https://github.com/maurocicio>, it looks like Safari fails
on line 80 of qrcode.js. In your example, it is line 3063 of qr.js.
var image = new Image(); image.crossOrigin = "Anonymous";
I got it to work in Safari by commenting out image.crossOrigin =
"Anonymous" and rebuilding.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAmeiDCzoJpKN3r9X2qVPnAATc1DxnXDks5rEGfUgaJpZM4KnQaz>
.
|
@igowerf do you think we should remove that line completely ? |
I believe it would be enough to comment it out and add a comment there, should somebody else need that line. Mauro |
I don't understand because thiw was added here : And it seems to be correcting a bug ... I find this quite difficult to understand |
Hi there,
I have setup a bare bone demo at http://la.cicio.org/?layout=node to verify for which browser jsqrcode works (your library is named codejs/jsqrcode/qr.js).
It seems to work fine with Firefox on linux, windows, android, mac.
When using safari, though, the decoded string is not visible.
No message appears in the JS console (firebug), there are no errors, it just doesn't show the string.
Is there any other information I could supply for you to figure out what is wrong?
Thank you!
The text was updated successfully, but these errors were encountered: