Browser Support about elemental HOT 31 CLOSED

IE 10 or 11+

from elemental.

11+

from elemental.

from elemental.

I once encountered a CSS bug that worked on Chrome and IE 11 but not Firefox, so...
xD

from elemental.

lolwut

from elemental.

I would say focus on chrome, firefox, and IE 10+

from elemental.

I say focus on Firefox, Chrome, and Opera 15+ (based on Chromium), then branch out to Safari, IE11 and MS Edge, then if we feel like it go to IE9 and 10.

from elemental.

For now, I'll make things work on Chrome, Firefox, Opera 15+, IE 10+, and Safari (newest version).

Mobile (responsiveness) shouldn't really be important for this project.

from elemental.

If we make things work for Chrome and IE, things should work in general, I think

from elemental.

Yeah.

from elemental.

yeah, if it works on chrome it usually works on firefox too.

from elemental.

Except when you're applying an ios-style shake effect to text inputs using jquery when users do something wrong.

... Personal experience.

from elemental.

Just ditch IE support altogether. Don't worry about IE, it's time to let it die.

from elemental.

Yes

from elemental.

We don't want the people learning html to deal with support themselves

from elemental.

Still think at least IE 11+. Then at least it'll make them learn to stop using IE :P
Even so, as long as we build it, it should work unless we use some browser-specific stuff (which we shouldn't anyways...)

from elemental.

The only browser worth supporting is netcat.

Or, if you're feeling slightly less masochistic, maybe support lynx.

But seriously, I agree with @hydrabolt

from elemental.

Unfortunately, netcat doesn't appear to support flexbox, so that won't be an option. :(

from elemental.

Did you read what I said?
As long we don't use any super esoteric browser features, we'll be good

from elemental.

@Firedrake969 That's not a given really; CSS3 animation isn't really "esoteric".

from elemental.

It's just vendor prefixes and things - should we include microsoft filters and stuff?

from elemental.

So IE 11 or up doesn't support CSS animations?

from elemental.

Just do a mix in that auto prefixes for you

from elemental.

Okay, cool!

How about browser support for the code exported by Elemental?

from elemental.

Don't care - it's theirs, let them do what they want

from elemental.

But in terms of auto-prefixing and things.

Also, should we let them know what browsers their sites will work in?

from elemental.

(ex. If they make a gradient, should it be auto-prefixed? If so, which browsers?)

from elemental.

All prefixes?

from elemental.

And what about in terms of telling them if they're using experimental/unsupported features?

from elemental.

We should probably just leave those out.

from elemental.

Ok, added a mixin for vendor prefixes

from elemental.