15 Comments

  1. Morten Rand-Hendriksen

    I can’t quite express how exciting this is. Not only does it make the flex module something we can use in a much more extensive way without building in clunky fallbacks, but (like with RICG images) it shows that the WordPress community can be at the forefront of the battle to push modern web standards forward.

    The web community as a whole owes the 10up team a huge debt of gratitude for making this tool available to us all and paving the cowpaths for widespread use of the Flexible Box Layout Module.

    Report

  2. John Teague

    10up has done great things in the WordPress space, but I scratch my head at the idea of building anything that supports archaic and often insecure browsers like IE8 and 9. Gotta cut the chord at some point.

    Report

    • Josh Broton

      Tell that to the users of the sites I build who won’t upgrade. Choices are:
      1. Support IE8 and IE9
      2. Ruin their experience and impact my clients’ bottom line.

      Pretty easy choice there.

      Report

    • Morten Rand-Hendriksen

      This is not about prolonging support for IE8 and IE9, but about providing a great user experience for those still stuck using older browsers while still implementing new technologies. Unlike other advancements like media queries, responsive images, and so on, flexbox has not had a proper polyfill that allowed us to use it in production. Now we have it thanks to 10up, and as far as I’m concerned, Flexbox is now ready for production.

      Report

    • David Peters

      Health care is *notorious* for needing IE 8/9 support. Part of this has to do with government tech that actually supports IE8/9 exclusively and part of it has to do with specialty computers built for providers that run complex medical software that only runs on XP/Vista.

      Report

      • John Teague

        I understand the problems within specific industry/gov sectors. But the real downside are insecure systems open to, what we routinely witness, intrusions and data theft.

        I suspect that organizations that are allowed to continue bad practices, supported by those willing to write code that extends the legacy even further down the road, will gladly continue to open not just themselves but others to that theft.

        It’s a pay me now or pay me later issue in my mind.

        But again, that’s just my opinion. It doesn’t diminish my respect for 10up, whom I think are an awesome OSS group, and all around good folk.

        Report

      • Sunny R Gupta

        Agreed, I am currently developing for the “heath-care” sector and IE8/9 users on our platform are 9%. Compare that with the global 1% and you’d know why this polyfill is a boon to developers like me.

        It’s not about the client, but about making websites which look beautiful accessible in all their glory to these set of users too.

        Report

  3. Ryan Hellyer

    This is very cool.

    It also has absolutely nothing to do with WordPress, which I think is even cooler. It’s nice to see the WordPress community positively affecting things outside of the narrow confines of WordPress itself.

    Report

  4. Jason Witt

    I tested this with my own tests and the demos provided in the package on browserstack and it just does not work.

    IE11 is the only version that got any results, so still no love for flexbox. I was supper excited about this, too.

    Report

  5. Zach Russell

    This is a really awesome thing that 10Up did for the community. As it is said, this doesn’t only have to do with WordPress itself, but legacy compatibility as a while. I just had a site where I spent about 10 hours doing back-compatibility for IE8 becasue flexbox doesn’t work on it; creating fallbacks using Modernizr. If this was open sourced a few weeks ago I would have been so much happier. Great work 10Up!

    Report

Comments are closed.

%d bloggers like this: