Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
This data from caniuse http://caniuse.com/#feat=calc suggests that practically all browsers now support calc in CSS. Are there any reasons to still avoid using calc for consumer websites? Have any major websites started using calc?
The official level is Candidate Recommendation for W3C and are descripted in draft document CSS Values and Units Module Level 3
Candidate Recomendation is not like Approved but is very near, so (i think) it 'a choice deeply comforted by the state of the documentation of W3C
IE seems to be the problem as usual but as far as I know, the calc element is fairly safe to use, depending on the units you are using (c.f. 'Known issues' with vw vh).
About Opera Mini, I thought it was now using the Chrome engine, even on iOS (iOS Safari engine is specified for iOS on caniuse). Would someone have more details about this?
EDIT:
A very interesting post about this on CSS-Tricks by Chris Coyier.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 months ago.
Improve this question
I am new to web development. I was wondering if I should really write different CSS code for different browsers. If I should, any tips for writing and testing my website in different browsers? Also, which browsers should I write different CSS code for? Thanks!
If you use autoprefixer then it will do all the different browser stuff for you: https://css-tricks.com/autoprefixer/
For testing in different browsers you could use something like BrowserStack
I suggest you write CSS code that targets the largest audience or market. Currently, the most used browser is Google Chrome. If you're more comfortable with another browser such as IE or Safari you can choose to write browser-specific CSS code.
Be sure to check the browser compatibility of the CSS properties you're using on the MDN Web Docs. Cheers!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question appears to be off-topic because it lacks sufficient information to diagnose the problem. Describe your problem in more detail or include a minimal example in the question itself.
Closed 8 years ago.
Improve this question
I am taking over an application that has buttons with this css:
background-image: -moz-linear-gradient(center top , #049CDB, #0064CD);
it looks beautiful in firefox but looks like a mess in IE, etc
what is the best way to take these clearly firefox specific css and determine the best way to make it look the same on all browsers (just need IE8+)
This tool might be a useful tool for you.
Since this CSS attribute is still a working draft of CSS and has some legacy it will require a lot of markup to be fully supported for your current situation. The -moz- prefix is one such isntance of providing support. All other browsers will required either the standard, -ms-, -webkit-, -webkit-type or -o- prefix as well.
You should look out for other spots in the application you've taken over for code that hasn't been fully tested on other browsers.
LINK
http://www.colorzilla.com/gradient-editor/
This is a matter of opinion but there are tools online that will help you generate css for gradients that works across browsers. http://www.colorzilla.com/gradient-editor/ is an example.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
How does the
not(#foo)
selector works to block older browsers and for which browsers does it work in the following tutorial?
http://css-tricks.com/snippets/css/custom-checkboxes-and-radio-buttons/
The CSS selector does not block browser, it's just not supported by the browser, i.e. when CSS file is being parsed by browser's built-in parser (which in turn supports certain CSS specification), unknown selectors and rules will be ignored and won't be added into styles of frames in render tree
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
How do you disable auto font-kerning for firefox and ie10? I've spent a while trying to search for a solution but all I get are out dated pages and experimental methods.
Previously, on Firefox, setting text-rendering: optimizeSpeed in CSS prevented kerning (and ligatures). According to Mozilla documentation, such a setting is now ignored “because the standard code for text rendering is already very fast and there is not a faster code path at this time”.
You can prevent kerning by using a font to which the browser does not apply kerning at all. The documentation is vague, but it seems that Firefox applies kerning to some “C fonts” by Microsoft and to DejaVu fonts.
Another, very clumsy, way is to use ZERO WIDTH NON-JOINER (U+200C) characters between letters, e.g. Wally to have “Wally” rendered without kerning the “Wa” pair.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
Is there a browser which supports CSS shaders?
At the time of this writing, CSS Custom Filters, formerly known as CSS Shaders, are not available in any browser. They were an experimental feature available in WebKit Nightly and Chrome (under a flag) for a while, but have since been removed.
No modern browser supports CSS Shaders or its later name, CSS Custom Filters.
Where to search for which browsers support various features:
Searching caniuse.com for CSS Custom Filters should provide an up-to-date answer to this question.
Can I Use is a great tool that provides compatibility tables for support of HTML5, CSS3, SVG and more in desktop and mobile browsers.
Support for CSS Shaders was discontinued in Webkit in January 2014.
https://lists.webkit.org/pipermail/webkit-dev/2014-January/026098.html
Chrome has some support for it and, I think, FF might have some now. I don't have my link for articles in Chrome handy but it's all very new.
If the browser supports every feature of HTML5 and CSS3. The only one that supports it by now is Chrome I guess.
Webkit appears to start having them: http://trac.webkit.org/changeset/103170
this link is supported for you to know the css supported browser.
https://dvcs.w3.org/hg/FXTF/raw-file/tip/custom/index.html
https://bugs.webkit.org/show_bug.cgi?id=73317
chrome and safari are supported for CSS shaders