Aos: DO NOT USE AOS

[TheIllestt]

AOS is an incomplete project that will inevitably mess up your workflow and cause you all sorts of problems. Don't make the same mistake I did and install this product. Will take me less time to uninstall and find a complete solution than to fix the issues that exist in AOS.

AOS breaks frequently, items triggering too early, too late, or not at all.

There is some issue deep in the AOS library that most likely will never get fixed. Delete AOS from your projects and move onto the next scroll-trigger software.

[DiemenDesign]

I've had no such issues.
Also, if you know what's wrong with a repository, the nature of GitHub allows anyone to submit Pull Requests and fix those issues or submit improvements. There's no need to behave like a spoilt 5 yr old by opening these types of issues and bitching about your inability to use it. I'm sure there's plenty of others who use this Repo without issues.

[TheIllestt]

I've had no such issues.

Read through the 129 open issues and you can see some core commonalities.

This product is not production ready, and should not be presented as such.

[joshangehr]

I've been using AOS for years on dozens of projects with no issues. There are several threads outlining common issues and solutions for most problems. I'm not sure where this flippant aggression is coming from, but if you explain the issue you're having, many of us would be happy to help.

[DiemenDesign]

I don't know why pointing out that there's 129 open issues is going to do. Many projects, have a lot more open issues, with people outside of that group working to improve projects, hence, the nature of Open Source and GitHub allowing anyone to help.
@TheIllestt you are more likely to get a positive response when keeping the above in mind.

[Unknow-max]

Alalalalalala

[nandomoreirame]

very unnecessary issue dude

[thevipinmishra]

Well, don't be that harsh. I myself is having issues with AOS recently. AOS doesn't like overflow:hidden for sure.

[Unknow-max]

I agree a Little bit,
Often I see issues with Aos, animation that triggered few moments Later or earlier, ecc.

[enguerranws]

AOS comes with a lot of CSS rules, that's the point of a library. That's why it _can_ break things with your project CSS.

Depending on your project, AOS CSS rules can be:

• too specific
• not specific enough
• can cause conflict with one of your project CSS rules

Just like any third-part CSS (including all frameworks).

When you import AOS (or any library, actually), you have to be sure of its implementation in your project (and you have to be sure of how your project's CSS implementation aswell: surely, AOS won't handle well hacky CSS with negative margin, zoom, etc).

So, well, that's not an issue, and cannot be considered as it.

_"Damn, React has more than 450 issues opened, I stop using it!"_ 😂

[sebastian-marinescu]

I'm voting to close and lock-down this issue, as it isn't an issue at all.

[TheIllestt]

This post has served its point to caution developers who aren't looking for a "basket case" software. If I can save one person the frustration and wasted time, then this post was worth it. Seems a few people may have benefited from my cautionary tale.

As for the 129 issues -- the point is that you can see there are many issues that have no resolution, and there are some core similarities. The number doesn't matter, but unresolved and piling up issues in the framework do.

I've found another scroll-trigger solution. You can put your pitchforks and torches away now.

Good luck y'all, stay safe.

[enguerranws]

This post has served its point to caution developers who aren't looking for a "basket case" software. If I can save one person the frustration and wasted time, then this post was worth it. Seems a few people may have benefited from my cautionary tale.

You get the point: that's not an issue, that's what people tells you. It won't last 5 minutes on Stack Overflow before getting closed by a moderator. If your goal is to warn rookie web dev, just start a Medium post, this is not the purpose of an issue.

As for the 129 issues -- the point is that you can see there are many issues that have no resolution, and there are some core similarities.

React too, will you start the same issue on its repo?

The number doesn't matter, but unresolved and piling up issues in the framework do.

This is basically why the issue tab exists.

I've found another scroll-trigger solution.

You're more than welcome to share it.

One thing you never said, which might actually help someone: what version of AOS are you using?