RE: [clipboard events] seeking implementor feedback on using CID: URI scheme for pasting embedded binary data

[Ben Peters]

 Second, can you provide the javascript for how a site would put them into 
 the pasted markup during paste?

>>> The way I thought this would work, would be that the site starts XHR 
>>> uploads from the paste processing, and shows some intermediate 'loading' 
>>> animation or something before it gets the final URLs back from the server.

>> This generally makes sense. If sites prefer to use local dataURI or 
>> blob, they can use the blob URL, and then upload the file later (like 
>> in an email scenario). This means they don't have to wait for them to 
>> be on the server before displaying them. If they want to upload them first 
>> and use the server's new URL for them, they would need to do what you're 
>> saying.

>Sounds good, but this requires standardising something similar to 
>msConvertURL(), right?

I don't believe so. Couldn't the site just get the HTML DataTransferItem (which 
contains the CIDs), replace the CIDs with Blobs or DataURIs, and then insert 
the HTML where the paste was going to happen? Personally I think msConvertURL 
is a convenient way to do this. But it's not the only way.

-Ben

Re: [admin] Draft of updated charter available for review

[Arthur Barstow]

On 1/21/14 3:36 PM, ext Arthur Barstow wrote:
Although WebApps' current charter [Charter] does not expire until the 
end of May, since it can take a while to agree on a new charter 
(especially if new deliverables are proposed), I created a Draft 
[Draft] today. A diff of the current charter vs. the draft is 
available at [Diff].



Hi All,

Last week I checked in two changes to the [Draft] charter:

[1] Added a statement that the expectation is WebApps will be 
re-chartered after the 2014-2016 charter expires (this is intended to 
reinforce a related statement already in the charter.


[2] Philippe reminded me the Consortium's process requires a WG charter 
include "milestone" data so I added 5 "priority" specs that are 
dependencies for specs by other groups and included my best "guestimate" 
on these specs' next milestone. I also included a link to [PubStatus] 
and state it should be used for current status of all of WebApps' specs.


WebApps' current [Charter] has nine specs with milestones and none of 
our predictions for the REC milestone were accurate. Because of this, my 
original draft did not include any milestone data. Although I think 
milestone data should be useful, I only support adding data if there is 
a relatively good probability plus resource commitment(s) to meet the 
milestone.


Feedback on the new milestone data as well as proposals for other specs 
and their next milestone is welcome.


-Thanks, AB

[Draft] 
[1] 

[2] 





[Charter] 
[Draft] 
[Diff]