Search in popup window is not transferred to main window

[Anaphory]

Before, and after installing and running ngrok as described in the README.md and adding the address to public/bibnet_chrome_extension_testing/content_script.js, searching for terms in the main WC? window opens a popup window with the google scholar results, but does not show the results back in the main window.

Do I need to tell the system somehow that it's in testing mode? The extension comes from the chromium web store, which I don't assume knows anything about my local changes?

[jimmytidey]

It sounds as though the popup is being prevented from sending back the data, likely because the ngrok proxy isn't working. You need to get the inspector out in the popped-up google scholar window and see what it's reporting when it tries to the request to your ngrok proxy.

Is it sending it to the right address? Is it getting blocked because it's not HTTPS?

[Anaphory]

I figured it out, it was some issue with the current versions of meteor client-side. (Underscore not loaded properly? Babel version? I need to undo some changes like

-               _.each(bibnet.cookies, function(cookie){
+               bibnet.cookies.forEach(function(cookie){

in server/bibnet.js (the correct solution is to explicitly require underscore, and not to use these methods, I think) and test again, then you'll get a pull request.

[Anaphory]

Ah, no, the solution to this was to install the local version of the add-on, not the one from the chrome store; instructions for that should also go into the readme under the localhost instructions:

Open the ‘extensions’ settings; switch on ‘Developer mode’ (switch on the top-right), ‘Load unpacked’ from bibnet/public/bibnet_chrome_extension_testing.