Intent to Implement: An event to enable arbitrary objects to provide form data
TAMURA, Kent
Contact emails
Explainer
https://docs.google.com/document/d/1JO8puctCSpW-ZYGU8lF-h4FWRIDQNDVexzHoOQ2iQmY/edit?usp=sharing
This intent is about "Proposal A" part of the explainer.
Summary
Add a new event so that arbitrary objects can provide form data.
Motivation
- Avoid to add many <input type=hidden> to a form to pass application status
- Make submittable custom elements
Risks
Interoperability and Compatibility
The risk is low. This is a small addition to the forms area. This was discussed in WebComponents F2F in March 2018, and we agreed on the approach of Proposal A though we haven't agreed on the API details yet.
Edge: Not opposed
Firefox: Public support
Safari: Public support
Web developers: Positive
See https://www.w3.org/2018/03/05-webplat-minutes.html#item09
Ergonomics
This feature might be used with Custom Elements frequently.
Activation
Polyfill would be helpful.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Link to entry on the feature dashboard
https://www.chromestatus.com/feature/5662230242656256
Requesting approval to ship?
Software Engineer, Google
Ojan Vafai
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqHBbSWZeWVcr6kOQHahsvee%2BCiqy1z9eYEaUNSWxDsz-A%40mail.gmail.com.
TAMURA, Kent
I thought the idea was to call the event beforesubmit.
As the meeting minutes say
"RESOLUTION: expose beforeSubmit and formdata is low hanging fruit."
-Olli
On 03/26/2018 09:27 PM, Ojan Vafai wrote:
> Very exciting! There's a lot of demand for this. The API surface all makes sense to me with one bikeshedding nit. Usually event names are verbs, so
> you might want a different name than "formdata." Maybe something like "serialize" or "serializeform"? Serialize is kind of a long word though. :(
>
> On Sun, Mar 25, 2018 at 7:58 PM TAMURA, Kent <tk...@chromium.org <mailto:tk...@chromium.org>> wrote:
>
> Contact emails
>
> tk...@chromium.org <mailto:tk...@chromium.org>
>
> --
> You received this message because you are subscribed to the Google Groups "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org
> <mailto:blink-dev+...@chromium.org>.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANMdWTtTzCXe3HY%2BEvSXpu0NyiHNBei5QttaiRgovDH6etx44Q%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANMdWTtTzCXe3HY%2BEvSXpu0NyiHNBei5QttaiRgovDH6etx44Q%40mail.gmail.com?utm_medium=email&utm_source=footer>.
Daniel Bratell
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqEsHRtTjooZoOQj8t9K1iAS8TOx%3DozL6zXZSiVVVDm0bw%40mail.gmail.com.
bat...@chromium.org
Contact emails
Explainer
https://docs.google.com/document/d/1JO8puctCSpW-ZYGU8lF-h4FWRIDQNDVexzHoOQ2iQmY/edit?usp=sharing
This intent is about "Proposal A" part of the explainer.
Summary
Add a new event so that arbitrary objects can provide form data.
Motivation
- Avoid to add many <input type=hidden> to a form to pass application status
- Make submittable custom elements
Risks
Interoperability and Compatibility
The risk is low. This is a small addition to the forms area. This was discussed in WebComponents F2F in March 2018, and we agreed on the approach of Proposal A though we haven't agreed on the API details yet.
TAMURA, Kent
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e5b2a3a7-b642-49df-b88d-b2829d85ffbb%40chromium.org.