Re: Status of support for Android on ARMv7 without NEON

2017-10-10 Thread didi 
On Tuesday, May 23, 2017 at 10:00:47 PM UTC+2, haxe...@gmail.com wrote:
> I was updating from Google Play without any warning on my -indeed very old 
> but good functioning- ASUStransformer tf101. Took even a while to figure out 
> what the problem was and why all of a sudden FF didn't work anymore.
> PtrK

I'm in a similar situation: Firefox stopped working on my TF101 (which even 
runs Android 6) after upgrade.
In my case the upgrade was done downloading the APK directly from Mozilla (link 
from https://wiki.mozilla.org/Mobile/Platforms/Android), not Play store.

Is it now impossible to build APKs which run on this platform?

Where can I find an APK of previous versions?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

W3C Proposed Recommendation: Cooperative Scheduling of Background Tasks (requestIdleCallback)

2017-10-10 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:

  Cooperative Scheduling of Background Tasks
  https://www.w3.org/TR/requestidlecallback/
  https://w3c.github.io/requestidlecallback/
  Deadline for responses: Tuesday, November 7, 2017

If there are comments you think Mozilla should send as part of the
review, please say so in this thread.  Ideally, such comments should
link to github issues filed against the specification.  (I'd note,
however, that there have been previous opportunities to make
comments, so it's somewhat bad form to bring up fundamental issues
for the first time at this stage.)

Given that this is something that I believe we implement, we should
be voting on this, even if that vote is just to support without any
comments.  But I'd definitely like to hear from somebody
knowledgable about the spec and our implementation before just doing
that.

-David

-- 
𝄞   L. David Baron http://dbaron.org/   𝄂
𝄢   Mozilla  https://www.mozilla.org/   𝄂
 Before I built a wall I'd ask to know
 What I was walling in or walling out,
 And to whom I was like to give offense.
   - Robert Frost, Mending Wall (1914)


signature.asc
Description: PGP signature
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Status of support for Android on ARMv7 without NEON

2017-10-10 Thread Ralph Giles 
On Tue, Oct 10, 2017 at 5:43 AM,  wrote:


> Is it now impossible to build APKs which run on this platform?
>

Some patching would be required.


> Where can I find an APK of previous versions?
>

Historic versions of Firefox for Android can be found at
https://archive.mozilla.org/pub/mobile/releases/ Please not that these will
have unpatched security vulnerabilities, so I don't recommend them for
daily use.

 -r
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Looking for testers: Lenovo M30-70 laptop

2017-10-10 Thread Jim Mathies 
Hey all,

If you have a Lenovo laptop with specs similar to this:

Lenovo M30-70 Notebook
Intel Core i3-4030U
Synaptics ClickPad V1.2

I'd appreciate it if you could try to reproduce Library window scrolling bug 
1399126 [1], and if you can, help debug it. Mostly I just want to confirm that 
in a standard config for this laptop, the issues *doesn't* reproduce.

Thanks for the help!
Jim

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1399126 
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Changes to tab min-width

2017-10-10 Thread Jeff Griffiths 
On Oct 6, 2017 07:50, "Boris Zbarsky"  wrote:

On 10/6/17 9:52 AM, Nicolas B. Pierron wrote:

> I will add that 91% of the session on release have 12 or fewer tabs, and
> thus would not be concerned at all by these changes.
>

Do we actually know that?

As I said upthread, at the 100px tab width my tabs start to scroll when
adding the 9th tab.



This is highly dependent on screen size. For me it's 12, for you 9, on
large desktop LCD monitors probably 20+.

The more interesting comparison to me is "tab identifiability" ( heh ) vs
chrome, which is a complex issue. Feedback has included questions about
reduced identifiability with two extreme points of view expressed: people
who think favicons are enough, and people who need some tab title context.
I take very seriously the use case for the latter expressed here - lots of
tabs opened to the same site.

In this first phase, the question is, what is the minimum thing we can do
to tackle this issue and the feedback. We've uncovered a number of aspects
of the tab design that impact "tab identifiability" that causes problems
for some users at various settings, but a more complex patch to address
these in some way is out of scope. We simply don't have time.

To bring this discussion to a conclusion, after some discussion in the second
bug  we're landing a
patch that re-introduces the preference, and sets the minimum to 76. There
are some remaining edge cases that aren't a great experience, but we think
the improvement is worthwhile overall and in particular having the pref
available is necessary as this seems to be a very polarizing issue.

Stephen and I will be working wit the UX and frontend teams on strategies
to mitigate the problems we uncovered by looking into this, I hope to see
things improve over the next few cycles.

thanks, Jeff



-Boris

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Status of support for Android on ARMv7 without NEON

2017-10-10 Thread dho 
On Tuesday, October 10, 2017 at 6:13:03 PM UTC+2, Ralph Giles wrote:
> Some patching would be required.
Doesn't sound like something somebody without knowledge of the code can do in 
reasonable time.

> Historic versions of Firefox for Android can be found at
> https://archive.mozilla.org/pub/mobile/releases/ 
Thx, that helps a lot!

> Please not that these will
> have unpatched security vulnerabilities, so I don't recommend them for
> daily use.
Sure!
There seem however not to be so many alternatives. On this device I have an 
Open Source only policy, thus e.g. Chrome is not an option.
I tried Brave, doesn't start (probably for the same reason).
For the time being I feel safe enough with Firefox 52 and all trackers blocked. 
The device is mostly used for reading, not for wild Safaris :-)

