I just upgraded my mac to Firefox 3.6, and now neither of my TIFF Viewing plugins work.
in 3.5, If I had Quicktime on, then I'd get the tiff, viewed through quicktime. If I had Quicktime disabled, but my own plugin, AcellViewTIFF enabled, then I would get ViewTIFF viewing the TIFF. Since I'm the author of ViewTIFF, That's how I had it most of the time.
After I upgraded to 3.6, if ViewTIFF is enabled, I just get a blank space. if ViewTIFF is disabled, no matter whether or not Quicktime is enabled, it goes straight to preview.
Has anyone seen this?
(This is programming related because I'm writing AccelViewTIFF, and if the framework for plugins changed, I need to fix it...)
Edit to add:
This is an NPAPI plugin, I've removed or commented out the main, so I don't think that this is a CFM plugin problem.
I looked at Mozilla's "basicplugin" (located in mozilla-1-9-1-f15a2686e9a6/modules/plugin/sdk/samples/basic/mac under the standard mozilla source) and it works. I compared all of my functions to the functions in BasicPlugin, and the only function that it has that I don't is the drawPlugin function, which appears to do the actual work. All equivalent functions have the same interface.
When I remove or disable AccelViewTIFF, Firefox downloads the image and gives it to preview. When I enabled it it does nothing. This tells me that Firefox IS seeing that I have a plugin, but it's not running it for some reason.
There are no errors either in Firefox's error console or in any of the console logs I can see...
any ideas?
For the record, the problem was that this is an OLD plugin that still uses Quickdraw routines. evidently, they didn't make it into 64b, and so they don't work in FF 3.6.
Lets hear it for progress.
Are you using Leopard or Snow Leopard?
TIFF files open fine with the QuickTime 7.6.3.0 plugin with Firefox 3.6.
Go to Firefox -> Preferences -> Applications. Search for "tif" and then you can choose how Firefox handles files with the image/tiff MIME type. Set it to the plugin of your choosing. QuickTime should work (is for me on Snow Leopard).
Related
The "Warn Before Quitting" feature stopped working for me. When I click Cmd-Q Chrome closes immediately instead of showing me the "Hold ⌘Q to close" message.
I want to debug the code responsible for that, but I can't seem to find a way. On Windows I can attach to Chrome, get the PDBs from Google's symbol server, and get the appropriate sources using SrcSrv.
Is there anything similar on OS X?
(Firefox apparently has a script to download symbols for Linux/OS X, though I never tried using it.)
It doesn't happen on another user on my machine or on Chromium. I tried copying my profile to ~/Library/Application Support/Google/Chrome of another user and to ~/Library/Application Support/Chromium (for a Chromium build I made). In both cases the bug did not present itself (though other bad things have happened), so using Chromium doesn't seem like a solution.
(Although I did build Chromium's HEAD rather than the tag corresponding to the version of Google Chrome I'm running. Maybe if I do that I would be able to reproduce the problem in Chromium. Nonetheless the question remains.)
Is it possible to perform source debugging of Google Chrome on OS X? If so, how?
Note: I'm not interested in attempts to solve the "Warn Before Quitting" bug, suggestions to report it to Google, etc. That's not the point. I want to be able to debug Chrome myself.
So in our application, a video preview is displayed after it is uploaded. On my computer, however I'm getting a thumbnail that says 'plugin missing' and upon further inspection it says to install the quicktime plugin.
However, the link provided by Chrome to install the plugin leads to a page on apple's website which says 'quicktime plugins don't need to be installed anymore.'
Some details:
Video Extension: .mov
Codec: H.264, AAC (which may be what is in question here)
Chrome Version: Version 39.0.2171.71 (64-bit)
OSX Mavericks
How do I go about making videos play on my machine, as well as making sure that they show up in the production environment?
Google Chrome has removed support for plugins like Quicktime. Most likely you are also using Chrome 64bit. The Quicktime Plugin was only for 32bit.
HTML5 supports videos out of the box so the browser developers of IE, Firefox and Chrome do not see any more use for such plugins.
Is it possible to access the clipboard in a Firefox OS app? If so, how? I know Internet Explorer has a way to do this using window.clipboarddata. However Firefox has never supported this. Do they use this method for Firefox OS or is there a different method or none at all?
This is not implemented yet, but it is planned for a future version. There is a meta bug for copy & paste support in Firefox OS that you can follow to track progress. It seems that Gecko already supports some Clipboard API events, but there is no UI yet for copy-paste in Firefox OS.
I'm writing this HTML5 music player that works by dragging music files onto it. (will soon use WebRTC too)
http://pepijndevos.nl/KjuMusic/
It works in Chrome, it used to work in Firefox, and still does on a friends Mac.
However, on my Xubuntu laptop, both with the default and the nightly Firefox, I get
FileList { length=0, item=item()}
when dropping one or more files. I'm not even sure anymore if this is a bug in my code, Firefox, or somewhere else in xfce.
Which file manager are you using? HTML5 Drag&Drop used to only work with Nautilus for a long time. As of this writing, PCManFM works as well, but Thunar still doesn't.
Current versions for future reference:
Thunar 1.6.3
PCManFM 1.1.1
Nautilus 3.8.2
There's also a Firefox Bugzilla entry regarding this problem: https://bugzilla.mozilla.org/show_bug.cgi?id=609284
I'm looking into chrome frame and I'm wondering how it works.... http://scriptsrc.net shows that it's a javascript that can be embedded on the page....
http://code.google.com/chrome/chromeframe/ shows it as an install file... does the JS prompt for an installation or something?
Google chrome frame is a plugin (think Adobe Flash) for Internet Explorer, that replaces core modules of IE (unlike Flash), like layout/rendering and javascript. But the UI remains. Then there is some javascript that can detect if this is real IE or IE+Chrome, and also offer an install option to the user. Also there is a HTTP-header and a meta-tag that are required to switch IE to chrome mode, when available.
The JavaScript is to detect it and enable it if it's there. (scriptsrc is just giving you the link to the file, which is on the Google CDN.) The end user does have to do a one-time install of it, it's a plug-in (like Flash or Java). Quoting from this page in the Google documentation:
In Internet Explorer, check() determines if Chrome Frame is installed. If not, the user is prompted to install it.