Skip to content
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

NOTICE: Version 8.x of LazyLoad soon to be deprecated #306

Closed
verlok opened this issue Feb 16, 2019 · 4 comments
Closed

NOTICE: Version 8.x of LazyLoad soon to be deprecated #306

verlok opened this issue Feb 16, 2019 · 4 comments

Comments

@verlok
Copy link
Owner

verlok commented Feb 16, 2019

I'm planning to dismiss the development of version 8.x and deprecate it in favor of maintaining only version 10.x which could work with the IntersectionObserver polyfill by w3c.

The reason of this is that:

The official w3c polyfill could be loaded conditionally on less recent versions of Safari and Internet Explorer, using Polyfill.io.

@Erulezz
Copy link

Erulezz commented Feb 17, 2019

+1

Dropping support and updates is a good idea when Safari 12.1 has been released (coming somewhere in March probably with iOS 12.2 and macOS 10.14.4). Keeping the docs online for v8 (as it is now, but with a deprecation warning) until the majority of users are on Safari 12.1 is also a good idea. It always take a while before the majority of users are upgraded.

@shoesforindustry
Copy link

+1 With Erulezz comments. All in favour of this move, but it has to be after Safari 12.1 has been out for some time, it just makes sense?

@verlok
Copy link
Owner Author

verlok commented Feb 18, 2019

Hi all,
thanks for taking the time to comment.

In my opinion, the deprecation of version 8.x could start the exact day Safari will start supporting IntersectionObserver, because:

  • The suggested solution would be to use the IntersectionObserver polyfill, which will grant compatibility with older Safari versions still around.
  • Version 8.x would continue to be available forever, only it won’t be maintained anymore, so it would still be available for those who don’t want to upgrade their code

@verlok
Copy link
Owner Author

verlok commented Feb 19, 2019

It's done already. The README file no longer mentions conditional loading and version differences.

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

No branches or pull requests

3 participants