Skip to content

Conversation

@annevk
Copy link
Member

@annevk annevk commented May 27, 2016

This changes the following things:

  • Makes algorithms other than multipart/form-data return code points
    rather than bytes, since most callers want code points. With this
    change we are no longer required to use US-ASCII and more importantly
    it removes a redundant encode/decode roundtrip.
  • No longer use multipart/form-data for “Mail as body” since that does
    not match implementations. They only support the other two encodings
    there. “Submit as entity body” is the only algorithm that supports
    multipart/form-data (which makes sense, since a MIME type is required
    to interpret it).

Fixes #663.

This changes the following things:

* Makes algorithms other than multipart/form-data return code points
rather than bytes, since most callers want code points. With this
change we are no longer required to use US-ASCII and more importantly
it removes a redundant encode/decode roundtrip.
* No longer use multipart/form-data for “Mail as body” since that does
not match implementations. They only support the other two encodings
there. “Submit as entity body” is the only algorithm that supports
multipart/form-data (which makes sense, since a MIME type is required
to interpret it).

Fixes #663.
to the <var>submitter</var> element's <span>node document</span>. If this fails, abort these
steps.</p></li>

<li><p>Let <var>action</var> be the <span>resulting URL string</span>.</p></li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this just an unused variable?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The combination of e2d80d9 and 69ea9df landing made it redundant, yes.

@zcorpan zcorpan merged commit ec42efb into master May 30, 2016
@zcorpan zcorpan deleted the form-submission-encoding branch May 30, 2016 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants