Is -moz-box-shadow property still supported in firefox? - css

Im not able to use the hack -moz-box-shadow.Im using windows 64 bit laptop.Is it got deprecated or not supported anymore.
Thanks,
Balaji

The -moz- prefix is no longer required as box-shadow itself is now widely supported and has been for a while.
The last time the -moz- prefix was required was back in version 3.6. It was finally removed from use in version 13. The current latest version of FireFox is 40.
The last time the -webkit- was needed was back in version 9. The current latest version of Chrome is 44.
You can view the browser support here: CanIUse

-moz-box-shadow is for support Firefox 3.5 or less. We are in Firefox 40. Use box-shadow standard.
https://developer.mozilla.org/es/docs/Web/CSS/box-shadow
EDIT:
I don't say that's removed. I said that is for support old browsers.

Yes! I think it was removed :
https://developer.mozilla.org/en-US/docs/Web/CSS/box-shadow

Related

Why backdrop filter in Firefox don't work?

I use backdrop-filter: blur(30px); but firefox unsupported this property;
-moz-backdrop-filter: blur(60px); also doesn't work
Its not supported by default https://caniuse.com/css-backdrop-filter
However you can activate it manually.
Navigate to about:config and set it to true
As described on https://developer.mozilla.org/en-US/docs/Web/CSS/backdrop-filter, both layout.css.backdrop-filter.enabled and gfx.webrender.all have to be set to true.
Important: the browser must be restarted for it to work
I just wanted to point out that, as of yesterday, the newest Firefox Nightly Release does support backdrop-filter after enabling gfx.webrender.all and layout.css.backdrop-filter.enabled in about:config.
It will also be officially implemented in Version 102 (which will be released on 28.06.2022) as far as I could grasp that.
Firefox officially support it since version 103. In my case I was using Firefox-esr and at the moment I write this latest ESR version is 102.7.0esr. I had to switch to non-esr version (109.0 right now) to make it work.

Why does Chrome require the -webkit- prefix for CSS cursors?

The cursor spec is pretty old. Am I missing something in terms of cursors that I should be accounting for in my CSS other than just prefixing the cursor value?
Edit: I'm referring specifically to the "grab" property and others like it, which require "-webkit-grab". Sorry for the confusion.
The grab value is new to css-ui-3. This was during a time when anything that was new and experimental came in the form of vendor prefixes, including values. I'm not sure why Chrome hasn't still unprefixed it yet considering Firefox 27, released two and a half years ago, now supports this value unprefixed. Microsoft Edge also supports it unprefixed, though Internet Explorer does not.
It doesn't, you can use cursor just fine in Chrome.
Fully supported in all browsers - http://www.w3schools.com/cssref/pr_class_cursor.asp

Does the -o-animation vendor prefix exist?

I'm trying to find out if I need to include the -o-animation vendor prefix in my CSS, but I can't seem to find any resources which indicates it exists, and if it does, what versions of Opera it applies to.
Can anyone offer some suggestions?
The -o-animation vendor prefix is no longer required for Opera, unless you need to support old Opera v12.** versions.
Instead, use the -webkit-animation vendor prefix to support newer Opera.
According to Opera 12.10 release notes, you didn't need the -o- vendor prefix from that version on. Adding -o- was therefore just needed to support Opera 12.0x versions.

Sencha Touch CSS3 -webkit browser prefixes etc

I realise that Sencha Touch 2 states that they only support webkit browsers but was looking at just enabling it on a friend's Windows Phone 7.5 to see what it looked like.
I realise that alot of the CSS etc uses -webkit browser prefix like:
-webkit-border-radius:
instead of
border-radius
I understand that if I remove the -webkit- value that older versions of webkit will stop working but Chrome is set to auto update and I'm wondering if there's a list anywhere on the internet that shows the version of webkit for each version of Android/RIM etc.
Something like:
Android 2.0.3 - Webkit 504
Android 2.3.1 - Webkit 634
I guess a solution would be to just to add the one without the browser prefix as well

What is the current status on css 3 and using prefix for rounded corners?

I used to do -webkit-border-radius and -moz-border-radius but now that there is ie9 I was wondering which prefix I should use. So after some googling I found this:
When we added border-radius, we decided not to use –ms as the specification was a Candidate Recommendation at the time. The full module is again a Working Draft to resolve box-shadow issues but border-radius is still at Candidate Recommendation stability. Other browsers either already support the unprefixed version or will in an upcoming release.
source
So I guess I should use:
-moz-border-radius
-webkit-border-radius
border-radius
It also seems that chrome supports a non-prefixed border-radius but Firefox doesn't so I was wondering if I should only use:
-moz-border-radius
border-radius
Your best bet is using the example below because altough newer browers dont require the prefix, older browsers that did require the prefix wont work without it
-moz-border-radius
-webkit-border-radius
border-radius

Resources