Plug oldIE hacks wherever needed about atomizer HOT 7 CLOSED

@thierryk Do we need this for the 2.0.0 release?

from atomizer.

It depends how we want to treat IE7? Not having this in will break that browser.

from atomizer.

I believe this duplicates issue #38, so I'll close that one out in favor of this one, since this one covers Ov-h as well.

from atomizer.

@thierryk Is this issue limited in scope to those two classes, or do you mean to track all cases where oldIE support is needed? If the latter, I'm thinking we should target this for a 2.x release, and not hold up 2.0 waiting on it. Thoughts?

from atomizer.

Yes, those 2 are the only ones that come to mind.

from atomizer.

@thierryk Talking to @renatoi, we're thinking this belongs in a post-processing step, which would be outside of Atomizer. We could, however, create an "atomizer-examples" repo to demo various things (grids, grunt, workflows, etc) and post-processing for IE could be one of those examples we offer. Thoughts?

from atomizer.

@renatoi @src-code I like the idea but I don't think we can go this route. We are a library that pretends to help people build whatever they want, but right there we'd need to tell people things would fail in old IE unless they use a post-processor or add rules themselves (rules we would have to tell them about).
Can't we simply dump these extra declarations when needed?

from atomizer.