I know firefox does not support MP4 and I understand the reasons for that. I'm developing an html5 video framework and I strongly prefer firebug to Chrome's debugging tools and because of this, I am very interested if there is any way via extension paid, free or otherwise to add mp4 support to firefox for my personal use.
Anyone know of any tricks?
EDIT:
Clarifying my Question. I am only testing the html5 implementation while the flash implementation is handled separately. This is a widget / CMS driven framework and feature parity is not limited to video, so I have to spend a lot of time in the debugger. A lot of listeners in the video trigger other functionality, leading to very large call stacks. Because of this, debugging in firebug vs chrome isn't trivial for me.
The simple answer is no, however you can fallback to a flash player that supports H.264, this will also ensure compatibility with older browsers.
Microsoft released an extension for Firefox 3.6+, but it requires Windows 7 and doesn't add some kind of native support, but rather causes similar effect as if you'd use <embed> instead of <video>.
Related
we are using jquery in our project and we were thinking about to implement a function for offering a drag and drop download from our website to the local underlying file system (Desktop for example...).
I found some useful links but all of the seem to be outdated:
http://ankurm.com/html-5-dnd-download-a-quick-implementation/
http://www.html5rocks.com/en/tutorials/casestudies/box_dnd_download/
https://www.salesking.eu/blog/coding/jquery-plugin-to-drag-files-from-browser-onto-desktop/
My questions:
Does anybody knows a overview of Browsers and their versions which support this feature?
I read its a part of HTML5 but not every HTML5 browser is supporting this feature. More worse: in one of these links users wrote some Browsers were supporting this feature but after a while the support was removed...
Does anybody knows a up-to-date howto how to implement it "nowadays"?
Thx in advance!
http://caniuse.com/#feat=filesystem
Pretty much Chrome and Opera these days, most API filesystem support was removed from other browsers and the standard is going to pretty much defunct.
I want to develop a browser plugin for RTSP streaming on web browser, I read about NPAPI, which can execute native code(C++). But Google Chrome will not support NPAPI in future and no guaranty about Firefox also.
Please somebody can suggest me to "How can I develop plugin which can execute native code(OR any other language) using other framework instead of NPAPI?".
How can I add RTSP Streaming support for web browsers?
I'm afraid you cannot implement universal plugin at the moment. It's possible to write extensions for Chrome and Firefox which support TCP and UDP sockets (Chrome API, Mozilla API ). No such thing for Microsoft Edge or Explorer or Safari as far as I know.
If using different streaming protocol is an option, consider WebRTC. Its support is still not very good, but at least WebRTC is an official standard and has better chances of being adopted.
If you plan to develop an extension for the major browsers (IE, Firefox, Chrome and Safari) then I'd suggest looking into the kango framework. It takes a common code base and converts it into plugins for 3 of the 4 major browsers (for IE you'll have to contact them)
Is there a way to port a chrome extension to other browsers, without having to entirely re-write the code? My chrome extension uses the browser_action command to open "popup.html" in the extension window...
Update: I found adblockforchrome port.js and found it only somewhat helpful for porting to Safari...
Apple provides some guidance on how to port convert a Chrome extension to Safari, but the problem you're going to run into is that each browser has a different set of allowed functionality for extensions. Even with Chrome to Safari, there are things you could do in Chrome you can't do in Safari, and visa versa.
It depends on the type of the extension, but not really. To answer your question more clearly, you need to specify what your extension is about: modify some pages (like userscripts/userstyles), extend browsers' features, or something else.
There are a few portability notes, however, that could help you to simplify this process:
Don't write browser specific code. In some modern browsers you're able to use HTML5 features, like Web SQL Database API. It is difficult to emulate such behaviour on IE, for instance.
Keep your JavaScript modular; don't use vendor specific JavaScript methods, and your code will be portable and will not rely on TraceMonkey or V8;
Separate HTML from CSS and Javascript, don't make your code dirty and complicated.
Jumping in a bit late.
Our company - Slice Factory (full disclosure here!) does provide a browser extension conversion service: http://gallery.extensionfactory.com/labs/conversion/
In most cases your chrome extension will work seamlessly in FF and Safari.
The service is still in beta trial, and Firefox conversion is working better than Safari one.
I can't fully disclose what's our technical solution, but this being an SO answer, I can add a few details: we have re-developed a full javascript api stack that mimics most of chrome extension APIs for Safari and Firefox; in Firefox we base our work on JetChrome. Plus we have wrappers that re-package the chrome extension adding our library and rewriting manifests and so on.
Beyond that, it's mostly a few good ideas, trial and error, and a LOT of development time.
As an example:
Safari 5.1 just introduced a popup corresponding to Chrome's browser_action, but we have already an alternative solution that works for previous versions. Firefox does not support HTML5 WebSQL, but we have an API for it. We also provide a way to bring webapps to FF, and soon to Safari.
The objective is to have Chrome API as a reference, and mimic it on all the other browsers.
Without pushing you towards our solution, I might add that the time to fully cover the Chrome API on both Safari and Firefox is probably not worth it - unless you plan to convert several extensions. So for just one or two extensions I would advise making your code as modular as possible, and just creating three extensions - or trying our service!
Yes, it's possible with Webextension API using webextension-polyfill.
I made use of it to build this where I only had to change the callback methods to Promises and using browser.something instead of chrome.something to call the browser APIs.
What about support for major browser? IE 6+. FF 2+, Opera 9+, Safari 3+, Google Chrome?
It is good idea to use actionscript to generate graphics (interface developed in JS and standard HTML forms)? Maybe its better to use canvas? What about performance?
I would start with the flash.external.ExternalInterface object.
ExternalInterface is AS3 specific. For AS2, use fscommand. I can't vouch for it though, as I haven't worked in AS2. As for AS3, I've used ExternalInterface successfully in FF(3+), IE(8) and Chrome. Haven't heard anything about it not working in other browsers either.
As opposed to using Flash for the whole form? Yeah, that way the form will be accessible to users who don't have flash too.
Given that you're targeted browsers include IE-6 et al, Canvas is hardly an option. According to the linked article, no version of IE supports canvas yet. Even FF started supporting it from FF3.
About performance, its hard to say without knowing what you are trying to do.
It's the year 2009. Internet Explorer 8 has finally been released, and Firefox is coming up to 3.5. Many of the large browsers are starting to integrate features from CSS3 and HTML 5, or have been doing that for quite a while now. Still, I find myself developing web pages exactly the same way I did back in 2005.
A lot of progress has been made since then, and I think the reason that I haven't started taking advantage of these new possibilities is that it's so hard to know which of the new features that work in all major browsers. Since I'm mostly a backend developer I just don't have the time to keep up these developments anymore. Still, I feel like I'm missing out on a lot of cool stuff that actually would make my life a lot easier.
How can I quickly determine if a feature of CSS3 or HTML5 is supported by all major modern browsers?
Can I Use is a website which tracks browser support for current and upcoming web standards. Check it out if you would like to know whether or not a given feature is widely supported.
Font embedding through CSS, using #font-face. Webkit/Safari has been supporting it since version 3.1, Microsoft since IE4, Mozilla since Firefox 3.5 (browser support overview).
Also, the varied implementations of the Selectors API, which provides a browser-native CSS selector engine for use in DOM scripting.
For other examples, When Can I Use... seems to be a very good reference.
I would say display:table and a range of CSS2.1 selectors are the big wins for designers. display:table solves some unsolvable or difficult layouts like 100% height and inside borders without breaking semantics and using actual tables.
Multiple classes (.c1.c2)
I use min/max-width/height a lot.
Also working :hover and !important are awesome.
I would have liked to add SVG support to that list but naturally Microsoft messed that up.
BTW, big warning to those getting excited about HTML5 features. There is no official date for the adoption of this spec. It's even been implied it could take another 10 years (though I doubt that). The point is anything you do with HTML5 now is subject to breakage when the official spec does arrive and in the meantime you can expect plenty of browser inconsistencies, bugs and API changes (not to mention browsers that don't support the features at all).
Browser support for local storage should enable a bunch of new ideas now that some content can be saved on a user's machine.
Reference docs:
Mozilla Firefox
Internet Explorer