Who in production uses flexbox and what hacks do you use for certain properties?

Question

css

Hello!
Who uses flexbox to its fullest in production (yes, there is Can I Use, but he's not always perfect in his answers either)?
I’m interested in the opinion of such developers who are responsible for their project and support it in the future, and not those who take orders for a penny on freelance exchanges, do it quickly, and don’t care about the client, the main thing is to pass it, and so that at the beginning there are no jambs got out, and then "none of my business."
For many years I can not decide to use it, although the desire is simply unrealistic.
The problem was ie9 support, but the go-ahead has now been given to stop using that browser (read gov...oh).
But still there are concerns, because. even a year ago, I opened sites on flexbox in my browsers and saw jambs. What can I say a year ago - I even now open the well-known site https://css-tricks.com/ and in ie11 in which there are differences in the footer, in ie10 these differences are even greater (I mean differences with other browsers).
Yes, and I often meet questions, such as inconsistencies in decktop browsers, mobile, incorrect behavior of elements, etc.
You could, of course, start using them a long time ago, using fallbacks for unsupported browsers, but, honestly, I don’t see any point in this at all, because in fact you have to write almost twice as many, and polyfills and I haven't met a normal person to this day.
I would like to get an answer do you use in your projects (supported and aimed at a wide audience)? And what measures do you take if the display does not match? Maybe there are some useful resources where it is already described which properties behave incorrectly in certain browsers and how to deal with it?
Thank you very much!

Answer 1

Maybe there are some useful resources where it is already described which properties behave incorrectly in certain browsers and how to deal with it?

Yes, there is - flexbugs .

Answer 2

1) that the first thing I remembered was not to apply flex to the button, somewhere I got a bug when I aligned the text to the center. It's better to do it with padding or line hat
2) flex direction column reverse, justify content, it doesn't work quite right in IE when there is also an absolute tag in the wrapper. That block is better to take out. Here is the test, it remains for codepen. https://codepen.io/arkan4ik/pen/wrjejy
===
I hope it helped, otherwise it's necessary to use auto-prefixes. Another bug my friend told me that you need to write the correct order if you set certain properties, but I didn’t understand it, because I didn’t tell it to the end, and I didn’t meet such a bug

Answer 3

htmlacademy have already switched completely to flexbox even on their basic intensive html and css. A year ago, they also taught float and inline-block. The question is not whether to move or not. You have to use the right techniques in the right places. I have been using flex for about 2 years in all my work (both freelance and full-time). Yes, there are problems and they are very, very funny in places, and there are also solutions to these problems. For example, there is the following problem - on iOS 11 in safari, the site looks great, but not on iOS 10. And think what's the matter. But again, such problems are detected only by tests and are solved without much difficulty. IE 10-11 and Edge are the same, just tests and fixes everything that's wrong there. Again, it is unlikely that you need to make pixel perfect projects for these browsers, and therefore I do not see the problem of using flex.

Answer 4

I use it for half a year or a year on the sale, without hacks, but with prefixes. So far, there were no bugs.