[Bug 27466] https://dvcs.w3.org/hg/innerhtml/raw-file/tip/index.html#concept-serialize link is stale

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27466

Anne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Anne  ---
https://github.com/whatwg/xhr/commit/829579048b349bbab3fd24c33f5faf822d5f3c0b

-- 
You are receiving this mail because:
You are on the CC list for the bug.

PSA: publishing new WD of Clipboard API and events on December 9

[Arthur Barstow]

Hallvord would like to publish a new WD of Clipboard API and events and 
the plan is to publish that WD on or around December 9.


If anyone has any major concerns about this plan, please reply as such 
right away.


-Thanks, AB

Re: clipboard-apis spec reorganised

[Hallvord R. M. Steen]

> Do you want me to start a PSA (to publish a new WD) now; or do you still 
> have some changes you want to make before publishing a new TR?

I haven't re-checked the pubrules but otherwise it should be ready to go. So 
let's do the PSA.
-Hallvord

Re: [Push-API] Browser Implementation

[Arthur Barstow]

On 12/5/14 6:19 AM, Daniel Bevenius wrote:

Hi,

I've been trying to find a browser build that support the Push-API but 
failed. I was wondering if anyone on this list could point me to a 
revision/build that I might be able to build and try out.


Hi Daniel,

FYI, there are related Intent to Implement threads on the [blink-dev] 
and [mozilla.dev.platform] lists.


I don't know the latest status of either of these implementations and 
would appreciate updates on these, as well as any other Push API 
implementations.


-Thanks, AB

[blink-dev] 

[mozilla.dev.platform] 

[custom-elements] Re: web developer conformance requirements and advice in custom elements spec

[Arthur Barstow]

On 12/6/14 4:21 AM, Steve Faulkner wrote:

Hi all,

looking at the custom elements spec 
http://w3c.github.io/webcomponents/spec/custom/ i realized it includes 
no defined requirements or advice for web developers on creation of 
custom elements that are meaningful and expose useful semantics and 
behavior.


I would like to take a stab at this, what's the best way to 
contribute? pull requests?


Hi Steve,

Yes, it appears you should submit a PR to [1] and I'm sure Dimitri will 
clarify if he recommends otherwise.


BTW Dimitri - it looks like the ED has some relatively substantive 
changes since the last TR was published (October 2013) [Diff]. As such, 
it seems like the TR should be updated. WDYT?


-Thanks, AB

[1] https://github.com/w3c/webcomponents
[Diff] 
http://services.w3.org/htmldiff?doc1=http%3A%2F%2Fwww.w3.org%2FTR%2F2013%2FWD-custom-elements-20131024%2F&doc2=http%3A%2F%2Fw3c.github.io%2Fwebcomponents%2Fspec%2Fcustom%2F

web developer conformance requirements and advice in custom elements spec

[Steve Faulkner]

Hi all,

looking at the custom elements spec
http://w3c.github.io/webcomponents/spec/custom/ i realized it includes no
defined requirements or advice for web developers on creation of custom
elements that are meaningful and expose useful semantics and behavior.

I would like to take a stab at this, what's the best way to contribute?
pull requests?


--

Regards

SteveF
HTML 5.1