I love CSS Grid, but still can't use it because of support for IE11. There's still just too many windows 7 users, hopefully not for too much longer. What is webflow doing about that? Do you provide some measure of automated fallback to flex box?
Show HN: CSS Grid Playground in Webflow
31–34 of 34 posts
Re: Show HN: CSS Grid Playground in Webflow
#32Hello HN! 6 years ago we launched our very first playground on HN ( https://news.ycombinator.com/item?id=5407499 ). It barely worked, but a few months later we go into YC largely due to the awesome feedback we received from it. We thought we'd take a page out of history and show you guys how far we've come, with a version of the original playground, but fully integrated with CSS Grid. The Webflow designer was built m…
Re: Show HN: CSS Grid Playground in Webflow
#33I love CSS Grid, but still can't use it because of support for IE11. There's still just too many windows 7 users, hopefully not for too much longer. What is webflow doing about that? Do you provide some measure of automated fallback to flex box?
Right now we have only implemented a _subset_ of the spec; we'll be doing a more thorough audit of IE11 support as we add support for more sophisticated grid features, as those are more likely going to need some kind of built-in fallback.
In the meantime I would encourage folks that need custom fallback behavior to harness site-wide custom code; Webflow outputs pretty straightforward HTML and CSS so it should be easy to manually create fallback styles.
Re: Show HN: CSS Grid Playground in Webflow
#34I stumbled on webflow last week while looking for design tools and boilerplates. I was put off from going farther down the funnel by the mandatory account creation to try the demo. It's nice to see a there's now an ungated part of the product. I like the idea of more visual design tools, but I'm not sure the browser is the place for it. Just having the demo open destroys my laptop, and it's not exactly a weak machine…
I'm certain that the browser is the _perfect_ environment for a web design tool actually.
The performance issues you're experiencing are no fault of the browser per se; our codebase has grown very quickly in the last few years and we're just beginning to implement RUM to maintain a baseline of performance across the product. Live & learn
That said, we feel your pain! We've formed a feature team to take care of infrastructure-wide performance issues and we're working to maintain a higher standard for performance going forward.