Fixed the directory upload test

[phistuck]

Included a prefixed version.

I cannot find any specification that defined HTMLInputElement.prototype.directory (perhaps an old version of https://wicg.github.io/directory-upload/proposal.html - no idea) and Chrome does support a prefixed version of that (webkitDirectory) anyway, however, it does not support window.Directory (or any prefixed equivalent), so I think it is fine to use that for now instead of relying on a specification that is changing as we speak.

It makes sense to me to just put it in a bonus points section. Also, a link to the specification is missing.

[NielsLeenheer]

The webkitDirectory property is unrelated to this specification. It is a proprietary implementation that is not part of any specification.

And you are right regarding the directory property not existing (anymore). It is renamed to allowdirs, probably to avoid conflicts with webkitDirectory.

So, the test should be fixed, but webkitDirectory should not be part of it. Perhaps that can be a separate test for next update (in 2-3 months).

[phistuck]

Included a prefixed version.

I cannot find any specification that defined HTMLInputElement.prototype.directory (perhaps an old version of https://wicg.github.io/directory-upload/proposal.html - no idea) and Chrome does support a prefixed version of that (webkitDirectory) anyway, however, it does not support window.Directory (or any prefixed equivalent), so I think it is fine to use that for now instead of relying on a specification that is changing as we speak.

It makes sense to me to just put it in a bonus points section. Also, a link to the specification is missing.

[NielsLeenheer]

The webkitDirectory property is unrelated to this specification. It is a proprietary implementation that is not part of any specification.

And you are right regarding the directory property not existing (anymore). It is renamed to allowdirs, probably to avoid conflicts with webkitDirectory.

So, the test should be fixed, but webkitDirectory should not be part of it. Perhaps that can be a separate test for next update (in 2-3 months).

[phistuck]

Included a prefixed version.

I cannot find any specification that defined HTMLInputElement.prototype.directory (perhaps an old version of https://wicg.github.io/directory-upload/proposal.html - no idea) and Chrome does support a prefixed version of that (webkitDirectory) anyway, however, it does not support window.Directory (or any prefixed equivalent), so I think it is fine to use that for now instead of relying on a specification that is changing as we speak.

It makes sense to me to just put it in a bonus points section. Also, a link to the specification is missing.

[NielsLeenheer]

The webkitDirectory property is unrelated to this specification. It is a proprietary implementation that is not part of any specification.

And you are right regarding the directory property not existing (anymore). It is renamed to allowdirs, probably to avoid conflicts with webkitDirectory.

So, the test should be fixed, but webkitDirectory should not be part of it. Perhaps that can be a separate test for next update (in 2-3 months).

[phistuck]

Included a prefixed version.

I cannot find any specification that defined HTMLInputElement.prototype.directory (perhaps an old version of https://wicg.github.io/directory-upload/proposal.html - no idea) and Chrome does support a prefixed version of that (webkitDirectory) anyway, however, it does not support window.Directory (or any prefixed equivalent), so I think it is fine to use that for now instead of relying on a specification that is changing as we speak.

It makes sense to me to just put it in a bonus points section. Also, a link to the specification is missing.

[NielsLeenheer]

The webkitDirectory property is unrelated to this specification. It is a proprietary implementation that is not part of any specification.

And you are right regarding the directory property not existing (anymore). It is renamed to allowdirs, probably to avoid conflicts with webkitDirectory.

So, the test should be fixed, but webkitDirectory should not be part of it. Perhaps that can be a separate test for next update (in 2-3 months).

[phistuck]

Included a prefixed version.

I cannot find any specification that defined HTMLInputElement.prototype.directory (perhaps an old version of https://wicg.github.io/directory-upload/proposal.html - no idea) and Chrome does support a prefixed version of that (webkitDirectory) anyway, however, it does not support window.Directory (or any prefixed equivalent), so I think it is fine to use that for now instead of relying on a specification that is changing as we speak.

It makes sense to me to just put it in a bonus points section. Also, a link to the specification is missing.

[NielsLeenheer]

The webkitDirectory property is unrelated to this specification. It is a proprietary implementation that is not part of any specification.

And you are right regarding the directory property not existing (anymore). It is renamed to allowdirs, probably to avoid conflicts with webkitDirectory.

So, the test should be fixed, but webkitDirectory should not be part of it. Perhaps that can be a separate test for next update (in 2-3 months).

[phistuck]

Included a prefixed version.

I cannot find any specification that defined HTMLInputElement.prototype.directory (perhaps an old version of https://wicg.github.io/directory-upload/proposal.html - no idea) and Chrome does support a prefixed version of that (webkitDirectory) anyway, however, it does not support window.Directory (or any prefixed equivalent), so I think it is fine to use that for now instead of relying on a specification that is changing as we speak.

It makes sense to me to just put it in a bonus points section. Also, a link to the specification is missing.

[NielsLeenheer]

The webkitDirectory property is unrelated to this specification. It is a proprietary implementation that is not part of any specification.

And you are right regarding the directory property not existing (anymore). It is renamed to allowdirs, probably to avoid conflicts with webkitDirectory.

So, the test should be fixed, but webkitDirectory should not be part of it. Perhaps that can be a separate test for next update (in 2-3 months).

[phistuck]

Included a prefixed version.

I cannot find any specification that defined HTMLInputElement.prototype.directory (perhaps an old version of https://wicg.github.io/directory-upload/proposal.html - no idea) and Chrome does support a prefixed version of that (webkitDirectory) anyway, however, it does not support window.Directory (or any prefixed equivalent), so I think it is fine to use that for now instead of relying on a specification that is changing as we speak.

It makes sense to me to just put it in a bonus points section. Also, a link to the specification is missing.

[NielsLeenheer]

The webkitDirectory property is unrelated to this specification. It is a proprietary implementation that is not part of any specification.

And you are right regarding the directory property not existing (anymore). It is renamed to allowdirs, probably to avoid conflicts with webkitDirectory.

So, the test should be fixed, but webkitDirectory should not be part of it. Perhaps that can be a separate test for next update (in 2-3 months).

[phistuck]

Included a prefixed version.

I cannot find any specification that defined HTMLInputElement.prototype.directory (perhaps an old version of https://wicg.github.io/directory-upload/proposal.html - no idea) and Chrome does support a prefixed version of that (webkitDirectory) anyway, however, it does not support window.Directory (or any prefixed equivalent), so I think it is fine to use that for now instead of relying on a specification that is changing as we speak.

It makes sense to me to just put it in a bonus points section. Also, a link to the specification is missing.

[NielsLeenheer]

The webkitDirectory property is unrelated to this specification. It is a proprietary implementation that is not part of any specification.

And you are right regarding the directory property not existing (anymore). It is renamed to allowdirs, probably to avoid conflicts with webkitDirectory.

So, the test should be fixed, but webkitDirectory should not be part of it. Perhaps that can be a separate test for next update (in 2-3 months).