-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[Compatibility] Figure out the form attribute for IE11 #66
Comments
One thing to note is that this I'm curious what are the ups and downs of putting the |
cc. @LucasLacerdaUX |
The main issue is that, if we wrap all the
So we decided to use this As the form blocks can be reordered freely, we can't even choose to have two |
What we could do, though, is dispatch a |
For the scope of this issue, I've assigned myself to take a look at it. I'm leaning towards using a polyfill to make it work for IE11, even though I really don't want to use a polyfill. I can't think of anything better. 🤔 If the polyfill works outright, it should be pretty low effort. |
Purpose
We are using the
form
attribute on<input>
elements in a few spots to facilitate sections everywhere - the cart and the product page so far, and I'm sure its use will be broadened over time as we continue to discover new use cases with Sections Everywhere.The issue is that it is not supported on IE11, which still needs basic functionality like adding to cart and checkout. caniuse gives the rundown.
I don't think this should stop us from using it, but it might mean we need a polyfill which we had, in principle, decided were evil and not to be used.
The text was updated successfully, but these errors were encountered: