-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specification status report for TPAC 2019 #121
Comments
Hi Leonie, Unfortunately I will be unable to attend TPAC this year, but here are the answers to those questions:
The Level 1 spec is reasonably mature and has two separate implementations (Chromium and WebKit). It hasn't been through a formal process, having just been migrated to W3C.
I won't be able to attend and not sure if anyone will be able to proxy for me. |
If there are implementers in the room, it would be good to discuss #107 and the features the proposed additions. It might be good to discuss if it's possible to implement on Windows or not... it seems we might be missing some things in the Windows native APIs: it's not possible to detect if the user aborts - this is the same limitation that is on Android, right @mgiuca? CC @travisleithead , @aarongustafson from Microsoft. cc @saschanaz, who has been looking at implementing on Windows via Gecko. A good follow on discussion might be to discuss what we do about bringing over Web Share Target... and if there is much hope in getting OS-level support (and if we need it). We need to evaluate the state of tests in WPT, but I imagine it's pretty good. |
@saschanaz spotted that Windows 10 SDK Preview Build 18965 has namespace Windows.ApplicationModel.DataTransfer {
public sealed class DataPackage {
event TypedEventHandler<DataPackage, object> ShareCanceled;
}
} |
Closing as answered... |
Please can you respond to this comment with a brief specifications status report for the WebApps meeting at TPAC. The report should address the following:
We're tracking these status reports in WebApps issue #19
Thanks.
The text was updated successfully, but these errors were encountered: