I can't find this feature at caniuse.com and from research it seems no progress has been made since 2012. All articles pretty much are from 2012 as well.
I think this feature will help bring out the power in browsers.
First off, as indicated in this article from Adobe, "CSS Shaders" as a whole are now known as "CSS Filter Effects."
The W3C draft spec, which at the time of this writing was last modified in November of 2013, defines the new features. Many of the new features are basically just existing SVG filter effects that will now be able to be used from CSS for arbitrary elements.
According to CanIUse, some of the filter effects are available for newer versions of modern browsers. However, I suspect that this does not include the actual shader features, which are known as CSS Custom Filters / CSS Custom Shaders.
This article from March 2013 goes into an introduction to custom CSS filters/shaders, and links to more resources. It also mentions that custom filters have to be enabled directly from about:flags in Chrome.
So, basically, custom filters are still very much experimental, and very very few, if any, browsers will support it out of the box.
Related
I hope this question is on-topic for StackOverflow. I have seen many comments here that a lot of web developers scrollbar customizations are non-standard and not yet approved by the powers that be (W3C.org). My philosophy is to design to the standards Issued for Use by the Industry Organization that guides web standards and specifications because a properly, dependable, working website is what my users want.
Approved scrollbar customization standards that the W3C.org has approved. Where can I get that standard?
If I am off subject again, could you possibly get me some answers first, then pass me to the Red Queen for off with the head?
Thanks Community.
The "standard" Scrollbars CSS Module - Level 1 is in its early stages of adoption and that would be the only one matching your requirements.
Until it's implemented, you're limited to non-standard CSS scrollbar styling support.
Another option (the only production ready one, really) is to use a plugin which basically replaces the scrollbar mechanism with custom HTML elements.
Most of them have trouble with at least one mobile device type (either on IoS or on Android) and the sane solution is to detect it and simply disable the plugin for that case.
Note 1: while W3C support is a very wise thing to look for when choosing how to build your page, it doesn't mean much without browser support. In theory, if Chrome refuses to implement something today, considering their market share is above 60%, they simply won't and nobody can do anything about it. But your clients will require their page to work in Chrome.
However, much of Chrome's popularity comes from strictly sticking to web standards so far, so it would be safe to assume they will continue to abide by them.
Note 2: I recommend this article. It's well written, quite informative and up to date on the current state of scrollbar customizations.
As a lone developer with limited resources, I made the decision some time ago not to continue support for IE8 and IE9.
To manage the situation I use IE's conditional comments - I now also use Modernizr to detect support for individual features, which the above browers do not support anyway.
Javascript is also a given for me - if you don't have it, then sorry but we can't do business.
I was therefore considering removing conditional comments and letting Modernizr/javascript do the job.
Conditional comments do break a lot of things that scrape the site - for instance CopyScape will not work - there's also testing software I use that breaks and/or gives out false signals.
Does anyone have any cast iron reasons NOT TO remove them or TO remove them?
Given that support for conditional comments was removed from IE10, I would recommend against using them at this point in time. It's 2017; time to move on. (That's my take, anyway; YMMV.)
I would consider providing a bare bones version of the site designed for any browser other than your preferred one (which, conveniently, also helps you support experiences you didn't plan for).
I want to make a desktop app with electronjs. For this I want to use custom elements. (not Polymer)
But here on MDN is a note that the spec will be rewritten:
Spec for Custom Elements will be rewritten in early 2016. All current
implementation are experimental and the upcoming standard will not be
compatible with these. Web sites using Custom Elements are likely to
be broken in the near future.
Are there any updates in this? What will change? Are there new specs available? Where can I find more information on this?
The Custom Elements W3C Editor's Draft specification is available on GitHub. It was last updated on June 1, 2016 (as of this writing) though you can expect it to continue to be updated. To answer your first question, yes, there are updates and you can see them directly at the spec. Which also answers your third and fourth questions.
Because it is a draft, you cannot expect any browser to support it yet (though some claim to). Polyfills are your best bet if you want to use it now, knowing that since you are using bleeding edge technology you will need to stay on top of browser implementations and constantly review what works.
Because it lives on GitHub, you can file bugs against the spec if you want a say in how it progresses (it is not tech support, however). Looking at open issues essentially answers your second question.
As for browser support, Can I Use is tracking where it stands today including who does and doesn't have it on their roadmap. Note that browsers who claim to support it are supporting an incomplete spec that will change. That same page also has a link to lots of handy resources to help get you up to speed.
Due to the low level of support for HTML5 in older browsers should one (or could one) use any part of HTML5 at this point in time for a new website that will have varying users with the full spectrum of browsers (and versions) to access the site?
EDIT: To fill in some more info here. The website in question, for simplistic comparison, would resemble fb. I am not talking a social website just one that will reach that type of vast audience (anyone can join) and will be an interactive portal (not just a site full static content being displayed).
First, HTML5 is a standard that includes the previous standards. Therefore, you are already doing HTML5 without knowing it.
Second, HTML5 could be compared to CSS in terms of feature grouping (CSS = CSS1 + CSS2 + CSS3 and so on). In other words, it is a collection of individual features and not one big thing.
Third, you will have to implement new HTML5 features one day or another. Why wait? Ooh right some people do not care about "modern browsers". You have a responsibility as a Web developer/designer to inform people about the consequences of obsolete browsers.
Last but not least, there is tons of information already... Like this website: http://diveintohtml5.ep.io/.
Some complementary info can be found from this answer and this other answer I wrote for other questions about HTML5.
Have fun! :)
Thank god MS is finally campaigning to get gid of IE6 but it surely will be in China for years to come due to pirated windows software which I had altogether too much experience with; despite this push for higher standards tons still use IE7, 8, and some even 9 is not perfect. Chrome IMOP is exceptional followed by Safari and FF for HTML5 support but even these browsers are not perfect.
I think it is ok to use features css3 and HTML5 such as canvas but in an unobtrusive manner like javascript enhances UI HTML5/CSS3/jQuery should enhance not be the content.
With javascript we can check for browsers and use appropriate methods this concept should also be applied to HTML5. So if you do implement anything I think it's important to understand how to detect and this is probably the best resource to start with.
http://diveintohtml5.ep.io/detect.html
You can use all of the new HTML Field types in forms safely, any HTML 5 inputs in browsers which don't support html 5 will simply fall-back to a standard type="text" inputs.
Mobiles currently seem to benefit from HTML 5 forms most at the moment as they recognise the input type, lets say "email" and then provide an email specific keyboard layout to the user.
Its also simple to provide JavaScript fall backs for some html 5 elements with http://www.modernizr.com/
I'm confused by the discussion and advancement both of a new version of HTML and a new version of XHTML. Are they competitors? If so, what is likeliest to be the adopted future of the web? If not, what is the differing non-competing purpose for each?
Are we due to have a BluRay/HDVD battle here? Is there ultimately any clear decision? I fear a future where browsers pick and choose among the easiest and/or flashiest features of each to implement, leaving web developers trying to sort out the lowest common denominator for any new web app.
HTML 5 is meant for web applications whereas XHTML2 is meant for documents. From the HTML 5 working draft:
XHTML2 defines a new HTML vocabulary with better features for hyperlinks, multimedia content, annotating document edits, rich metadata, declarative interactive forms, and describing the semantics of human literary works such as poems and scientific papers.
However, it lacks elements to express the semantics of many of the non-document types of content often seen on the Web. For instance, forum sites, auction sites, search engines, online shops, and the like, do not fit the document metaphor well, and are not covered by XHTML2.
[HTML5] aims to extend HTML so that it is also suitable in these contexts.
XHTML2 and [HTML5] use different namespaces and therefore can both be implemented in the same XML processor.
XHTML2 and HTML5 are competing standards, they both purport to be the next iteration of HTML.
It is pretty clear that HTML5 is going to win, since it has support by the browser vendors.
XHTML2 is effectively dead. Since w3c(HTMLWG) accepted WHATWG's proposal the work has stopped on XHTML2 (even before that, since the last working draft for xhtml2 is from 2006).
In my opinion HTML5 will be the next dominant format. XHTML is just too unforgiving to be used in a web environment (you can't have the page fail on every small error...).
HTML5 is shaping up to be quite the treat for web developers - a formal spec for the CANVAS element, native drag-and-drop API, an offline storage API, server notifications API (push model), a formal content editing API and much more. If they can deliver even half of what they are proposing to, it will be a major advancement for web applications.
From what I was able to find in a quick google search, I would suggest that these are indeed competing standards. Both are attempting to advance web technology but are following different paths to do so.
For a pretty thorough treatment of the matter you might look at these two links:
http://xhtml.com/en/future/x-html-5-versus-xhtml-2/
http://www.cmswire.com/cms/industry-news/setting-the-standards-html-5-vs-xhtml-2-002032.php
Ultimately it's whatever is supported by browser makers. HTML 5 is feature rich, but the final draft may be years off. There are inherent difficulties in implementing things like audio and video support in 4(+) major rendering engines, and having them all behave the same way. Even validation would be a chore. Most browsers besides IE support the canvas element and SVG, but they still only represent about 25% of the market. With IE still commanding 75-80% of the market share, users who don't use or are oblivious to alternatives will be unable to use more advanced features, giving designers a tough decision.
IE8 is only finally implementing support which other browsers have had for users, meaning that the IE user base will always lag in compatibility. While HTML 5 is a nice idea, I think proprietary solutions such as Flash/AIR and Google Gears will continue to provide standardized support for the rich features HTML 5 provides. The biggest problem really is standardization - you have to design a website with the greatest percentage of users in mind as possible. There is hope, however. A Mozilla developer made a canvas plugin for IE - we could potentially see an open-source IE add-on that brings it up to a certain standard, that users could install much like Flash.
To Microsoft's credit they are being very open with IE8 and Windows 7 development (see their project blogs), so there is the possibility that more proactive IE development will accelerate adoption of HTML 5.
The W3C allowed the xhtml2 working group's charter to expire in 2009. Their resources were rolled into the html5 working group. The html5 spec contains a section entitled The XHTML Syntax.