thanks fabrice for bringing some clarity to the issue. On 11 Jan 2013 18:31, "Fabrice Desre" <fabr...@mozilla.com> wrote:
> Hi David, > > On 01/11/2013 06:09 PM, David Bruant wrote: > > > I've discovered on the devengage mailing list [1] that as of January > > 10th, remote debugging for FirefoxOS has been disabled. This is quite > > unfortunate, because remote debugging makes a tremendous difference in > > my work studying and documenting the APIs. It's also obviously a much > > needed feature for app developers. > > A couple of questions remain unanswered: > > * Why has this been decided? > > The remote debugging support we have currently on b2g only allow > debugging the chrome process. This was a huge security issue since this > process runs as root on device. Unfortunately the work needed to debug > content processes is not finished yet (there are bugs filed, but I don't > know the numbers). > > > * Is it planned to re-enable it in its previous form? a new form? > > As soon as the devtools team get content processes debugging working, > we'll happily enable that support. Note that we didn't disable support > on b2g desktop, where out of process is disabled, so devs can debug there. > > > * Has a date or milestone been decided to fix this issue? > > I don't know. Panagiotis may tell us more! > > > * If it takes too long to fix, what are the other ways to debug apps on > > an actual device? > > None that I know of. > > > Besides these questions to understand the current situation, I'd like to > > discuss a trend I'm noticing. I am under the impression that app > > developers are becoming a growing population of the FirefoxOS ecosystem > > especially with Mozilla increasingly reaching out to potential such > > developers (app days all over the globe in the upcoming weeks). I feel > > it will become increasingly important for this population to have a > > stable development environment and if for good reasons the environment > > can't be kept stable, alert this population of the upcoming change that > > may affect it. > > I agree. But we have tight schedules so we can't usually give notice too > much in advance. For this particular topic, we discussed the problem and > solutions on Monday, and got code landed Wednesday. Being in a frantic > work week, we didn't make a great job reaching out to developers. We'll > do our best to better communicate such changes in the future. > > Cheers, > > Fabrice > -- > Fabrice Desré > b2g team > Mozilla Corporation > _______________________________________________ > engagement-developers mailing list > engagement-develop...@lists.mozilla.org > https://lists.mozilla.org/listinfo/engagement-developers > _______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
