Remove nonstandard 'endings' option for Blob/File constructor

Remove nonstandard 'endings' option for Blob/File constructor

new Blob([data], {endings: 'native'});
new File([data], 'filename', {endings: 'native'});

... which translates '\n' in the data to '\r\n' on Windows. This has
never been supported in other browsers, and use counters show only
0.0000000002% usage and no hits in HTTPArchive. Remove the option and
associated plumbing.

Intent to Remove: ****TBD****
Chrome Status: ****TBD****

BUG=605710
R=foolip@chromium.org

[foolip, 2016-07-20 17:45:18]

Should I review this?

[jsbell, 2016-07-20 17:49:09]

On 2016/07/20 17:45:18, foolip wrote:
> Should I review this?

No rush until we have the stats from stable.

And apparently I didn't build/run all the relevant unit tests locally. (Yay for
unit tests!) Let me at least get it green before taking a look.

[jsbell, 2016-07-20 18:18:36]

The CQ bit was checked by jsbell@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-07-20 18:19:15]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-20 20:10:31]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-20 20:10:32]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[jsbell, 2016-07-21 17:53:17]

The CQ bit was checked by jsbell@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-07-21 17:53:39]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-21 20:15:05]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-21 20:15:06]

Dry run: This issue passed the CQ dry run.

[jsbell, 2016-07-21 22:06:50]

foolip@ - if you're bored (*grin*) you can review, but I won't land before
getting stats from stable and sending out an intent/chromestatus.

[jsbell, 2016-07-21 22:07:22]

Description was changed from

==========
Remove nonstandard 'endings' option for Blob/File constructor

new Blob([data], {endings: 'native'});
new File([data], 'filename', {endings: 'native'});

... which translates '\n' in the data to '\r\n' on Windows. This has
never been supported in other browsers, and use counters show only
0.0000000002% usage and no hits in HTTPArchive. Remove the option and
associated plumbing.

BUG=605710
R=foolip@chromium.org
==========

to

==========
Remove nonstandard 'endings' option for Blob/File constructor

new Blob([data], {endings: 'native'});
new File([data], 'filename', {endings: 'native'});

... which translates '\n' in the data to '\r\n' on Windows. This has
never been supported in other browsers, and use counters show only
0.0000000002% usage and no hits in HTTPArchive. Remove the option and
associated plumbing.

Intent to Remove: ****TBD****
Chrome Status: ****TBD****

BUG=605710
R=foolip@chromium.org
==========

[foolip, 2016-07-27 18:12:29]

lgtm

https://codereview.chromium.org/2147633002/diff/40001/third_party/WebKit/Layo...
File third_party/WebKit/LayoutTests/fast/files/blob-constructor.html (right):

https://codereview.chromium.org/2147633002/diff/40001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/fast/files/blob-constructor.html:48:
shouldNotThrow("new Blob([], {endings:'illegalValue'})"); // Non-standard
'endings' entry is no longer supported.
I think keeping wpt/FileAPI/blob/Blob-constructor.html as the only negative test
would be just fine, once it's gone from the IDL it's pretty far fetched that it
would somehow regress :)