New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flickity v2: drop IE8 and 9 support #178

Closed
desandro opened this Issue Jul 1, 2015 · 13 comments

Comments

7 participants
@desandro
Member

desandro commented Jul 1, 2015

Flickity will be dropping support for IE8 and IE9 in the next major version, v2. Expected release date in early 2016.

The time has come. Browser usage for IE8 is 2%, IE9 is 1.5%. Android 2 and 3 support will also be dropped. These are the last browsers with large feature gaps. By dropping support for them, we can remove a lot of code including helper libraries: eventie, classie and doc-ready.

Flickity v1 will still be made available to download and view documentation.

@CaptainCodeman

This comment has been minimized.

Show comment
Hide comment
@CaptainCodeman

CaptainCodeman Jul 8, 2015

Lots of mainstream javascript frameworks (e.g. Angular 2) are dropping support for these older versions of IE so I don't think that's a bad decision - the sooner the better !

CaptainCodeman commented Jul 8, 2015

Lots of mainstream javascript frameworks (e.g. Angular 2) are dropping support for these older versions of IE so I don't think that's a bad decision - the sooner the better !

@julienbenisty

This comment has been minimized.

Show comment
Hide comment
@julienbenisty

julienbenisty Jul 30, 2015

I second that.
Although developing sites for mainly the Asian market, I see more IE8-9 usage than North America or Europe due to the existing normalization of pirating windows XP; I think it's the only way to go. These 2 version are so old, so making people who are still using ancient browsers see with a warning that it's time to update or they will not enjoy modern is the only way to push them.

PS: BTW, i love the fact that i can initiate flickity via html using "data-flickity-options" is "killa" feature. That is what i call improvement. Making it easier to implement while still being powerful. Super job flickity team !

julienbenisty commented Jul 30, 2015

I second that.
Although developing sites for mainly the Asian market, I see more IE8-9 usage than North America or Europe due to the existing normalization of pirating windows XP; I think it's the only way to go. These 2 version are so old, so making people who are still using ancient browsers see with a warning that it's time to update or they will not enjoy modern is the only way to push them.

PS: BTW, i love the fact that i can initiate flickity via html using "data-flickity-options" is "killa" feature. That is what i call improvement. Making it easier to implement while still being powerful. Super job flickity team !

@nicholas-c

This comment has been minimized.

Show comment
Hide comment
@nicholas-c

nicholas-c Jul 30, 2015

Don't see why not!

As of 12th Jan 2016 MS Are dropping all support anyway;

http://blogs.msdn.com/b/ie/archive/2014/08/07/stay-up-to-date-with-internet-explorer.aspx

nicholas-c commented Jul 30, 2015

Don't see why not!

As of 12th Jan 2016 MS Are dropping all support anyway;

http://blogs.msdn.com/b/ie/archive/2014/08/07/stay-up-to-date-with-internet-explorer.aspx

@ivancuric

This comment has been minimized.

Show comment
Hide comment
@ivancuric

ivancuric Aug 12, 2015

Agreed. It's also easy to do a fallback to a simple tab-like slider for ie8.

ivancuric commented Aug 12, 2015

Agreed. It's also easy to do a fallback to a simple tab-like slider for ie8.

@desandro desandro added this to the v2 milestone May 25, 2016

desandro added a commit that referenced this issue Jun 16, 2016

@desandro

This comment has been minimized.

Show comment
Hide comment
@desandro

desandro Jul 11, 2016

Member

Flickity v2 is out now! Time to close up this one.

Flickity v1 will still be available if you need IE8+ or Android 2.3+ support.

Member

desandro commented Jul 11, 2016

Flickity v2 is out now! Time to close up this one.

Flickity v1 will still be available if you need IE8+ or Android 2.3+ support.

@desandro desandro closed this Jul 11, 2016

@Fortyfive

This comment has been minimized.

Show comment
Hide comment
@Fortyfive

Fortyfive Aug 3, 2016

Wondered there was a way to add IE9 support into Flickity v2 without having to roll back to Flickity v1 so that I can retain some of the v2 benefits? I have a client who is specifically looking for IE9 support. Thanks

Fortyfive commented Aug 3, 2016

Wondered there was a way to add IE9 support into Flickity v2 without having to roll back to Flickity v1 so that I can retain some of the v2 benefits? I have a client who is specifically looking for IE9 support. Thanks

@desandro

This comment has been minimized.

Show comment
Hide comment
@desandro

desandro Aug 5, 2016

Member

@Fortyfive sorry, nope. Flickity v2 and its many dependencies were all refactored to remove IE9 support.

Member

desandro commented Aug 5, 2016

@Fortyfive sorry, nope. Flickity v2 and its many dependencies were all refactored to remove IE9 support.

@Fortyfive

This comment has been minimized.

Show comment
Hide comment
@Fortyfive

Fortyfive Aug 5, 2016

No problem, thanks!

Fortyfive commented Aug 5, 2016

No problem, thanks!

@bentalgad

This comment has been minimized.

Show comment
Hide comment
@bentalgad

bentalgad Aug 12, 2018

Is there a simple solution to have a nice fallback or even to the v1 fallback for users that use ie 10 and less ?

bentalgad commented Aug 12, 2018

Is there a simple solution to have a nice fallback or even to the v1 fallback for users that use ie 10 and less ?

@desandro

This comment has been minimized.

Show comment
Hide comment
@desandro

desandro Aug 13, 2018

Member

Flickity v1 documentation is available to view & download at https://flickity.metafizzy.co/v1

Member

desandro commented Aug 13, 2018

Flickity v1 documentation is available to view & download at https://flickity.metafizzy.co/v1

@bentalgad

This comment has been minimized.

Show comment
Hide comment
@bentalgad

bentalgad Aug 13, 2018

Thanks, Yes i know that. my question is if i want to use v2, is there a way to detect that the v2 can't work on the user's browser and then load v1 ?

bentalgad commented Aug 13, 2018

Thanks, Yes i know that. my question is if i want to use v2, is there a way to detect that the v2 can't work on the user's browser and then load v1 ?

@desandro

This comment has been minimized.

Show comment
Hide comment
@desandro

desandro Aug 15, 2018

Member

You could do a quick & dirty check for a feature like classList

if ( 'classList' in document.documentElement ) {
  // Flickity v2 okay
} else {
  // Flickity v1 required
}

It's not foolproof, but it could work.

Member

desandro commented Aug 15, 2018

You could do a quick & dirty check for a feature like classList

if ( 'classList' in document.documentElement ) {
  // Flickity v2 okay
} else {
  // Flickity v1 required
}

It's not foolproof, but it could work.

@bentalgad

This comment has been minimized.

Show comment
Hide comment
@bentalgad

bentalgad Aug 15, 2018

Great! Thanks!

bentalgad commented Aug 15, 2018

Great! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment