HTTPS bookmarklet doesn't work

[gsmnv]

HTTPS bookmarklet doesn't work

[epicmonkey]

I'm afraid I was not able to reproduce this defect, have just added a new post with no issues: http://pepyatka.com/posts/c4906fea-6504-4253-8ae1-16068bbfff32. Presumably it may has something to do with a browser I'm using and you might want to check out public/js/bookmarklet.js file for a jQuery loader.

[epicmonkey]

Indeed, this is an old version of Firefox (https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/). I'm thinking if we load jQuery from https always will it solve the issue. Can you please test this?

[gsmnv]

It indeed solves the problem with jQuery loading but next exact same problem with loading from http://0.0.0.0:3000/js/pepyatka.js arises why don't you include pepyatka.js into bookmarklet.js? It isn't that large.

[epicmonkey]

The main reason behind loader and core scripts is to be able updating bookmarklet without affecting any users those have already added it (js code) to a browser. Say user A added a minimized bookmarklet to a bar and next day you find a defect or just want to release a new version, so if there's only one script you'll somehow tell that user to update bookmarklet code, which is definitely a tricky task. However two scripts allow updating bookmarklet smoothly.

[indeyets]

the solution is to get certificate for HTTPS and server pepyatka's js via it

[epicmonkey]

This is for the frontend. See linked story.