I was having a problem with IE finding both secure and non-secure items on a page. This seems to have been sorted thanks to a solution by David (many thanks!) who suggested altering the JS we use to display a gallery of images at the top of the page.
The issue now is that the gallery doesn't work!
Here's the error message:
Webpage error details
Message: 'this.galleryData.0.image' is null or not an object
Line: 266
Char: 4
Code: 0
URI: https://www.droverholidays.co.uk/scripts/jd.gallery.js
The page is:
https://www.droverholidays.co.uk/bikehireform.php
I don't understand JS very well so it would be great if anyone can tell me what I need to do to make this work!
In bikehireform.php change the line that says
startGallery();
to
window.addEvent('domready', startGallery);
In looking at your other question, I personally think CptSkippy's answer is still the correct one.
Stick with the onDomReady approach and make sure your external assets are being loaded from http***s***
Wow... I think I may have got it. I substituted 'load' for 'domready' in Rob's solution, above, and now I don't get the IE warning, and the script works. It seems to be a bit slower than before, would that make sense?
Related
Im trying to use the awesome jQuery Rhinoslider plugin, however it does not work one bit.
Not even the demo i downloaded works, it just throws Effect for explode not found and "Preparations for explode not found" in the console.
I choose the effect explode but this happens with every effect, even if i choose none as effect.
The documentation is pretty poor regarding this kind of questions and you dont find a lot of answers on the internet for this plugin..
Does anybody know what this logs mean? I included every other scripts (easing, mousewheel) and as said, not even the demo i downloaded is working.
Thanks very much!
You probably need explode effect from jqueryUI download page
I had the same "Effect not found" issue and I solved it with downloading again the slider from http://rhinoslider.com/demo-download/
You may need to check all the effects or the effects you need, because they are not checked by default.
I set a breakpoint in a script block of a razor view.
VS2012 attaches to IE but breakpoint has yellow triangle with exclamation mark saying:
The breakpoint will not currently be hit. The code in the document is
not loaded.
Script debugging is enabled in Internet Options of IE.
Have no idea what is wrong.
I faced this problem too. After trying many codes and things take from different posts in Stackoverflow and others websites, they have not solve my problem. When i have take a look for #robert4 solution and go back in my javascript code, i saw one error and fixed it, by doing like that, i have finally solve may problem and can now get a breakpoint in my javascript document. For those who will face this type of problem, i think that the first thing to do it is to verify your js file code by code to see if there is no error before beginning to implement each of others solutions take from differents posts.
When I had similar issue it turned out that an omitted } was the cause
(in one of the JavaScripts of the page, one of the {}s was not closed).
There was no error message on the browser console at all,
just didn't work and I had no clue for half an hour.
When I fixed the missing }, everything began to work as expected.
I have been having an issue previewing the website inside IE. For all other browsers the website works just fine but not for the evil one.
I have been been trying for a while to solve the problem but unsuccessful. I think I might run out of ideas. :/ Is there anyone who might point me in the right direction and help me out solve the problem.
The website can be seen on this address: http://www.flyingcowproduction.com/platinumlimoservices
if you click on any of the menu buttons the jquery won't load the content in IE :(
Many, many thanks in advance
Best regards,
-Davorin
Your javascript is breaking on this line:
var iframe = $("#jQuery_history")[0].contentWindow.window;
jquery.history.js, line 33
Unable to get value of the property 'contentWindow': object is null or undefined
It then breaks again if you go to the services page
showArea(id[0]);
PageNavigation.js, line 296 character 3
'showArea' is undefined
The second one probably just happens because of the first error.
PS - In IE, push F12 and use the script debugger and you can solve this with a little help from google.
Ok here's the problem. I have a page that works in FF3 and Safari4 no problem. It's IE8 that's causing the issue, go figure. I remember in the Netscape days when it was the opposite.
Anyways,
So i'm building a website for a friend - i have three pages. the first two work fine on their own, but when they are combined in a frameset in the third (main.html) in IE8 all hell breaks loose. here are the pages:
www.wither.org/Karoline/navigation.html
www.wither.org/Karoline/portfolio.html
http://www.wither.org/Karoline/main.html
& my CSS if you want it: www.wither.org/Karoline/css/styles.css
if anyone can figure out how to fix this, i'd be eternally grateful. It's completely baffling to me and i've tried all kinds of options. i upgraded jquery to the latest version but then my scroller didn't work and i can't dive too much into the javascript code right now.
Please if you could help out, it would mean a lot to me. this has to go live sometime tomorrow.
There is a JS error when executing the following line of code document.getElementById("loading").style.display = 'none';
in the portfolio page.
Apparently, the element with id 'loading' is not being found. However, if I continue execution of the JavaScript on the page (from within the debugger), there are no issues, and the behavior is the same as in Firefox. This is indicative of a concurrency issue - the element 'loading' is not present in the DOM yet, but the script is attempting to change the element's style.
In order to fix this issue, you will have to ensure that the 'loading' element is present in the DOM before its style is being changed. In fact, you could delay the execution of the onload event handler (using window.setTimeout), until a point where the element is present in the DOM.
What's the actual javascript error?
And IE does have an issue in regards to invalid/broken markup inside of frames, I would try
a) commenting out each script and see which causes the js error
b) if commenting out all the js did nothing it might be related to the invalid markup inside of a frame issue, in which case I'd ditch frames alltogether.
yeah....
so thanks so much for your help. problem solved and i figured the other CSS error. should have picked up on that one earlier.
so site is working and if you want to see what happened with your help,
http://www.wither.org/Karoline
it works perfectly cross platform. made the deadline with hours to spare. thanks SO much. can't believe how well this worked.
I am using the Mootools Fx.Scroll effect to navigate horizontally through my website sections. Everything is working properly with Firefox, but Internet Explorer gives me some trouble. First the section were a big mess, but after adding one line in the Mootools core file thanks to a lighthouseapp.com patch, the sections are now well displayed.
My problem is that I can not go backward (to the left), only going to the right (again, it is only with IE...). The working demo is here.
After days of unsuccessful research, I am asking for your help, for any advice. I will provide any needed details.
Thanks a lot ;)
erm - couple of things.
you have commented out mootools 1.2.3.1 and gone back to 1.2.1, any reason for this?
you run to patch the framework using some code from the ticketing system, seems rather dubious to me and it most certainly should not be how you approach solving this. I am far from saying that mootools is free of errors but my point is that for such a simple transition, there can be a million other solutions than to look at the framework's ticketing system. all things being equal, it is safe to assume the problem will lie elsewhere... (and yes, I know of an error to do with Fx.Scroll that is still not patched but I don't think it would affect your setup).
for starters, my debugger on IE7 reports a JS exception on line 57 of your code:
if($('prog')) { // error somewhere here.
progBrowser = new ProgBrowser('prog',{
topX: '50px',
topY: '100px',
mouseOnColor: '#ffe400',
mouseOutColor: '#ffffff'
});
}
subsequently, a lot of code breaks and you get an utter mess on your screen. but there is nothing wrong with your instantiation - the problem is elsewhere: you have actually removed methods of the ProgBrowser class and left a trailing comma, check the bottom of the prog-browser.js file
}, // this comma will always break IE.
});
as for the scrolling problem, you can try using element.scrollTo(x,y) - but in any case, you have totally rewritten the normal event handlers for the class (replacing the click event with a onclick assignment etc) - fix the exceptions and post back your error-free page and we can look at doing scrollback again. good luck :)