We have an app that embeds a Google Trend chart. However every couple of months the chart stops working. Each time it seems that the embed JS version has been incremented and the old version is no longer available.
This was today's fix:
-<script type="text/javascript" src="https://ssl.gstatic.com/trends_nrtr/760_RC01/embed_loader.js"></script>
+<script type="text/javascript" src="https://ssl.gstatic.com/trends_nrtr/962_RC10/embed_loader.js"></script>
Is there any kind of URL that 301's to the latest version? I've tried:
https://ssl.gstatic.com/trends_nrtr/latest/embed_loader.js
... but it doesn't work.
Surely this approach from Google means any page on the internet with an embedded script will eventually break?!
Related
My project is using both Google Map JavaScript API and Place Library based on React. But since google upgraded it to v3.39, I met an issue in IE 10. (Some clients are still using IE 10!) The latest version 3.39 doesn't support IE 10, so I tried to degrade it to 3.38 in different ways but none of them working:
Pass 'v=3.38' when load Place in header: <script src="https://maps.googleapis.com/maps/api/js?v=3.38&key=mykey&libraries=places"></script> -->. It still loaded v3.39.
Manually Load v3.38 Map in header:
<!-- <script src="https://maps.googleapis.com/maps/api/js?v=3.38
&key=mykey&callback=initMap"
async defer></script>
<script src="https://maps.googleapis.com/maps/api/js?key=mykey&libraries=places"></script> -->. The map can be rendered, but address autocomplete will not even show up.
Manually load a 3.38 version when render a map: This method partly works. But browser will display an error said: You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors.
Please give any suggestion on my scenario. Thanks so much!
I have a question for you about jQuery.noConflict.
First of all - I did some research on what
jQuery.noConflict(true)
is, my question is related to this closely. So far I have found no answer that I was able to apply to my case, so if the answer is obvious and slipped my mind I apologize in advance.
The problem:
I am currently trying to solve a problem for a very large JS application. The JS application runs on a SAMSUNG browser (based on Orsay), which in turn runs on specific SAMSUNG displays.
To use display functions it is required to include:
<!-- TODO : Common API -->
<script type="text/javascript" language="javascript" src="$MANAGER_WIDGET/Common/API/Widget.js"></script>
<script type="text/javascript" language="javascript" src="$MANAGER_WIDGET/Common/API/TVKeyValue.js"></script>
<script type='text/javascript' src='$MANAGER_WIDGET/Common/af/2.0.0/loader.js'></script>
<script type='text/javascript' src='$MANAGER_WIDGET/Common/API/Plugin.js'></script>
Also to use Deferred objects within the code jQuery 1.9.1 is included:
<script type='text/javascript' src='app/javascript/jquery-1.9.1.js' ></script>
My problem arises from the fact, that the SAMSUNG APIs apparently load whatever it is they are loading in the display's backend, however one of the things they load is their own jQuery version, which is 1.4.2.
The situation is such that I cannot say which version will be loaded at what point. I can start up the display five times having done no changes to the code and will get two times 1.4.2 and three times 1.9.1 or once 1.4.2 and four times 1.9.1 or any other possible order. I suspect this being due to the display's API able to run multithreading, so that the JS application and the API run independently from one another.
So I took a look at the noConflict method, however am unsure how to go about this problem using it.
As said, the application is large. It uses jQuery in various places. So doing something like
jQuery1_9_1 = $.noConflict(true);
after loading our jQuery version is rather unfeasible, since this will cost a large amount of time to fix.
However so far I have found no way to reliably unbind version 1.4.2 from $, because I do not load it, but the display's API does and it is not clear as to when it is loaded.
I hope this question is not redundant and someone has an idea how to go about it.
Okay guys I have a website that has a lights off for videos source code: http://www.megaptery.com/allofthelights/
An organic tabs for videos using Jquery
and a 2buttons which onclick it changes the CSS of the whole page you know it's kinda like a theme for the page
Here is an example of one of my page:
http://myanimesekai.com/Watch/Noucome-Episode-9
okay all of them works perfectly fine on my laptop all of them IE, Mozilla and the OLD Google Chrome.
But Then I tried it on my Brothers Laptop BUT his Google Chrome is the latest Google Chrome the Google Chrome where the scrollbar changed. The problem is that the Lights off feature is malfunctioning it doesn't turn off the video only. But the Organic Tabs and The 2buttons works perfectly fine. So I tried it on an internet Cafe and this is where I was really frustrated their Google Chrome is also updated and then both 3 of them were malfunctioning then after a while I tried them on Mozilla and all of them worked perfectly fine and so I have an Idea maybe it's becaused it took time for the Jquery and my Javascript to load which is why all 3 of them were malfunctioning.
so my question is is there a way for me to make my page load the jquery and javascript 1st? or am I missing something that the new Google Chrome requires? this is really frustrating me
oh BTW the 2buttons that changes the CSS are the B and M squares Below the facebook page
There are so many errors on this page (http://myanimesekai.com/Watch/Noucome-Episode-9) that any one error can cause the page not to work.
You need to clean up your code quite a bit:
<script src="http://myanimesekai.com/javascript.js"></script>
<script src='http://ajax.googleapis.com/ajax/libs/jquery/1.6.1/jquery.min.js'></script>
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.0/jquery.min.js"></script>
<script src="http://myanimesekai.com/organictabs.jquery.js"></script>
You are calling jQuery in your javascript.js file. The jQuery library has not been declared before your scripts. You need to restructure your code to (you only need one version of jQuery):
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.0/jquery.min.js"></script>
<script src="http://myanimesekai.com/javascript.js"></script>
<script src="http://myanimesekai.com/organictabs.jquery.js"></script>
This will fix some errors. I suggest that you look at the console for further errors and fix them.
I have been searching everywhere and do not seem to be able to find anyone else reporting the same issue.
I'm currently building a website that is using the jQuery vegas plugin but I started noticing that if I kept the page opened while developing and testing, my computer starts slowing down drastically. I started monitoring my task manager and the memory used by the browser goes up every time the slideshow moves to the next image and just keeps going up non-stop.
I've tried with IE 11, firefox 27 and Chrome 33 and the problem only seems to happen with google Chrome. However, using Chrome, if I go on the official plugin website (http://vegas.jaysalvat.com/) where they do use the plugin, I do not experience the problem.
Here are the links to jQuery and the plugin:
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js"></script>
<script type="text/javascript" src="http://jaysalvat.github.io/vegas/releases/latest/jquery.vegas.min.js"></script>
Here is my js code:
$(document).ready(function(e) {
$.vegas('slideshow', {
delay:10000,
preload:true,
backgrounds: [
{src:'images/bg_body-001.png', fade:2000},
{src:'images/bg_body-002.png', fade:2000},
{src:'images/bg_body-003.png', fade:2000},
{src:'images/bg_body-004.png', fade:2000},
{src:'images/bg_body-005.png', fade:2000}
]
});
});
Are you testing your code in a local hard drive? I had this problem too, but I solved it by moving the same website from my local hard drive to a webserver. I'd suggest trying this and testing again, and hopefully this will help you too.
Our webpage has 3 google adsense ads on it along with a custom dojo build. Everything has been working great until I updated to Firefox 14. Now the page doesn't load I'm guessing due to some javascript errors?
I've been trying to trial and error this issue. The best I have found is that when you paste adsense code into your page there is a script:
<script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
if you use openX:
<script type='text/javascript' src='http://d1.openx.org/ag.php'></script>
from what I can see, if this script is defined on the page more than once the page will not load correctly. This has been working in older versions of FireFox. It also works fine in chrome and IE.
Does anyone have any ideas what is going on or what changed?
Thanks
EDIT
I think this issue has to do with a custom build of dojo and the ad script tags. If I remove all the ads from my page dojo works correctly and my page is fine. I can also view all the ads on the page when dojo is not loaded. Does anyone know how I can debug this?
This appears to be a bug in FireFox 14. I can't find a bug report on http://bugzilla.mozilla.org, but I tested it with Aurora, and edge version of FireFox, which means it should be fixed in one of the next two versions of FireFox.
Aurora goes to Beta August 27th
with FireFox 15th being released the next day. If you want to ensure it will work with FireFox 15 try downloading the release and running it under that.
Release date schedule here
As of FireFox 14 something has changed as to what gets cached. If you edit the preferences (about:config in the url bar) and change the parameter network.http.use-cache to false the website will work correctly.
I verified that this parameter is in firefox 13 and also set to true by default. Our site works in ff 13 so something changed with the way firefox caches resources.
EDIT
I also realized that trying to load my 3 google adsense ads at the same time as dojo was causing issues.
I used dojo/domReady! before loading any dojo modules and this fixed any issues I was having. It will also work without changing the firefox network.http.use-cache parameter.