Jisho

×
8b3776e48bb58316fa5ad55875fe7470
9 Replies ・ Started by Qzoz at 2015-03-05 15:18:21 UTC ・ Last reply by Kimtaro Admin at 2015-09-21 20:21:45 UTC

HTTPS Everywhere and Kanji stroke order

Using Firefox with HTTPS Everywhere plugin stops the Kanji stroke order animation from showing.

2986330e38386f92fee4774b0c54ed66
Kimtaro Admin at 2015-03-08 17:55:12 UTC

Thanks for reporting this, I'll have to research this as I'm not sure off of the top of my head what the issue is.

2986330e38386f92fee4774b0c54ed66
Kimtaro Admin at 2015-03-26 23:42:29 UTC

I have made some changes to the way the resources are served from AWS. Can you please try and see if it works now?

8b3776e48bb58316fa5ad55875fe7470
Qzoz at 2015-03-28 17:50:52 UTC

Still doesn't work. Only an empty space shows where the stroke order should be displayed.

2986330e38386f92fee4774b0c54ed66
Kimtaro Admin at 2015-03-29 10:50:05 UTC

Very odd, it's working for me using HTTPS Everywhere in both Firefox and Chrome, so it's hard for me to debug this. But I've gotten more reports from people having trouble with HTTPS Everywhere, so it's not just you.

But I've made another change to my AWS configuration. Can you try again please?

2986330e38386f92fee4774b0c54ed66
Kimtaro Admin at 2015-03-29 13:52:47 UTC

I just heard from another user that has had trouble with HTTPS Everywhere that updating it to the latest version fixed the issue with stroke order diagrams. Can you try and see if that works for you?

8b3776e48bb58316fa5ad55875fe7470
Qzoz at 2015-03-30 12:18:04 UTC

Yup, updating HTTPS Everywhere to 5.0 does fix the problem. Thanks for your work.

2986330e38386f92fee4774b0c54ed66
Kimtaro Admin at 2015-03-30 18:52:43 UTC

Great!

8b3776e48bb58316fa5ad55875fe7470
Qzoz at 2015-09-08 12:47:27 UTC

This problem seems to have returned lately. Using HTTPS Everywhere 5.1.1 in Firefox and Encrypted Web 5.1.1 in Pale Moon seems to break the stroke order diagrams. Chrome doesn't seem to be affected though.

2986330e38386f92fee4774b0c54ed66
Kimtaro Admin at 2015-09-21 20:21:45 UTC

I recently switched to using Cloudfront to distribute the stroke order data and it seems like HTTPS Everywhere blocks Cloudfront by default. This seems to be a general issue with sites that use Cloudfront unfortunately: https://github.com/EFForg/https-everywhere/issues?utf8=✓&q=is%3Aissue+is%3Aopen+cloudfront

The recommended fix seems to be to disable the Cloudfront rule.

to reply.