Implementer interest in this spec

[marcoscaceres]

Wondering which browsers have committed to implementing this specification?

This is to help us determine if we keep this in the Charter or if we move this spec to the WICG.

[marcoscaceres]

I'm being told that this specification represents what is interoperable across browsers and that new things moved to https://wicg.github.io/entries-api/

Is that correct? If so, it would be great to update the SoTD or Abstract to reflect the above.

[annevk]

Why would that be in the SotD or Abstract?

[marcoscaceres]

Just to be clear what the spec represents.

[annevk]

I guess I don't really understand, it seems to have a pretty clear Abstract et al, albeit a tad verbose.

[marcoscaceres]

Respectfully, I disagree. Otherwise, I would not have filed the issue.

[marcoscaceres]

To be clear, this issue arose because none of the WG chairs could determine the status or level of interest in this spec. I can appreciate that people involved in the spec might know the status, but it’s unclear to external parties.

[marcoscaceres]

Alternatively is the addition of an implementation report, given that there is a test suite. That would really help.

[annevk]

Since when is any of those part of the Abstract or SotD though?

[marcoscaceres]

Argh, Anne. Stop.

[marcoscaceres]

The implementation report is fairly standard at the top of a spec.

[inexorabletash]

I'm being told that this specification represents what is interoperable across browsers and that new things moved to https://wicg.github.io/entries-api/

Entries-API itself should probably not exist; it documents some de facto standards but the contents should really be merged into FileAPI and HTML.

[inexorabletash]

Wondering which browsers have committed to implementing this specification?

"All of them" ? The four major engines all support nearly all of the spec, albeit with some interop issues: https://wpt.fyi/results/FileAPI?label=stable&aligned=true

[marcoscaceres]

Entries-API itself should probably not exist; it documents some de facto standards but the contents should really be merged into FileAPI and HTML.

ok, that’s really useful to know. Maybe we can look at what needs to go into both and start bringing stuff back from entries into this spec.

Also, it would be awesome to have the wpt.fyi link serve as the implementation report link. Helps us easily track status.

[inexorabletash]

I put up #112