Which Browsers Support Webkit CSS

Which browsers support WebKit CSS?

Wikipedia has a summary of what browsers use WebKit as their HTML rendering engine. The WebKit Project itself has even an more complete list.

Which browsers support -webkit-text-fill-color?

On MDN you can see the browser compatibility : https://developer.mozilla.org/fr/docs/Web/CSS/-webkit-text-fill-color

As you can see, -webkit prefix only applies to webkit-based browsers (Chrome, Opera, Safari).

Other prefixes can target other browsers, like -o, -moz, -ms.

Be also aware that it is not a standard property, according to the same page.

It may be why you can't see yet it on caniuse.

What is WebKit and how is it related to CSS?

Update: So apparently, WebKit is a HTML/CSS web browser rendering engine for Safari/Chrome. Are there such engines for IE/Opera/Firefox and what are the differences, pros and cons of using one over the other? Can I use WebKit features in Firefox for example?

Every browser is backed by a rendering engine to draw the HTML/CSS web page.

~~IE → Trident~~ (discontinued)
Edge → ~~EdgeHTML (clean-up fork of Trident)~~ (Edge switched to Blink in 2019)
Firefox → Gecko
~~Opera → Presto~~ (no longer uses Presto since Feb 2013, consider Opera = Chrome, therefore Blink nowadays)
Safari → WebKit
Chrome → Blink (a fork of Webkit).

See Comparison of web browser engines for a list of comparisons in different areas.

The ultimate question... is WebKit supported by IE?

Not natively.

Difference between -webkit , -khtml ,-moz ,-o property in css?

There are no immediate differences, it's a vendor prefix in order to tell the different browsers how to interpret, in this case, the property box-shadow.
This is done since the different browsers could possibly implement it differently.

The vendor prefixes also allows you to use experimental features or not finalised features.

Why Google Chrome browsers use -webkit-* prefix, while Chrome runs on Blink (except IOS, where they run on webkit)

Google Chrome used to use Webkit until Chrome 28 when it was replaced with Blink, a fork of Webkit. Whilst using Webkit, Chrome had access to all -webkit- prefixes.

When the change to Blink was made, the development team decided not to add any new vendor prefixes to the Blink engine. Vendor prefixes are intended to let web developers try out new standards until such time as they are properly implemented, and the Chrome team felt that this could be better done by enabling/disabling an un-prefixed version of the feature from within the browser. The Chromium site states:

...instead of enabling a feature by default with a vendor prefix, we
will instead keep the (unprefixed) feature behind the “enable
experimental web platform features” flag in about:flags until
the feature is ready to be enabled by default.

For compatibility reasons the old -webkit- prefixes were retained in Blink (removing support would break sites that relied on Webkit prefixes). Due to the above reason they were not replaced with Blink specific counterparts, and since Chrome 28 no new prefixes have been (or will be) added.

Browser compatibility for -webkit-scrollbar (CSS)

You can for IE and Webkit browsers but Firefox would require a JS solution - and if you bother to do it in JS, it doesn't really need you to do it in CSS as well.

An example of a JS scrollbar jQuery plugin.

Edit: Mobile browser - you apparently can style these but I haven't noticed them styled at all, nor did I even know my phone had scrollbars until I just checked. This plugin seems to be able to style them.

-webkit support in Internet Explorer

The Internet Explorer 10 supports some more CSS3 features. Did you to obmit the prefix? If this doesn't work there is nothing you can do. You may need to wait for the Internet Explorer 11.

However I would not recommend to concentrate your work for the IE. Better try to make run your app on Firefox, Safari, Opera and co.

Have also a look to the blog post Adapting your WebKit-optimized site for Internet Explorer 10 by Microsoft.

Which Browsers Support Webkit CSS