Re: Who loves multiple selection feature in editor?

2016-12-18 Thread Karl Dubost 
As Ehsan said:

Le 17 déc. 2016 à 02:32, Ehsan Akhgari  a écrit :
> (I also wonder how many people even know about these ways to create
> multi-range selections, given how undiscoverable they are!  We should
> probably add telemetry to measure their usage.)

I know it for a very long time and it's very practical to me when I want for 
example to reply to a specific part of a text but don't want to copy, paste and 
trim. 

It is one of these very useful features where Firefox is leading, but that we 
do not advertise this as user benefits. Missed opportunity. Instead of removing 
it I would probably vote for making it known ;)



-- 
Karl Dubost, Mozilla
http://www.la-grange.net/karl/moz

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

Re: Intent to ship: NetworkInformation

2016-12-18 Thread Karl Dubost 
When reading a thread about a new API or feature such as…

Le 16 déc. 2016 à 04:39, Ehsan Akhgari  a écrit :
>  From what I remember, the argument for shipping
> this API was that web developers have been asking for this for years,
> and they are basically happy to know the distinction between cellular
> data and other transports, and infer whether the connection "costs
> money". 


I have always in the back of my mind:

* How does it give control (benefits) to
  - users? 
  - web developers?
  - UX/Designers?
  - marketers/analytics crunchers/BD?

Maybe there is a bit more user research (or maybe Marcos knows this already) to 
do in what users want to do? I guess we all have our own ideas about it. 

Mine would be more give me a possibility to choose in the chrome what type of 
assets/performances I desire. I am on high performance bandwidth/latency 
network, but I want low-res, because I just want speed (the same way I would 
access a mobile domain m. for quick access on desktop). Or give me the high-res 
pictures on my slow network because I really need this high quality images I 
want to share with someone else and/or print.

I see a lot of benefits in user control. I see a lot of privacy issues at the 
other end of the spectrum. Privacy issues are not (often) a use case for 
service providers in the current business model. And we really never know what 
those will be before someone had an idea to "pervert" the usage of the API.


-- 
Karl Dubost, Mozilla
http://www.la-grange.net/karl/moz

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

Re: Intent to ship: NetworkInformation

2016-12-18 Thread Mike Hommey 
On Fri, Dec 16, 2016 at 12:25:03PM -0800, Jason Duell wrote:
> On Fri, Dec 16, 2016 at 11:35 AM, Tantek Çelik 
> wrote:
> 
> >
> > Honestly this is starting to sound more and more like a need for a
> > "Minimal Network" variant of the "Work Offline" option we have in
> > Firefox (which AFAIK no other current browser has), since no amount of
> > OS-level guess-work is going to give you a reliable answer (as this
> > thread has documented).
> >
> 
> So a switch that toggles the "network is expensive" bit, plus turns off
> browser updates, phishing list fetches, etc?  I can see how this would be
> nice for power users on a tethered cell phone network.  One issue would be
> to make sure users don't forget to turn it off (and never update their
> browser again, etc).  Maybe it could time out.

One thing asking the OS can do, other than give information of dubious
accuracy for the purpose of the API discussed here, is allow to tell if
things changed. So the browser could turn this off automatically (or ask
to) when the network connection changes.

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

Re: Do we have some documents listing up when we need to touch CLOBBER?

2016-12-18 Thread Mike Hommey 
On Fri, Dec 16, 2016 at 05:16:25PM +0900, Masayuki Nakano wrote:
> Hi,
> 
> I'm looking for some documents which explain when we need to touch CLOBBER
> to avoid build failure. However, I've not found such document yet. I see
> such information only in CLOBBER about WebIDL change.
> 
> So, is there any document which lists up when we need to touch CLOBBER?

The rule is that CLOBBER should never need to be touched. Unfortunately,
our build system is far from perfect, and there are plenty of cases
where that doesn't actually hold true. There are a bunch of bugs filed
for those cases, and new ones should be filed and marked as blocking bug
#941904. IOW, the dependencies of bug #941904 that are still open are
the currently known cases where a CLOBBER was required, but many of them
are of the form "bug # required a clobber".

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