personally have a hard time to understand what is to correctly fill out a bug, while I regularly do this on GitHub for example. That's it. Usually when I have this kind of issue I never go into the process of filing a bug for browsers. When you see a discussion about a CSS spec that is ongoing, sometimes I'm interested, but the discussion seems like you have to consider a lot of things to participate in these discussions. Even by giving your "I will be a user of this CSS feature in the future", even that I'm not sure... it doesn't seem to be very welcoming to non-spec-writer views. But maybe it's just me, the way I feel about it, not sure.
Participant 9
Background
I've been doing this for a while, I started web development back in the IE6 days, like around 2006 or -7. I know this focuses on browser compatibility, but... Back then browser compatibility was non-existent. I have some battle scars, I still have nightmares trying to get PNGs to work in IE6. The trauma.
Browser support
Basically all the evergreen ones and... I think it's Edge 15 and up, according to our research. Enterprise is a bit heavier on Internet Explorer usage but we just decided it wasn't worth it and we'll just ask them to use something more standards compliant.
Mobile browsers?
Basically Chrome, iOS Safari. We've been going back and forth on the iOS numbers, but we're targeting Safari from iOS 12 and up. It seems in general, at least from our research that iOS users are pretty good about staying on a fairly recent iOS version. And Android browsers... we haven't done a lot of testing on Android but we've tested in Chrome for Android. Since that gets updates pretty frequently we haven't really had any problems there either.
Viewport / Scrolling
The responsive layout you're using, do you remember when you implemented that, any browser compat issues that stand out?
Made with FlippingBook - professional solution for displaying marketing and sales documents online