Intent to Implement: Web Animations API

2014-04-17 Thread Brian Birtles
Summary: Allow web authors to inspect/debug/control running CSS (and SVG) animations and create new animations Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=875219 Link: http://dev.w3.org/fxtf/web-animations/ Platform coverage: All platforms Estimated or target release: late 2014 Prefere

Re: Intent to ship: :scope support in querySelector(All)

2014-04-17 Thread Cameron McCormack
Boris Zbarsky: > We've been shipping :scope in querySelector(All) for a while now, > enabled in nightly/aurora, disabled in beta/release. > > The spec is no longer trying to do wild and wooly stuff with it, so > I believe our implementation matches the spec. > > Any objections to turning this on?

Intent to ship: :scope support in querySelector(All)

2014-04-17 Thread Boris Zbarsky
We've been shipping :scope in querySelector(All) for a while now, enabled in nightly/aurora, disabled in beta/release. The spec is no longer trying to do wild and wooly stuff with it, so I believe our implementation matches the spec. Any objections to turning this on? Anyone actively in agre

Re: Intent to Implement: Web Activities for Android

2014-04-17 Thread Jonas Sicking
In FirefoxOS we already limit the ability to *handle* an activity to webapps, however we do allow websites to initiate an activity. I think it would make sense to only allow webapps to both handle and initiate activities on android. This way we can limit exposure until we have a solution that is m

Re: Oculus VR support & somehwat-non-free code in the tree

2014-04-17 Thread Kyle Machulis
So querying and tying together peripherals is a big, big issue in VR. It's why VRPN exists (I've got a few drivers that are linked to that, for haptics, cameras, etc). Has anyone looked at that or other ways the VR community has already exposed this stuff? I realize kinect/oculus/etc are the new

Intent to implement W3C Manifest for web application

2014-04-17 Thread Marcos Caceres
Summary:   JSON-based manifest, which provides developers with a centralized place to put metadata associated with a web application. This includes, but is not limited to, the web application's name, links to icons, as well as the preferred URL to open when the user launches the web application

Intent to Implement: ServiceWorkers

2014-04-17 Thread nsm . nikhil
Hello, For the past few months Mozilla and Google have been working on spec and prototype implementation for ServiceWorkers [1][2]. ServiceWorkers are client side proxies that can intercept navigation events and provide their own responses. They are intended as a programmatic AppCache replaceme

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-17 Thread Ehsan Akhgari
On 2014-04-17, 1:31 PM, Bobby Holley wrote: On Thu, Apr 17, 2014 at 10:00 AM, Ehsan Akhgari mailto:ehsan.akhg...@gmail.com>> wrote: What would be your opinion on the interim use of ifdef (or moz.build equivalent) to prevent some or all of those files from being built on

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-17 Thread Kyle Huey
On Thu, Apr 17, 2014 at 12:09 AM, Henri Sivonen wrote: > I am not done preparing the removal patches yet, but with my current > patch queue I can already get 149 KB off of Android ARMv7 optimized > apk size and 138 KB off of Android ARMv7 optimized libxul size. (I'm > not sure what sort of size wi

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-17 Thread Bobby Holley
On Thu, Apr 17, 2014 at 10:00 AM, Ehsan Akhgari wrote: > What would be your opinion on the interim use of ifdef (or moz.build > >> equivalent) to prevent some or all of those files from being built on >> browser builds? >> > > I think this is the right thing to do. > We still want this code to di

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-17 Thread Ehsan Akhgari
On 2014-04-17, 10:00 AM, Neil wrote: Henri Sivonen wrote: I am not done preparing the removal patches yet, but with my current patch queue I can already get 149 KB off of Android ARMv7 optimized apk size and 138 KB off of Android ARMv7 optimized libxul size. What would be your opinion on the

Re: Dehydra status

2014-04-17 Thread Joshua Cranmer 🐧
On 4/17/2014 11:32 AM, Eric Shepherd wrote: Dehydra's documentation warns against using it due to its not having been updated in some time. Does that mean that it's safe to archive this content? Dehydra is, for all intents and purposes, dead. It certainly won't compile anymore due to JSAPI

Re: Dehydra status

2014-04-17 Thread Ehsan Akhgari
On 2014-04-17, 12:32 PM, Eric Shepherd wrote: Dehydra's documentation warns against using it due to its not having been updated in some time. Does that mean that it's safe to archive this content? Yes. ___ dev-platform mailing list dev-platform@lists

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-17 Thread Chris Peterson
On 4/17/14, 12:09 AM, Henri Sivonen wrote: In theory, Gecko engineers are not supposed to use time for tweaking c-c. Yet, just going ahead and totally burning c-c would be terribly impolite and at odds with the notion of Mozilla continuing to keep Thunderbird builds going. That's why I tried to p

Re: Oculus VR support & somehwat-non-free code in the tree

2014-04-17 Thread Vladimir Vukicevic
On Thursday, April 17, 2014 10:18:01 AM UTC-4, Gervase Markham wrote: > > The good news is that with the preview release of the latest SDK, > > they added a C API that does everything that we need. So this might > > become a moot point; we can dlopen/dlsym our way to victory, and I'm > > already r

Dehydra status

2014-04-17 Thread Eric Shepherd
Dehydra's documentation warns against using it due to its not having been updated in some time. Does that mean that it's safe to archive this content? -- Eric Shepherd Developer Documentation Lead Mozilla Blog: http://www.bitstampede.com/ Twitter: @sheppy __

Re: Oculus VR support & somehwat-non-free code in the tree

2014-04-17 Thread Gervase Markham
On 17/04/14 05:55, Vladimir Vukicevic wrote: > Already in the works. :) Awesome :-) > The good news is that with the preview release of the latest SDK, > they added a C API that does everything that we need. So this might > become a moot point; we can dlopen/dlsym our way to victory, and I'm > a

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-17 Thread Neil
Henri Sivonen wrote: I am not done preparing the removal patches yet, but with my current patch queue I can already get 149 KB off of Android ARMv7 optimized apk size and 138 KB off of Android ARMv7 optimized libxul size. What would be your opinion on the interim use of ifdef (or moz.build e

Re: "Unresponvie plugin" error with NPAPI plugins

2014-04-17 Thread Georg Fritzsche
On 17 Apr 2014, at 09:00, Girish Gaitonde wrote: > We have developed NPAPI based plugin in firefox. > We are using "addon-sdk-1.14" and currently it is working properly with > > latest Firefox ver 28. > > But as all the calls are Synchronous calls, firefox throws a

Re: Oculus VR support & somehwat-non-free code in the tree

2014-04-17 Thread Mike Hommey
On Wed, Apr 16, 2014 at 09:55:02PM -0700, Vladimir Vukicevic wrote: > On Wednesday, April 16, 2014 9:00:40 PM UTC-4, Eric Rahm wrote: > > So who actually needs to talk to Oculus? I can try to reach out some > > folks I used to work with who are there now and see if they're > > interested in makin

Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-17 Thread Henri Sivonen
Thanks to the work that Anne has done on the Encoding Standard specification and the work that Masatoshi Kimura and I have done to progressively implement the specification in Firefox, we are now at a point where there's a whole bunch of internationalization-related dead code in Firefox. The code i

"Unresponvie plugin" error with NPAPI plugins

2014-04-17 Thread Girish Gaitonde
Hi All, We have developed NPAPI based plugin in firefox. We are using "addon-sdk-1.14" and currently it is working properly with latest Firefox ver 28. But as all the calls are Synchronous calls, firefox throws a message stating "Unresponsive plugin". Ca