Modernizr/Modernizr — Issue #416: Address Flexbox Class Name Conflict
Author: hguiney
Created: 2011-11-24 23:16:10+00:00
State: open

As you may be aware, the syntax of flexbox [changed](http://www.xanthir.com/blog/b4Dm0), and now the feature called "flexbox" that browsers have implemented, and that Modernizr is detecting, is different from the "flexbox" that will become what people use that name to refer to, once support exists. Leaving the class name the same though would obviously create inconsistent results.

You could either rename the current version—to "flexbox-1", "flexbox-beta", "flexbox-old", etc.—or call the next one "flexbox-2", "flexible-box", etc. Either way has the potential to break sites though: the former would for anyone relying on the existing implementation; and the latter would for anyone who is not aware of the spec change and assumes the class is "flexbox".

A third option would be to phase out the older one; perhaps keeping "flexbox" and adding "flexbox-1", notifying users on the homepage that as of [some date when enough support exists], "flexbox" will then refer to the newer standard, while "flexbox-1" will refer to the older standard, and to update their code.

I don't have a strong opinion any way or the other, but I feel it should be addressed in some way, if plans do not already exist.