Btw. I needed to reinstall Fennec after the failed upgrade.
While I have Sync set up, I'm not able to restore the previous state.
Despite having the same device name, the new install created a new logical 
device with initial settings. Is there a way to restore from the previous 
instance?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Changes to tab min-width

2017-10-10 Thread Boris Zbarsky 

On 10/10/17 1:11 PM, Jeff Griffiths wrote:

This is highly dependent on screen size.


It's dependent on window size.  And I was just pointing out that the 
post I was replying to assumes that "12 or fewer tabs" means "not 
scrolling", whereas we have no obvious data to that effect.


That is, we have telemetry for number of tabs.  We have telemetry for 
screen sizes, iirc.  I don't know whether we have telemetry for _window_ 
sizes at all.  And we don't have telemetry for "window size divided by 
number of tabs", which is what we would need to know what fraction of 
people have overflowing tabs.


We could approximate this last if we have telemetry for window size (or 
assume that window size closely tracks screen size) and assume that 
number of tabs is uncorrelated with window or screen size.  But it's not 
clear to me how justified such an assumption would be.


I was addressing just this one statistical analysis point, not the 
broader question of what the right behavior is here.


-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Setting expectations for sheriffing over the next month

2017-10-10 Thread Chris Cooper 
Our code sheriffing bandwidth is greatly reduced right now. We
continue to train up the SoftVision (SV) sheriffing contractors to
assist with backouts and merges on a 24/7 basis, but they are not
ready yet.

What does this mean for you?

In the short term, this means the sheriffs can only guarantee one
merge per day. The sheriffing team (staff/community/contractors) will
try to keep the trees sufficiently green to *enable* a second daily
merge, but the merge may or may not happen, depending on the
availability of a senior sheriff to perform the merge.

As developers, you can help by being a little more conservative with
your code landings. Use autoland as much as possible, and make sure
your try results don't have obvious anomalies before pushing to
inbound. Most of you already do this, so thanks for that.

I know this may be inconvenient for people, but I appreciate your
patience during this interval. With any luck, we should be back to
normal in a few weeks.

If you do have any questions, please direct them to me.

cheers,
--
coop
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Switching language packs to WebExtensions

2017-10-10 Thread zbraniecki 
Hi dev.platform,


We're planning to switch language packs to use the new WebExtensions platform 
somewhere down this week [0].


This is a very important change on that enables us to enable the first 
milestone on the path to the new localization API [1].

In a longer term, we hope to promote language packs to first tier localization 
experience which would allow us to look into switching from building 100+ 
builds, to building a single build and 100+ langpacks.

In the short term, this makes our language packs support L20n, but also makes 
them safer, easier to maintain, and no longer a blocker to removal of the old 
addons code.

If you notice any issues with the new code, please, contact L10n Drivers team.

zb.


[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1402061
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform