I installed an SSL certificate to a website created with Prestashop 1.6.
But it indicates to me that it is not totally safe since there is a request to the logo of the site by HTTP. Checking the code from chrome developer tools I verify that the request to said logo image is by HTTPS so I do not understand why I have this problem in console.
Site: www.menguz.com.mx
You have an HTTP image link in your fancybox javascript.
jQuery(document).ready(function () {
$.fancybox('<div class="pop"><img src="http://menguz.com.mx/img/vinos-y-licores-menguz-logo-1460428150.jpg" alt="" /><h3>Vinos y Licores Menguz sólo vende alcohol a mayores de edad.</h3><h3>Le pedimos responder con responsabilidad:</h3><div class="options"><ul class="buttons"><li>Salir, soy menor de 18 años</li><li>Soy Mayor de 18 años</li></ul></div></div>', {
'width': 500,
'height': 250,
'autoScale': true,
'scrolling': 'si',
'closeClick': false,
'closeBtn': false,
'keys': {
close:
null
},
'helpers': {
overlay: {
closeClick:
false
}
}
});
});
Related
The OneDriver Picker does not load after the authentication process but instead shows a spinner.
Steps to Reproduce
OneDrive Scripts Tested:
https://js.live.net/v7.2/OneDrive.debug.js
https://js.live.net/v7.2/OneDrive.js
Code used to Initiate the OneDriver Picker:
function launchOneDriverPicker() {
debugger;
var odOptions = {
clientId: "${clientId}",
action: "share",
multiSelect: true,
openInNewWindow: true,
advanced: {
redirectUri: "${redirectUri}"
},
success: function(r) {
},
cancel: function() {
},
error: function(error) {
}
};
OneDrive.open(odOptions);
}
Environments Tested:
- Chrome (Normal/Incognito)
- Firefox (Normal/Incognito)
Steps
The page hosting the OneDrive Picker and redirect URLs are served from the same domain
The redirect occurs to a redirect page with the following content hosted under the same domain (domain/redirect):
<html>
<head>
<link rel="icon" href="data:;base64,iVBORw0KGgo=">
<script type="text/javascript" src="https://js.live.net/v7.2/OneDrive.debug.js"></script>
</head>
</html>
Additional Notes
The above setup works correctly with the OneDriver Picker 7.0 as noted in an earlier issue:
https://github.com/OneDrive/onedrive-api-docs/issues/824
While debugging the issue I noticed that the OneDriver Picker makes a cross document call to the parent window which opened the Picker. There are no errors up to this point but the parent page does not receive this message.
The domain specified in the cross document call is correct
Reference
[1] https://learn.microsoft.com/en-us/onedrive/developer/controls/file-pickers/js-v72/open-file?view=odsp-graph-online#using-a-custom-redirect-uri
I have sound working in Chrome, Firefox on Mac, but not Safari Version 9.1.3, OSX 10.11.6.
I can only find a statement in the docs saying that Safari will need the Quicktime plugin. However, when I point my Safari to the Soundjs and Preloadjs demo pages, the sound works fine in the demos. Furthermore, apparently Apple is no longer including the QT plugin on current installs of Safari. It would be unacceptable to ask users to install a legacy plugin. (edit: just received word the sound isn't working in MS Edge either)
Here is all of my code:
var stage;
var canvas;
canvas = document.getElementById("gamezCanvas");
stage = new createjs.Stage(canvas);
var soundsManifest = [
{
id: 0, src: '10_ciiruhi.ogg'
},
{
id: 1, src: '20_shuuk.ogg'
}
];
var queue = new createjs.LoadQueue();
queue.installPlugin(createjs.Sound);
queue.on("complete", handleComplete);
queue.loadManifest(soundsManifest, true, audio_url);
function handleComplete() {
createjs.Sound.play(1,
{
interrupt: createjs.Sound.INTERRUPT_NONE,
loop: 0,
volume: 1
}
);
}
var btn = new createjs.Shape();
btn.graphics.beginFill("#000");
btn.graphics.drawRect(0, 0, 200, 120);
stage.addChild(btn);
stage.update();
btn.on("click", function() {
createjs.Sound.play(0,
{
interrupt: createjs.Sound.INTERRUPT_NONE,
loop: 0,
volume: 1
}
);
});
It was a simple file format issue. Outside the scope of createjs's documents to inform me about. Shame on me :(
OGG is no bueno in Safari and Exploder.
I upgraded twitter typeahead using the nuget package manager from 10.2 to 1.11 and the remote query is no longer being called to get the autocomplete results in my ASP.Net MVC 5 project. There are no errors reported.
var engine = new Bloodhound({
datumTokenizer: Bloodhound.tokenizers.obj.whitespace('FullName'),
queryTokenizer: Bloodhound.tokenizers.whitespace,
limit: 10,
remote: '/Person/GetPeople?q=%QUERY'
});
engine.initialize();
$('#Person').typeahead({
hint: true,
highlight: true,
minLength: 1,
}, {
display: 'FullName',
source: engine.ttAdapter()
}
I found the answer before I finished typing my question out, so here is what I found. I just had to change the remote declaration in the following:
var engine = new Bloodhound({
datumTokenizer: Bloodhound.tokenizers.obj.whitespace('FullName'),
queryTokenizer: Bloodhound.tokenizers.whitespace,
limit: 10,
remote: {
url: '/Person/GetPeople?q=%QUERY',
wildcard: '%QUERY'
}
});
Furthermore, the CSS was broken for Bootstrap 3 - I am using typeahead.js-bootstrap3.less. The temporary fix for this was to replace dropdown-menu with menu in typeahead.css (until a new release).
I am porting a chrome extension to firefox and want to keep as much code as possible. I am working with the sdk and I am new with JavaScript, so please bear with me if it is just a nooby mistake ;)
I need to get some stuff via a couple of XMLHttpRequests in content-scripts.
The "firefox-way" of doing things would be to use the sdk-request-api and work via messages between the main- and the content-script like so. Besides the fact that it would mean a lot of work for me to implement this throughout the whole addon, I also need to get binary data, which seems not to be possible.
The workaround for this is documented here. I would prefer to avoid this, since I think I read somewhere that it is a beta-feature right now and it seems to be pretty "work-aroundy".
Ideally I would like to implement it this way. In the upcoming Firefox 24 it should be possible to allow content scripts to access certain domains. Therefore I am using Firefox Aurora right now. I added the following code to my package.json:
"permissions": {
"cross-domain-content": ["http://mozilla.org"]
}
My main.js creates a panel when a button is clicked and loads the scripts into it:
var testPanel = require("sdk/panel").Panel({
contentURL: data.url("pages/background.html"),
contentScriptFile: [data.url("util/jquery-1.8.2.min.js"), data.url("pages/xhrTest.js")]
})
testPanel.show();
And this is my xhrTest.js:
var xhr = new XMLHttpRequest();
xhr.open("GET","http://mozilla.org",true);
xhr.onerror = function () {
console.log("Error");
};
xhr.onload = function () {
console.log("loaded");
}
xhr.send();
While debugging, it jumps from status 2 to 4 with an empty response and calls the "onerror". The status is 0, statustext is empty and I don't see any other indicators of what went wrong.
Now I don't know if this is still the same-origin-policy blocking me, or if I did something else wrong?
I'd really appreciate any help I can get :)
Thanks in advance,
Fabi
Hrm, I can't really see a glaring error. Here is an example add-on based on the docs that does work, at least it does for me in Firefox 24 Beta:
Main.js:
// main.js
var data = require("sdk/self").data;
var panel = require("sdk/panel").Panel({
height: 250,
contentURL: data.url("panel.html"),
contentScriptFile: data.url("panel-script.js")
});
panel.on("show", function(){
panel.port.emit("show");
});
require("sdk/widget").Widget({
id: "test-widget",
label: "Test-Widget",
contentURL: "http://www.mozilla.org/favicon.ico",
panel: panel
});
Panel.html:
<!doctype HTML>
<html>
<meta charset="utf-8">
<head></head>
<body>
<pre id="forecast_summary"></pre>
</body>
</html>
Content script:
// panel-script.js
var url = "https://hn-test.firebaseio.com/articles/e5b10c82600b51732af584583a7f57c4a7c01bff.json";
self.port.on("show", function () {
var request = new XMLHttpRequest();
request.open("GET", url, true);
request.onload = function () {
var element = document.getElementById("forecast_summary");
// formatting
var pretty = JSON.stringify(JSON.parse(request.responseText), null, ' ');
element.textContent = pretty;
};
request.send();
});
Package.json:
{
"name": "jp-crossdomain-xhr",
"fullName": "jp-crossdomain-xhr",
"id": "jid1-B2RaQxOBKox8wA",
"description": "a basic add-on",
"author": "",
"license": "MPL 2.0",
"version": "0.1",
"permissions": {
"cross-domain-content": ["https://hn-test.firebaseio.com"]
}
}
Github Repo
Here is my code:
<script>
require(["dojox/grid/DataGrid", "dojo/store/Memory","dojo/data/ObjectStore", "dojo/store/JsonRest", "dojo/_base/xhr", "dojo/domReady!"],
function(DataGrid, Memory, ObjectStore, JsonRest, xhr){
var gridSimple,
store,
dataStore;
function createGrid(){
gridSimple = new DataGrid({
store: dataStore,
structure: [
{ name: "Name", field: "name", width: "84px" },
{ name: "Last name", field: "lastName", width: "84px" },
{ name: "e-mail", field: "email", width: "120px" }
],
rowsPerPage: 20,
autoHeight:15,
selectionMode: "single"
}, "grid");
gridSimple.startup();
}
function init(){
store = new JsonRest({target: "/users/"});
dataStore = ObjectStore({objectStore: store});
createGrid();
}
init();
});
</script>
<div id="grid">
</div>
I'm getting the first page (The Range header is being sent), but when scrolling down nothing happens, dojo is not sending the next request. Not sure what I'm doing wrong.
I'm on firefox 14.0.1, btw the scroll is really really slow using the mouse wheel. I also tried in chrome, not getting next page, but at least the mouse wheel works just fine.
Dojo version: 1.7.2
The problem was I had to add the next header to my response:
response.addHeader("Content-Range", "items " + from + "-" + to + "/" + total);
I did not know this. It is what they call the "REST Paging standard". http://dojotoolkit.org/reference-guide/1.7/dojo/store/JsonRest.html#id7
On the other hand, firefox is scrolling painfully slow. Not happening in chrome.
Here is the bug report:
http://bugs.dojotoolkit.org/ticket/15487
So, in firefox preferences>Advanced> uncheck "Use smooth scrolling".