Flickity VS mailcheck

There is also a hacked fade version as discussed here: https://github.com/metafizzy/flickity/issues/26

Search for "class OptionsSelection extends HTMLElement". That should get you to the correct area of the JS file. Retina uses Flickity for the main image carousel and thumbnail carousels so should get familiar with that. https://flickity.metafizzy.co/

As always with development, it depends. Some carousels need a lot of features to meet requirements. If you need something really simple, use a css one. If you need a complex one e.g flickity then use that as making your own version of that would be unfeasable.

I'm working on a SvelteKit project, and I'm trying to import Flickity through CDN. I need to include the following element: ``, into my project, but SvelteKit doesn't allow multiple instances of a script element inside a single component.

Ah I see, thanks for the insight! From what I can see, Flickity supports lazy loading and is vanilla JS https://github.com/metafizzy/flickity

I am trying to make some responsive carousel cards and I found Flickity (https://flickity.metafizzy.co/)

Not an "instead of" approach, but the best thing I'd implemented when running an ecom site was a typo detector that prompted people to fix their email if it looked wrong, like "[email protected]", "Did you mean [email protected]?".

At the time I used "mailcheck": https://github.com/mailcheck/mailcheck

There appears to be a more modern implementation here: https://github.com/ZooTools/email-spell-checker

It reduced the amount of badly entered emails more than any other approach I tried.

It misses the very common mistake of typing a comma instead of a dot.

Otherwise, yeah, most people would be better served by a library that detects domain typos like https://github.com/mailcheck/mailcheck than spending time on regexes.

The most helpful thing I've used in the real world is something that looks for common typographical errors, even if the email is technically valid.

Like, if the user types "[email protected]", it pops a dialogue asking "Did you mean "[email protected]". But lets them keep what they typed, or do a different fix if needed.

I found some JS called "mailcheck": https://github.com/mailcheck/mailcheck

There are updated clones that use react, vue, etc, instead of jquery.

With a working ecommerce site, this improved the percentage of correct emails more than anything else I tried, and I had tried many things. Because it's a bad situation when you've taken someone's money and have nothing other than a shipping address to contact them if something goes wrong (bad shipping address, out of stock situation, etc).

I somewhat lol'd when the demo allowed "[email protected]" just fine. Guess kickstarter isn't using mailcheck anymore. Looks like it's an open issue:

https://github.com/mailcheck/mailcheck/issues/179

I suppose it depends on what we mean by validate. Running an ecommerce site, I got a lot of mileage out of prompting the customer to fix emails that "looked wrong". We allowed them to proceed if they wanted. A really common one was "[email protected]" when "[email protected]" was wanted. We used a slightly modified version of https://github.com/mailcheck/mailcheck and found it to be really useful.

It does work well. I used a customized version of https://github.com/mailcheck/mailcheck on an ecomm website and the amount of bounces due to typos went way down.