More than one customizable product on a page causes issues.

[masonjeffreys]

Showing more than one customizable product at a time causes issues like:

• Scrolling over one variant changes all pictures
• Price calculations for one product affect all products

The javascript involved on the frontend of the gem should be reworked to be scoped to a single product, rather than the entire dom.

Happy to work on this. Perhaps some direction could be provided.
Thanks,
Jeff

[masonjeffreys]

@acreilly @dhonig If you're okay with this direction, I will take a first pass at it. I'll try hard to keep it backwards compatible. This would be for customizable options only at this point.

[acreilly]

That would be great. Ping me when you have a PR. Thanks!

[masonjeffreys]

@acreilly Took the first steps and issued a PR. This doesn't get us all the way to allowing multiple products on one page, but it starts us off.

I'd also like to move the front end calculator JS into the asset pipeline, but that's a bigger departure from current status quo. What do you think?

[masonjeffreys]

Sorry to overload the comments. But maybe it would be helpful to list the areas I'd like to help in, and see if they align with your vision:

• Frontend JS for calculators moved asset pipeline
• Validation of data types at the database level (According to some migrations, it looks like this may have been tried before?)
• More robust convention for naming customization groups, field ids, etc (i.e. jquery should find user inputs based on customization_type name and customizable_option name instead)

[masonjeffreys]

@acreilly @dhonig Any thoughts on my last PR or the bullet points in the comment above? Happy to do more work, just want to make sure it aligns with your vision. Thanks!