Is there a browser that supports all the Confluence features best?
I know that IE doesn' support Drag and Drop, but what about other features?
check https://confluence.atlassian.com/display/DOC/Supported+Platforms
scroll down to "web browsers - desktop"
As webwesen's answer says, all browsers listed on the supported platforms doc should be usable with Confluence.
My personal experience is that using Chrome is a good bet, since most of the Confluence development team uses Chrome day-to-day (or at least they did when I was in the Confluence team). However, Chrome doesn't have a built-in WebDAV client which means that Confluence's Edit-In-Office features do not work. If this is important to you, then I'd suggest Firefox with the Office Connector Add-on installed.
Related
I'm sure like most developers, you have gotten your code perfect only to test it on IE7 and it doesn't look right.
My analytics say that IE7 is one of the lower ranking versions of IE being used to view my website. My question is why do people still use IE7? Isn't it easier to update to a better version of IE than to still be on 7?
I'm not sure why you would be on such an old version of IE unless you are not computer literate and only use it for basic tasks.
I tried researching on the web but no such luck. Any thoughts?
Some people simply don't have a choice if their IT department has not upgraded them. If you're building your application for a specific client, build it to the lowest version they have to support. If you're just doing this on your own to publish, then just support 'modern' browser versions.
Does anybody knows if there's a browser whith Web MIDI support? ... I've tried the samples on http://webaudio.github.io/web-midi-api/ but they throw me an error that my navigator has not such properties. Im working on google-chrome and firefox. If, there's no browsers that support MIDI, when do u estimate we will have one, maybe in the next 2 years?
According to this posting (dated June 28th 2013), "initial experimental support" for Web MIDI is now available in Chrome Canary.
As of now, there are no browsers that support the Web MIDI API yet. First off, the spec isn't finalized yet and there were a couple of changes made from the original spec (function names and procedures could change anytime).
You can, however, enable your browser to support the API by installing the Jazz plugin and using Chris Wilson's Web MIDI API shim. I have personally tried it and it really works! :)
As of writing this, Web Midi is now available in regular Chrome (not just canary), though it is still an experimental feature, so it must be enabled manually at chrome://flags/#enable-web-midi
try this one, jasmid to play midi files directly on chrome/ff, no plugin needed
One of the authors of the Web MIDI API has created this shim, which enables you to work with the Web MIDI API in today’s browsers:
WebMIDIAPIShim
https://github.com/cwilso/WebMIDIAPIShim
Google has taken up the implementation of WebRTC in Chrome very seriously as indicated by the frequent updates in the Canary and Beta channel of Chrome. Are there any other browsers who are upto implementing this?
Firefox/IE/Opera are working on it. No word from Apple/Safari or Microsoft/IE, although IE is unlikely at best, because they're working on their own standard unfortunately. Crazier things have happened, but I wouldn't count on it. Apple has been fairly mum on the subject.
If you want support for those other browsers, we built a solution for it # Frozen Mountain (I work there) using IceLink.
Opera Mobile does offer support to WebRTC. And according to this article, Mozilla isn't all that far behind either. Ericsson Labs has their own custom browser which supports WebRTC. But it runs only on Ubuntu as of now. WebRTC itself is still under development and I'm sure that we can see complete support from all major browsers in some time.
Mozilla is far along in implementing WebRTC, and we're leading the design and implementation of DataChannels within WebRTC, as well as Identity work. We're working on a project-specific repo right now (alder), but pieces have already moved over into mozilla-central, such as initial support for getUserMedia.
what language should be used to make a website or a webpage which will combine with the browser or the add-ons installed in the browser or the website can even takeover control of the browser ? Is there any language ?
I do not see the language as a factor in your question. Browsers use well-defined interfaces. Software that interacts with a browser can be written in any language as long as it supports those interfaces.
Beyond that, you would need to better define what is meant by "combine with the browser". Having websites "takeover control" of the browser is a dangerous thing and, in general terms, is not allowed.
However, there are plug ins that can be downloaded and installed and will work with the browser. Again, you need to be much more specific about the task you are talking about.
Without more information its tough to answer this.
For code that runs on the browser look at javascript or better yet JQuery which allows a lot more functionality and handles a lot of the cross browser problems for you.
If you're looking to get further integration going then you're going to have to take a different route for each browser. Firefox allows you to develop add-ons to add functionality to the browser, as does chrome. For IE you'll have to look at ActiveX
However for anything more than simple javascript you're going to have to get your users to allow your site to install whatever addons you use. Most users, myself included, wouldn't allow your site to install additional content on their browsers unless they really trusted the site and there was a strong functional incentive to use the code.
I would like to know what the members of this great community think of developing and adjusting their web apps and sites in general to recent Google Chrome beta browsers on Linux and Mac OS X and of course Google ChromeOS.
Do you think it's too early and I shouldn't waste my time adjusting myself to something that might change due to bugs resolutions?
Thank you.
Since Google Chrome uses Webkit you could also (as an alternative) test against Safari or Konqueror instead. Chances are your test results will be very portable across these browsers.
I think you answered your own question. While it is good to test against multiple browsers, there is very little point in testing against a beta browser - especially one with as little marketshare as Chrome.
With that said, the only reason I could see testing against a beta browser, is that you want your website to look good in it as soon as it is released and becomes mainstream. But, I really only see this need arising for the browsers that, again, are more popular.
Code against the standard, if you code it right the browsers will move toward you - rather than you constantly playing catchup.