I'm trying to use a jquery-plugin called bigText. An awesome plugin for create block-headers. If you want to use this with a custom font, it states that you need google webfont loader, this way you can use a callback to trigger the plugin AFTER the #fontface has loaded/rendered.
It works fine in FF, Safari, Chrome, but it keeps crashing ie6-7-8, hard. A soon as the page loads it says it has an error and asks if you want to send a report to MS.
You can check out the code here
I'm sure this is triggered by the Google font loader, When commenting out all the other parts of the code it still seems to crash. When commenting out the google font-loader bit, all the other things work => font loader only example
Has anyone here ever experienced a bug like this and maybe found a solution?
First of all, I have had the same bug.
The first note is that you must reproduce the bug on NATIVE IE 6-8, not IE 9 using the Dev Tools -> Browser Mode.
I have isolated the bug to an incompatibility with Modernizr 2.5.2, simply upgrade your modernizr build and you'll be all set~
EDIT - Just upgrade to the latest version 2.5.3 of Your Build Here
Edit 2 — Verified that it's fixed on our Orlando Web Design Page
Related
I have tried pretty much every which way to configure the Google Invisible reCAPTCHA widget, but there is always an issue with the latest Firefox browser, detailed as follows:
add the plugin to a web page, which has other JS such as a dropdown menu
load the web page
keep loading the web page over and over, in an attempt to catch it 'half loaded'
eventually you will see for a split second an alert "The page at https://www.google.com says: Cannot contact reCAPTCHA. Check your connection and try again"
from now on, JavaScript is entirely broken until you restart the Firefox window
This never happens in Chrome, and appears to be Firefox only. I am surprised to not find any reports of this major issue with vendors Google and Firefox (unsure which party is to blame), so created this ticket.
This issue can be replicated on the official Google Invisible reCAPTCHA Demo by quickly reloading the page. This will eventually show the alert and break the entire demo, making all form inputs unresponsive until the Firefox window is closed and re-opened.
At the time of writing, I am using OSX Firefox 57.0.1 (64-bit) to replicate this issue, but has also been replicated on the same Firefox under Windows 10.
Update after valid comment from Federico, as this is being reported a lot but no solutions or workarounds that I can find: Google Groups Search
Is this a known issue and are there any plans to resolve from either Firefox or Google, or more importantly has anybody managed to put a workaround in place in the meantime?
I think the issue is resolved now. Try again and it is giving successful verification. I guess it was a bug which they fixed. If the problem still persists please try upgrading Firefox to the latest version.
I'm using Firefox v47 on a Mac. I've worked out how to get the Debugger to use JavaScript source maps to show where I'm triggering some code, but it uses the compiled file in the Console. How do I get it to show me the uncompiled file lines?
This works out of the box in Chrome, so seems an odd omission in Firefox so I'm assuming I've done something wrong.
In the Firefox Toolbox Settings, enable the option Show original sources in the Style Editor area. This option should, however, be enabled by default in all Firefox versions >= 35 (source)
There is a seperate article about source map support in Firefox that elaborates on the minimum required Firefox version for sourcemaps to work (Firefox 29).
Also, keep in mind that not all SASS-generated files come with sourcemaps - this is a feature that must be manually enabled with the --sourcemap argument if you're using it from the command line, by rendering it with render_with_sourcemap from within a ruby program, or by other means if you're using a task manager such as gulp or grunt.
You can check if your stylesheet has an associated sourcemap by looking at the last non-empty line of your generated css file - it should look somewhat like this:
/*# sourceMappingURL=style.css.map */
As of now, this is still a work in progress, see the related note on MDN and a bug ticket describing the problem that brought me to this question. So, for now, source map seem to work well everywhere except in the console.
UPDATE #2
So we found out how to debug our application utilizing the safari debugger. For those of you interested, here's the link on how to do this:
http://appletoolbox.com/2014/05/use-web-inspector-debug-mobile-safari/
Using this, we figured out that our issue was actually related to CSS that we were using in our code. In our body class, we had the attribute "overflow-y: auto". Upon deletion of this line of code, everything worked again in mobile safari.
~~~~~~~~~~~~~~~~
UPDATE: Upon further testing. It looks like if I go to the web version of this application (hosted on our server) from the safari app on our iPad, this bug still happens. If I do the same on the mac version of safari though, then this bug does NOT happen. Hopefully this information might be helpful.
~~~~~~~~~~~~~~~~
So we have a javascript hybrid application that's compiled using the trigger.io toolkit. Jquery, backbone.js, and marionette.js are use in this project. We just started testing on iOS devices.
Everything works fine on both the web / android versions of this app, but on iOS (both simulator and device), the following bug is occurring:
Upon loading up the application, on the first view, when you first tap into a text field the application freezes briefly. After the application unfreezes, the following error code is output into the trigger.io console:
_BSMachError: (os/kern) invalid capability (20)
_BSMachError: (os/kern) invalid name (15)
Everything looks fine, but then if you type more than one letter into the textfield, the entire application disappears except for the background view. You can tap out of the text field, and everything returns into view, but obviously this is something customers shouldn't be experiencing.
I've researched a bit, and some suggestions have said to try and edit the info.plist file. I've looked everywhere, but I can't seem to find this file. It's seeming like trigger.io hides this from the developer somehow.
Does anybody have any ideas as to what might be causing this issue or how to fix it?
Thanks!
So we found out how to debug our application utilizing the safari debugger. For those of you interested, here's the link on how to do this:
http://appletoolbox.com/2014/05/use-web-inspector-debug-mobile-safari/
Using this, we figured out that our issue was actually related to CSS that we were using in our code. In our body class, we had the attribute "overflow-y: auto". Upon deletion of this line of code, everything worked again in mobile safari.
I know that there already is a question like this: Force IE9 into browser compatibility view
But since adding:
<meta http-equiv="X-UA-Compatible" content="IE=9">
to the the head section and reloading the page with ctrl+F5 didn't help there must be another way.
On my website is also a bxslider and according to this: bxslider not working in IE9 I replaced the elements (which had empty href attribute) with tags - still not effect. The images of the slider are displayed in full size one below the other. After activating compatibility mode the site works perfect.
I don't wanna rebuild my application from the scratch so what could I do to force the compatibility-view? Or is there at least a good free debugging tool for that? I downloaded the firefox addon IE Tab which has a debugbar but to use it you have to buy a premium version. I just don't know what is causing the error...
I found what was causing the error: Why does JavaScript only work after opening developer tools in IE once?
So frustrating and so simple. It was caused by the console.logs in the script. Without them it works like a charm.
If you use this code at the start of your JS (I use it in all my projects) https://gist.githubusercontent.com/elijahmanor/7884984/raw/console-monkey-patch.js it will override the console.log function so you avoid errors in IE but still get logging in modern browsers like chrome.
I have a page in which I use jQuery for damn nearly everything, thus I find it kind of problematic when jQuery won't load in IE8 (works fine in IE9 and, I presume, IE10).
I've tried all the usual trickery: putting jQuery at the top of the header and I am loading the file from the same site as I am trying to run. I always do these things, but now you know ;)
The IE8 console isn't to much help, as it just bangs on about stuff being undefined, and not having this and that property and method. All i can get out of it is that the jQuery file is being loaded (it finds errors in that too :/), but for same reason it isn't working.
If someone would be so kind as to have a look at it, this is a link to the actual page.
jQuery 2.0 completely dropped support for IE 8. You need to use 1.10.2 to support IE 6,7,8
They both currently have all the same features and functionality but 2.0 and up is smaller in KB due to dropping legacy code for IE and earlier.
60% of my visitors are on IE8 so I will be using v1.x for a long time
It's not surprising that this doesn't work, because jQuery v2 does not support IE8.
It says so very clearly on the jQuery site.
You need to use jQuery v1.x if you want to support IE8 or earlier.
(the functionality of v1.10 is identical to v2; the only difference is that v2 removes all the extra code they had in there to support old IE versions)