当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

How to grant access to a website to extract canvas data without going to that website

  • 4 件の返信
  • 0 人がこの問題に困っています
  • 2 回表示
  • 最後の返信者: cor-el

more options

I can't grant access to a website because it's totally borked without canvas data, and keeps going on an infinite loading loop. This loading loop prevents me from having enough time to grant the permission, so I need to grant the permission to this website without actually visiting it.

I can't grant access to a website because it's totally borked without canvas data, and keeps going on an infinite loading loop. This loading loop prevents me from having enough time to grant the permission, so I need to grant the permission to this website without actually visiting it.

すべての返信 (4)

more options

Do you have enabled "Resist Fingerprinting" as that is a possible cause for Canvas issues?

Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)?


You can try to add the canvas exception via the Browser Console. You need to enable the command-line for the console.

Replace the https://xxxx with the correct origin (only protocol and hostname).

Services.perms.addFromPrincipal(
  Services.scriptSecurityManager.createContentPrincipalFromOrigin("https://xxxx"),
  "canvas", 1
);

more options

cor-el said

Do you have enabled "Resist Fingerprinting" as that is a possible cause for Canvas issues? Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)?

You can try to add the canvas exception via the Browser Console. You need to enable the command-line for the console.

Replace the https://xxxx with the correct origin (only protocol and hostname).

Services.perms.addFromPrincipal(
  Services.scriptSecurityManager.createContentPrincipalFromOrigin("https://xxxx"),
  "canvas", 1
);

It seems like perhaps this isn't the issue after all. I am still having the same issue. I've attached a picture that might be helpful. I used the browser console you mentioned to capture some logged info in a picture while the website was looping for a couple of seconds.

more options

It would help others if you gave a URL so others can click to see what happens.

more options

You would have to check the Requests in the Web Console or in the Network Monitor to see what is going on.