I went through an use case where my team has to choose a React component library. One of the evaluation criteria is the browser support, but the AntDesign docs says that it support the last two versions of the popular browsers: https://ant.design/docs/react/introduce#Environment-Support
Is it limited to the last two versions or are those only recomendations?
Other libraries like MaterialUI states very well which versions it supports: https://material-ui.com/getting-started/supported-platforms/
Related
I'm using Modernizr to make my HTML5 site backwards compatible. It's great, but is there a tool to run automated, headless tests which will parse my HTML for HTML5 features, then test each my code and its features in numerous browsers, and generate a report that I can use to add any polyfills I may have left off or know that I've successfully covered all of my bases using Modernizr?
unfortunately, no. Such a tool has not been made publicly available by anyone.
Even if there was, it would be extremely difficult to do properly. Some things have polyfills that shouldn't be used (see rounded corners and OldIE), or the polyfills that do exist may not be needed in some/most cases.
This is something that is best left to the developer to properly check and test during development.
My basic workflow whenever I am using a feature that I am unsure of, is
check caniuse.com, comparing the data to my own analytics to determine if I even need to detect it. if no - stop. If yes...
Add the Modernizr test for that feature. If a polyfill is needed, then...
Add yepnope test, loading one of the polyfills listed in the metadata filed of Modernizr v3 detect.
rinse, wash, repeat
Is it possible in any current browser (including, for instance, Chrome Canary)?
All the working examples I've seen are speech-to-text. Is there anything to either record audio or stream it to a server?
Update 4/30/2012:
The getUserMedia API is sloowwwwly making its way into browsers. It is in the latest version of Opera and apparently is in-progress in Chromium.
If you want a taste of how it will work, see: http://www.html5rocks.com/en/tutorials/getusermedia/intro/
There doesn't seem to be an implementation of this in current browsers.
There is a JavaScript API for getting access to microphone and camera planned:
http://www.whatwg.org/specs/web-apps/current-work/multipage/video-conferencing-and-peer-to-peer-communication.html#obtaining-local-multimedia-content
Also, have a look at this question:
How do I access navigator.getUserMedia()?
The standard versions of Chrome and Firefox fully support navigator.getUserMedia();
Numerous examples have been already made to record audio directly in the browser, in several formats even.
Here are a few examples:
This is a fully oriented project towards testing the limits and possibilities of the current state of webRTC
https://www.webrtc-experiment.com/RecordRTC/
I've personally made a record to mp3 library in JS sources can be found here:
https://github.com/nusofthq/Recordmp3js
Also for updates you can check the latest MediaStream Recording API proposal by the Media Capture Task Force. This is not yet implemented in the current browsers but it will in the near future.
a client wants to "modernize" a 5 year old web/html-based Blackberry "application".
The application allows field service technicians and franchisees to inquire on warranty
and service status. Currently they use very simple php/html pages.
Application seems slow, especially on repeated inquiries which require constant reload.
Blackberry/Java seems to be obvious choice, but client seems to think that
development and maintainace is expensive, which I suppose is true because this skill
is not very common around here.
I am thinking of maybe loading all pages in a single initial load and use a javascript
hide/show type technique to reveal pages as user requests them, and using ajax to populate/update data.
They want to target javascript enabled Blackberry devices (OS 4.5 and later). I know that issues and limitations
with css and js on early browsers. i would like to hear other people's experiences.
I know jQuery so that would be obvious choice, but it is pretty fat for wireless. Is there a better
toolkit for this purpose - I found the iqTouch site, but that was not Blackberry specific. Any sites with examples that I can harvest?
If you're targeting OS 4.5 and later, all I can say is good luck. BlackBerry support for HTML was pretty poor in older devices, and you're hit and miss at best with anything more than the most basic use of JavaScript. I've had very little luck with anything other than non-dynamic HTML websites with the older browsers.
With OS 5.0 and later you have a lot more options. Support for the Gears APIs and better JavaScript. The Widget SDK even lets you easily create HTML/JS based 'Widgets' for BlackBerry that can contain a bunch of pre-cached data. BlackBerry 6 of course, with its WebKit based browser and HTML5 support can do pretty much anything that iOS or Android devices can.
So my recommendation is to only go dynamic if you can target 5.0 and later. Or potentially a site that degrades gracefully to browsers that don't support JS well (either user agent detection or some fancy JS coding) and users with older devices have to deal with a slower experience.
have you looked at features available in HTML 5?
Do you know about useful resources about HTML5 & CSS3?
UPDATE:
I'm (and i think a lot of people) looking for practical information how and to what extent is it possible to use these unfinished technologies. I found one very useful resource:
http://caniuse.com/
For the gritty details when the metal needs to hit the road, go to the sources to lookup functions, objects, etc and get the latest info on them and their usage.
Implemented standards
Firefox
Mozilla Developer Network for Gecko engine
# https://developer.mozilla.org/en#Documentation
Internet Explorer
HTML, CSS, DOM object model
# http://msdn.microsoft.com/en-us/library/aa737439(v=MSDN.10).aspx
JScript (aka JavaScript)
# http://msdn.microsoft.com/en-us/library/hbxc2t98.aspx
Unsure about Webkit official dev docs (Chrome. Safari) but you can often use the MDC/Gecko docs because they are usually close in standards. (<< Update: Another answer provides Webkit info.)
Standards Sources
Standards also act as a good measuring rod for expected behaviour if you face a bug while developing.
This slide show is about HTML 5 standard technologies and must be viewed in HTML 5 (e..g Google Chrome works well).
HTML 5 (W3C):
http://dev.w3.org/html5/spec/Overview.html
CSS 3 (W3C):
http://www.w3.org/TR/css3-roadmap/
HTML 5 Web Sockets (W3C): http://dev.w3.org/html5/websockets/
WebGL: http://www.khronos.org/webgl/
Web SQL Database: http://dev.w3.org/html5/webdatabase/
Application Cache API for offline apps (W3C): http://dev.w3.org/html5/spec/Overview.html#offline
Web Workers for background processes (W3C): http://dev.w3.org/html5/workers/
Web Sockets for 2-way communication with host (W3C): http://dev.w3.org/html5/websockets/
Drag and Drop (W3C): http://dev.w3.org/html5/spec/Overview.html#dnd
Geolocation to pinpoint yourself (W3C): http://dev.w3.org/geo/api/spec-source.html
Web Storage to store more data in the browser (W3C): http://dev.w3.org/html5/webstorage/
Canvas Tag for on-the-fly visuals: http://dev.w3.org/html5/spec/Overview.html#the-canvas-element
and many more .... There are many parts.
A Strategy to find more info ...
See this great slide show (using an HTML 5 capable browser - it'll get you in the mood) for the overview...
Then look up the spec you want at the W3C.org website or Google its contents using a search terms to target the site like "site:www.w3.org "html 5" YourTerm" for example the Google Canvas tag.
As far as HTML5 goes, I frequently check out:
https://html5doctor.com
Dive Into HTML5
And yes, the HTML5 spec, which I recently visited to find out more about supported input types and form field attributes in HTML5:
https://w3c.github.io/html/
https://w3c.github.io/html/sec-forms.html#sec-forms
As for CSS3, I often find myself at:
http://www.css3.info/
Safari reference material, which may or may not be HTML5/CSS3 specific:
https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariCSSRef/Introduction.html
https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariHTMLRef/Introduction.html
Believe it or not, wikipedia: comparison of layout engines CSS3 and HTML5 is actually pretty good at very detailed comparisons. Modernizr is very coarse grained.
You can also take a look at HTML5 Laboratory which is my own HTML5 experiment site.
As mentioned above, HTML5 Doctor and Dive into HTML5 are two great resources.
we've trying to develop a mobile web app that will provide offline capabilities, not just reading but also creating content.
Gears supports three important aspects:
- local server so we can have cached static content such as html, css, js, etc
- local database so that we can have data stored locally for offline access as well as store new content inside of it while offline
- workerpool, used for a background process that syncs data back to the server
By the looks of the gears page and some other articles, gears is being abandoned in favour of html 5 which is understandable.
However, at this stage there are two problems:
there's still a long way to have HTML 5 supported by major desktop browsers,let alone mobile ones
HTML 5 does not support workers, there is a draft http://dev.w3.org/html5/workers/ but I assume real browser support is still far away.
Do what does one do today? (e.g. within the next year)
Cheers
Rok
I think that you have slightly misinterpreted Google's position on Gears. According to an article in the LA Times:
The Google spokesman wrote to clarify in a follow-up e-mail, "We're continuing to support Gears so that nothing breaks for sites that use it. But we expect developers to use HTML5 for these features moving forward as it's a standards-based approach that will be available across all browsers."
It sounds to me like it is completely safe to continue using Gears, until and after HTML 5 is ubiquitous.
HTML5 support is a little better then you think.
Android has various support for HTML5 standards, with the inclusion of Google Gears into most versions and Android 2.0+ having native support for HTML5 (at least as far as audio/video, canvas, offline storage, and geolocation go). IPhone also supports offline storage along with audio/video tags. WebOS seems to have offline database support, but I don't know much beyond that.
http://www.whatwg.org/specs/web-workers/current-work/ is the web worker draft implemented in Firefox 3.5 and Safari 4, so they should wind up in IPhone's version of Safari eventually.
So if you can live without worker threads and don't mind limiting yourself to Android, WebOS, and IPhone, you can use a hybrid approach of HTML5 with a fallback to Gears.
I don't think supporting other smart-phones is going to be possible in a truly portable way, although Firefox for Mobile (which is nearing release on the Nokia N900) will support all the HTML5 as Firefox 3.6.
Appcache, Web storage & Web workers works on Firefox and newer Android devices.
Use this handy test http://dev.w3.org/2008/mobile-test/v2/ to profile browsers.
HTML 5 does not support workers, there is a draft http://dev.w3.org/html5/workers/ but I assume
real browser support is still far away.
I coded a working example of web workers using the WebKit engine included in Qt 4.6.2. Looking at the code history, support was incorporated sometime in 2008.
I've been surprised by the level of HTML5 already in (desktop) browsers (excepting IE of course). Mobile lags a few years. I've found this site useful: http://caniuse.com/