My offline app works great for the most part.
I see my files have been cached in preferences > Safari.
I added this to my .htaccess file:
AddType text/cache-manifest .manifest
AddType text/cache-manifest appcache manifest
AddType text/cache-manifest appcache
AddType text/cache-manifest .appcache
My cache.manifest file is complete with all perimeters filled in.
My app launches fine, but when I try to hit the first button to continue, it tries to save data to local storage and fails to allow me to continue. If I turn my Wi-Fi on and use my offline app it works.
Solution:
It turns out you cannot have tags in your offline app. I had to put my form in as a div and use an onclick.
Related
I've started to notice this error on my Chrome dev tools. It appears after every http request.
Resource interpreted as Script but transferred with MIME type text/html: "http://www.superfish.com/ws/sf_main.jsp?dlsource=diigo&userId=153ec8d45ab00bb0221c814e5d659bee"
I logged on to Superfish.com and I've not used any of their service to my knowledge.
What is this notice/error exactly and how do I fix/get rid of it?
Superfish is adware, commonly bundled with existing Chrome extensions. You should look through your list of extensions and check whether there is any suspicious-looking extension.
Find and remove Superfish
Locate your Chrome profile directory. The default locations are listed at User Data Directory on chromium.org.
Go to the Default\Extensions subdirectory of your user profile (if you're using multiple Chrome profiles on your computer, "Default" might be something else).
Search for "superfish", and you will quickly find a file that contains this phrase.
Look at the path (e.g. C:\Users\Administrator\AppData\Local\Google\Chrome\User Data\Default\Extensions\jcheapnmfbmcccnbjhhkmleoiljgpmkl\js\sf-inject.js) and copy that 32-character phrase.
Go to the extensions page in your Chrome browser (chrome://extensions/).
Search for the extension with the given ID, and remove it.
How to identify bad extensions
Now you've removed it, you should take precautions to not get such extensions again.
Fortunately, there are some indicators that you can use to spot such extensions:
They require the "Access your data on all websites" permission.
Most extensions don't need this permission, be suspicious if you see it.
They are relatively popular (a few thousand users at minimum).
They are used for entertainment. In particular, if the extension "enhances" Facebook, you can almost be sure that it contains some form of malware.
Their description look more like an advert than a neutral description of features.
If you know a bit about code, I recommend to install my Chrome extension source viewer for reviewing the source code of Chrome extensions before installing it.
Note that the non-existence of adverts is not a guarantee for adware-free extensions. If the extension requests lots of permissions and it is owned by a poor individual, then it has a high likelihood of being compromised (I was offered 10k $ per month for a popular extension with a few hunderd thousand users. I resisted the offer, but I can imagine that many others do not).
To extension authors
If you are contacted by Superfish (or any other ad agency), reject the offer. Bundling adware without the user's consent is forbidden according to the Single Purpose policy.
An extension must have a single purpose that is narrow and easy-to-understand. Do not create an extension that requires users to accept bundles of unrelated functionality, such as an email notifier and a news headline aggregator. If two pieces of functionality are clearly separate, they should be put into two different extensions, and users should have the ability to install and uninstall them separately. For example, functionality that displays product ratings and reviews, but also injects ads into web pages, should not be bundled into a single extension. Similarly, toolbars that provide a broad array of functionality or entry points into services are better delivered as separate extensions, so that users can select the services they want.
I had the same problem - spent hours debugging and adding these to .htaccess but didnt work:
AddType application/x-javascript .js
AddType text/css .css
AddType text/javascript .js
AddType text/css .css
AddType font/ttf .ttf
AddType font/eot .eot
AddType font/otf .otf
AddType application/woff .woff
AddType font/woff .woff
AddType font/opentype .woff
AddType application/x-font-woff .woff
AddType application/vnd.ms-fontobject .eot
AddDefaultCharset UTF-8
Options -Indexes
When I finally found the issue, I realized that while localhost work, the server did not accept the path
\js\prettyPhoto\js\jquery.prettyPhoto.js
instead of
\js\prettyphoto\js\jquery.prettyPhoto.js
The CAPITAL p was making all those errors!
Do you use the Better History Manager extension?
The error disappeared when I was disabled it.
Using mediaElements.js, my video and audio test work fine in Safari/Chrome on the Mac but not in Firefox (14.0.1). See:
http://global-arts.4pixels.co.uk/global-arts-kingston/events-detail-mediaElement.html All the controls load and when you hit play it looks like it's loading, but then that stops and nothing plays.
To see if my .ogv and .webm files work I have a version of the page without MediaElement.js which is here:
http://global-arts.4pixels.co.uk/global-arts-kingston/events-detail.html and it loads OK, though in Firefox it takes a while to load. My .htaccess file has all the correct filetypes.
Having tested with video.js and still finding it didn't work in Firefox, I found it worked locally. Solution was to re-order the stack in .htaccess to have .webm first:
AddType video/webm .webm
AddType video/ogg .ogv
AddType video/mp4 .mp4
AddType video/x-m4v .m4v
Only took a weekend to find the problem :-S
I am trying to use the mediaelement.js library with Drupal. When I install the mediaelement drupal module and js library I am able to play MP3 files on all browsers except Firefox. It appears there is an issue with the Flash Fallback. But on the mediaelement.js page I see the MP3 player working in FF.
How can I diagnose this issue? What steps can I talk to find out if it is this version of the JS library, the Drupal module, or something I am doing.
I had the same issue, there are 2 things I suggest:
Add MIME-Type:
Add new mime type for your media types into your server config or directly in .htaccess
E.g. in my case I added
AddType video/mp4 .mp4
at the end of .htaccess to make it work in FF
Make sure that mediaplayer is initialized correctly and that all paths are set
up correctly. Check pluginPath and flashName properties.
Check http://mediaelementjs.com/#installation for more info.
I have a simple HTML file which references .gadget so that it can be downloaded:
Download me!
IE, Opera, Safari and Chrome all offer saving file to disk, however Firefox loads binary file in a tab. Why does Firefox hate me and what must I do to force Firefox to offer download dialog?
I don't really want to instruct users to "right-click and choose 'save file as'", or that they have to remove .zip extension after downloading.
Server is Apache/2.2.17, in case that it's relevant. Interesting fact is that Firefox does behave like all other browsers - if I load open .html file from local disk. But once it's on the server, it loads file in a tab.
So, here's the solution.
The problem is that Apache returns Content-Type=text/plain HTTP header by default for all "unknown" file types. Firefox adheres to the standards unlike all other browsers so it displays the content. Here's what they have to say about it. You can inspect header in Firefox with Firebug (or simply use curl if you're on Unix).
The above link also hints the solution; register application/x-windows-gadget MIME type with the server. If you don't have access to the server configuration, put .htaccess file in the same directory as your file (or in any of the directories above your directory) with the following line:
AddType application/x-windows-gadget .gadget
After that, don't forget to clear your browser cache.
Joomla 1.5.22 new installation, no extensions added. I've only configured the Global Configuration pages. For some reason, I can't upload any pictures, either in articles or in the media manager. "Start Upload" does nothing, it just sits there.
The only thing I could find on this was a folder permissions issue and and so I set Images and all sub-folders to 777, but that still didn't help.
Any thoughts on what could be causing this and how to get it to allow for pictures to be uploaded?
First off change your folder settings back from 777 to something more secure (664 or 775). Then Prakash could be correct in that the flash uploader is not working on your system and you can disable it and use the normal file view uploader. Try that and let us know.
On global configuration, in media settings you've enabled the flash uploader which disallows to upload the files for some reason. Disable it, now you'll be allowed to upload files again