@jsandlin85 We did officially retire IE9 and IE10 support earlier this year, a few months after Microsoft stopped shipping security updates to those browsers: IE9 and IE10 support for published websites will soon be deprecated on March 1st, 2016 - Webflow announcements - Forum | Webflow – for all intents and purposes, these browsers should be considered harmful. If you still have clients that still demand that their websites sites support these browsers, it might be time for a potentially uncomfortable conversation to explain to them why this is not a good idea
We recommend that you test your layouts on real IE11 browsers (if you have a significant percentage of users who visit with that browser) to catch potential issues early. Most of the time, however, you might see some non-critical degradation that still leaves your content readable - but perhaps not as beautiful as in the most recent versions of Chrome/Firefox/Safari/Edge.
Thanks for the reply; I completely agree and this is pretty much what I tell my clients walking into projects. It actually just slipped my mind this morning about Microsoft’s official support drop for those browsers. I must feel like I’m waiting to wake up from a dream lol
I don’t know if anyone remembers the Australian retailer Kogan that instituted a 6.8% IE7 tax to users making purchases on their site in IE7, but when I saw that I thought it was hilarious and brilliant.
On a side note, I just wanted to say thanks to the entire Webflow team for what you are doing. My story falls under the “You are changing my life and career for the better” category that I know a lot of others are in as well. I feel like Webflow is fulfilling a promise to the web that so many others have attempted to for years. I don’t typically gush like this unless I am completely convinced of a service’s value and you guys are nailing it. Watching you grow in both features and community has been an inspiration. Seriously, thank you. As long as you continue this great work, you have a loyal evangelist in me
Congratulation to the webflow team, this is great, and you keep surprising us with new announcements! Still exploring everything one can do with this, it looks like an alternative to the grid system and the layout properties rather than something on top of that. Which sounds great to me because bootstrap grids are somehow counterintuitive and limited in what one can achieve. This is a major step forward because Webflow is now really going to be a tool that empowers designers - so they can focus on content and be creative without constantly thinking: “How am I going to achieve that in HTML/CSS? Is there a way?”
Maybe someone can explain to me if it could also be a solution to the problem of how to create responsive layouts that scale well on larger screens? I observed in the training videos that sometimes you use flexbox layouts in combination with containers, sometimes you don’t, so that would be my first question.
For those who want to have a basic understandig of how flexbox works at the code level (which I always find helpful) Ryan Irelan has a nice video overview on his site. https://mijingo.com/lessons/guide-to-flexbox/
Looking at the generated CSS, I was a bit surprised to see it doesn’t include vendor prefixes, when according to caniuse around 5% of US users (and a larger number of global users) are still on browsers that require prefixes, mostly -webkit. Curious if @callmevlad or someone else on Webflow staff can comment on the reason for not including prefixed styles?
Just wondering if I am the only one have this problem, some the of layout on my website is not where it should be in internet explorer this morning. Not sure if this has got anything to do with the new feature…
Are you using Internet Explorer or Microsoft Edge?
If you’re using explorer, it might be that, that browser is no longer supported by Microsoft therefore the Webflow team are no longer taking it into account when testing cross browser compatability. See this article:
I know it must be something ridiculously simple, but I don’t get it.
