W3C Proposed Recommendation: Webmention

2016-11-03 Thread Tantek Çelik
Support :) I'm co-chair of the WG that produced this PR, as well as familiar with and contributed to its incubation/prototyping/implementation (including on my own site tantek.com) in the IndieWeb community before we brought it to a W3C WG for broader review and consideration. Happy to answer any

Re: W3C Proposed Recommendation: Webmention

2016-11-03 Thread Joe Hildebrand
The JSON reference really needs to be to RFC 7159, not 4627. (blocking, but trivial issue) There should be some mention of the prior art in this space. Pingbacks and trackbacks at least. Please differentiate this approach from them, so we have an idea if we need to do this also. Many Wordpre

Fwd: New Correlations on crash-stats

2016-11-03 Thread Nicholas Nethercote
[Forwarding this to a wider audience because this is a big deal. Please try out these correlations! They can be critical in diagnosing the cause of a crash.] -- Forwarded message -- From: Adrian Gaudebert Date: Fri, Nov 4, 2016 at 1:11 PM Subject: New Correlations on crash-stats

Re: W3C Proposed Recommendation: Webmention

2016-11-03 Thread Martin Thomson
On Fri, Nov 4, 2016 at 1:25 PM, L. David Baron wrote: > W3C Editor's draft: https://webmention.net/draft/ Wow, that is an extraordinarily wordy document for something that does so little. It's the first I've heard of this, but it's remarkably similar to (albeit much narrower than): https://ww

W3C Proposed Recommendation: Webmention

2016-11-03 Thread L. David Baron
A W3C Proposed Recommendation is available for the membership of W3C (including Mozilla) to vote on, before it proceeds to the final stage of being a W3C Recomendation: Webmention W3C TR draft: https://www.w3.org/TR/webmention/ W3C Editor's draft: https://webmention.net/draft/ deadline: We

Intent to ship: requestIdleCallback

2016-11-03 Thread Andreas Farre
As of 2016-11-7 I intend to turn requestIdleCallback on by default (with the condition that https://bugzilla.mozilla.org/show_bug.cgi?id=1314314 has landed). It has been developed behind the dom.requestIdleCallback.enabled preference. Other UAs shipping this or intending to ship it are Chrome (ship

Re: Error handling with MOZ_MUST_USE

2016-11-03 Thread Michael Layzell
We also have a static analysis attribute MOZ_MUST_USE_TYPE which can be added to class declarations to ensure that those declarations are always used when they are returned. We currently are using it to annotate already_AddRefed values. If there are other types which universally should be checked w

Error handling with MOZ_MUST_USE

2016-11-03 Thread Wei-Cheng Pan
Hi, As :njn announced before [1], we are trying to add MOZ_MUST_USE to all fail-able functions, which is tracking in bug 1268766 [2]. We have bugs to track the progress for each directory. If anyone is interested, please feel free to take any of the bugs. We hope all reviewers also mind the foll

Re: Removing navigator.buildID?

2016-11-03 Thread Henri Sivonen
On Tue, Nov 1, 2016 at 10:09 AM, Chris Pearce wrote: > It's not just Netflix that the media playback team has used > navigator.buildID in order to validate fixes; we've used it with other large > video sites too. It's invaluable for determining whether a bug has been > fixed in a build. Can we onl