I am looking at KendoUI for a js app that will run in house. I download the kendoui (either opensource or the latest from them) and follow these very simple directions:
http://docs.kendoui.com/getting-started/introduction
Doing exactly as they suggest results in a js error of (same js error if I run the files through a local apache server or directly as file:// in Google Chrome).
Uncaught SyntaxError: Invalid regular expression: missing /server/js/kendo.web.min.js:10
Uncaught TypeError: Object [object Object] has no method 'kendoDatePicker'
What gives?
The js files are found and loading. But it chrome complains about
GET http://0.0.0.0:7773/server/js/jquery.min.map 404 (Not Found)
Perhaps these instructions are old?
Update:
It appears that the js files in the Kendo downloads are corrupt today. It works if I either link directly to the Kendo CDN, or if I download web.ui from github. Its not my zip expansion software (OS X 10.8), as the query 1.9.1 included in the kendo download works perfectly.
This is due to a known issue. Long story short you need to download the bits again and use the updated JavaScript files.
Related
I'm using Laravel 8 on Heroku and keep getting 404 errors for some fonts. This just started happening earlier today but I haven't changed any of my code in several days.
This is a sample of what I'm seeing from laravel's error handler:
404 - https://www.example.com/%7B%7BEXTENSION_BASE_URL%7D%7D/b06871f281fee6b241d60582ae9369b9.ttf
404 - https://www.example.com/%7B%7BEXTENSION_BASE_URL%7D%7D/fee66e712a8a08eef5805a46892932ad.woff
404 - https://www.example.com/%7B%7BEXTENSION_BASE_URL%7D%7D/af7ae505a9eed503f8b8e6982036873e.woff2
I searched my entire directory for EXTENSION_BASE_URL and it doesn't exist anywhere in my code.
The user id's associated with these errors are not unique and it seems to be happening to multiple people. It's the same three font files as above each time.
My best guess is there's some kind of plugin people have installed that's trying to use a custom font that doesn't exist. I can't find any reference to EXTENSION_BASE_URL when I do searches online, so I can't figure out where it's actually coming from.
The only custom fonts I use are an import for Raleway from the Google Fonts API. I have jQuery 2.2.4, Bootstrap 3.3.7 and FontAwesome 5.4.1 which might also be including fonts with their CSS. Aside from the Raleway include, the versions for the other CSS files haven't changed in a while.
Since it doesn't seem to be affecting everyone and I can't track down what these font files are, my plan is to simply exclude these font files from showing up in my logs. I'd love to know what caused this though so I can take any other action if necessary
We had this same problem with some of our users and we tracked it down to a browser extension called ProWriting Aid Grammar Checker which is for the website https://prowritingaid.com/.
In our case, not only was it creating the errors you mention with fonts, it also caused some JavaScript to execute improperly.
This extension is available on Chrome, Safari, Firefox, and Edge. We had users across all these browsers have the same problem. It is clear that the problem code is shared across all these browser extensions' code base.
Having users uninstall that extension solved our issues.
The latest dropzone.js version does not seem to work in IE11. How to test?
1) Open up https://www.dropzonejs.com/examples/simple.html in IE11
2) dropzone not clickable and files cannot be dragged and dropped
The error via F12 console is:
'Symbol' is undefined
File: dropzone.js, Line: 3196, Column: 11
if (_didIteratorError32) {
throw _iteratorError32;
}
How can this be solved?
I solved this issue by adding following script tag.
<script src="https://cdnjs.cloudflare.com/ajax/libs/babel-polyfill/7.8.7/polyfill.min.js"></script>
Dropzone.js had arrow functions and lot of other things which are not supported in IE11. Therefore, it converted from es6 to es5 using Babel.
After researching a bit found that it needed polyfill support and hence script.
I had same issue with 'Symbol' is undefined in IE11 with Dropzone.js version 5.7.0 release that was (at the time of writing) still referenced from Dropzone.js website.
Issue was actually solved just by downloading latest release from GitHub which (at the time of writing) was Release v5.9.2.
So no need for explicit babel-polyfill anymore.
https://github.com/dropzone/dropzone/releases
I solved this problem when I downloaded the script directly from the website https://www.dropzonejs.com/js/dropzone.js?v=1583771423.
Link to the tutorial
I am trying to get to grips with Firefox SDK development using the tutorials on MDN. The annotator tutorials seem very good but CFX Run fails on the first control stage.
The tutorial uses the widget API that was deprecated in Firefox 29 but I tried downgrading Firefox 28 and the tutorial still doesn't work even when I am copy and pasting the code directly from the page code. When I come to the end of the Implementing the widget page I only get the following message when trying to click the widget icon (the first time, then nothing hapens).
(C:\Users\myname\Firefoxplayground\addon-sdk-1.16) C:\Users\myname\Firefoxplay
ground\pageMod>cfx run
Using binary at 'C:\Program Files (x86)\Mozilla Firefox\firefox.exe'.
Using profile at 'c:\users\sigvard\appdata\local\temp\tmpg3kq0j.mozrunner'.
console.error: pagemod:
Error opening input stream (invalid filename?)
JavaScript strict warning: chrome://browser/content/urlbarBindings.xml, line 666
: reference to undefined property this._value
JavaScript error: chrome://browser/content/urlbarBindings.xml, line 648: aUrl is
undefined
The issue was caused by a bug in the Firefox SDK.
Updating to Firefox SDK 1.16 and initializing a new folder for the project solved it.
I'm using valums file_uploader.js to upload files & I wanted to upload all the type of files like images, audios, videos, etc. It is working very fine in firefox & chrome. In safari upload is working good except for multiple files. But in IE nothing is working.
There is one line input.files to fetch the file details. It is giving null or undefined in IE.
I tried all the versions of IE, 7-9. But no use.
How do I get the file properties in IE using javascript. I tried to use ajax-uploader, but I'm not getting how to use it.
I'm using ruby 1.9.2, rails 3.2.1 & jquery 1.7.2. is it any problem with the versions?
Thanks in Advance.
I am trying everything under my power here to insert jquerymobile.1.0.1 into an extension I have build for firefox.
I can install, link to any other script and everything seems to work just fine, but have had an assortment of errors getting jquerymobile to work.
I've tried uploading through the add-on builder
I've tried remotely linking the file
I've tried copying and pasting the file into other code.. nothing works.
I've coded this extension for safari, chrome and opera without issue, but Firefox chokes the second I link to/include jquerymobile in my code returning this error:
Timestamp: 12-04-27 12:10:33 PM
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMHistory.replaceState]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://jid0-d4zlaxz3cfuahkcdoecsmya637m-at-jetpack/idesireit/data/js/jquery.mobile-1.0.1.min.js :: :: line 72" data: no]
and also an error about "unallowed unicode" which I didn't get the chance to copy or paste, but I haven't seen that one in a few saves...
I've read that the above error can be caused by cross domain functions, but all my cross domain functions are in another js file, and they are all working just fine ( judging by those I can navigate to with jquerymobile acting as it is right now )
I'm a novice - if my error is based on my stupidity, please go lightly :O
I went ahead and created an all new extension,
included nothing but the popup, and in that pop up, called jquery and jquery.mobile.
I got this error instantly again.
I'm just going to go ahead and use the alternative UI I'm using on the dashboard widget, I've wasted too much time on this.
The bug is in the addonsdk, not in JQ Mobile. Any attempt to access or manipulate the window.history object in a panel will raise this error.