In the red corner: Adobe, which has poured tons of time, money and hardcore dev hours into developing CSS Regions, a specification that enables the creation of rich, magazine-like layouts with content that flows through multiple containers.
In the blue corner: Google, which has just dropped the bombshell that it will abandon support for CSS Regions in favour of prioritising performance of Chrome, particularly for mobile devices.
It’s an announcement that’s divided the Web community, with many decrying the decision and others claiming they never really believed in CSS Regions in the first place. Opera’s Håkon Wium Lie recently presciently penned an article for A List Apart, going so far as to call CSS Regions “harmful” and claiming that:
"For those who believe in meaningful HTML tags, responsive web design, and compact CSS code, the introduction of CSS Regions is not good news.”
As a counterpoint, front-end developer Sara Soueidan fought back with an article that clearly struck a chord, examining the various problems and solutions with CSS Regions. Sara admitted that, while the technology is not yet perfect, CSS Regions can be “a useful and powerful tool in our responsive toolset.”
Either way, it looks like the die have been cast, at least as far as Google is concerned, and one thing’s for sure, Adobe isn't going to be happy about it.
What’s the future for CSS Regions? Is this a setback for web design? Or was Google’s a brave decision that will pave the way for better mobile web development? Only time will tell. We’d love to hear what you have to say about it. Leave us a comment below or tweet me @FOWD.
Follow @FOWD on Twitter for regular news and updates.