On 08/12/2013 15:03 , Robert Kaiser wrote:
That said, I think we should think about how we can enable more user
control of such features. If I open media tabs in the background, I
probably don't want them to autoplay at all.
I think that's the key part. Is there any common usage scenario in
On 08/12/13 12:28, Tetsuharu OHZEKI wrote:
On today's web, there are many interactive web sites which play
sounds when open them.
I suspect this is somewhat dependent on your culture and environment;
it's not a problem on the set of websites I visit :-)
Some of them are not controlled by
On Mon, Dec 9, 2013 at 4:48 PM, Gervase Markham g...@mozilla.org wrote:
On 08/12/13 12:28, Tetsuharu OHZEKI wrote:
On today's web, there are many interactive web sites which play
sounds when open them.
I suspect this is somewhat dependent on your culture and environment;
it's not a
On 12/8/2013 4:31 AM, Tetsuharu OHZEKI wrote:
I welcome your feedback to polish Firefox for mobile and web.
Note that autoplay is not the most interesting case, because most of the
top video sites don't actually use it; instead they use a scripted
.play() call on load.
On 12/8/2013, 4:49 AM, Robert O'Callahan wrote:
Don't these arguments apply to desktop Firefox used at work, in an Internet
cafe, or in a library, as well?
Media is a power hog on mobile, so it's worthwhile to handle it
differently there.
- mhoye
Changing the subject to make it more clear.
I will be raising this on the Monday weekly call as well as the
Engineering meeting.
On 13-12-07 03:31 PM, Armen Zambrano G. wrote:
(Please follow up on mozilla.dev.b2g)
Adding dev.platform to reach a wider audience.
I will bring this up at the
Gentle reminder that this is happening this Friday. Ideally you should
have migrated your local git clones to the new repositories by now, but if
you haven't, please take some time to do this before this Friday.
Again, if you have a reason why I should postpone this please speak up!
Cheers,
--
With some recent improvements in crash-stats data[1], we now have the
ability to report on which crashes don't have the necessary symbols to
produce a useful crash signature. I have generated the following reports
from yesterday's crash data:
On 12/10/2013 4:38 AM, Henri Sivonen wrote:
On Sun, Dec 8, 2013 at 11:49 AM, Robert O'Callahan rob...@ocallahan.org wrote:
I think it's important to have an easy way to mute/unmute the browser, but
disabling autoplay is probably not the right way to address these issues.
A pref to disable
Hi,
It seems a lot of people are using mozmake, which is good,
unfortunately, some are using an old version and i broke them with bug
944569. Those people need to upgrade mozmake by taking the last version
on either http://people.mozilla.org/~mhommey/mozmake.exe or
On Dec 9, 2013, at 19:17, Chris Pearce cpea...@mozilla.com wrote:
On 12/10/2013 4:38 AM, Henri Sivonen wrote:
On Sun, Dec 8, 2013 at 11:49 AM, Robert O'Callahan rob...@ocallahan.org
wrote:
I think it's important to have an easy way to mute/unmute the browser, but
disabling autoplay is
2013/12/10 Reuben Morais reuben.mor...@gmail.com:
Note that B2G doesn't have an about:config.
We can resolve with to add an option to gaia UI.
--
Tetsuharu OHZEKI
saneyuki.s.s...@gmail.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
2013/12/10 Benjamin Smedberg benja...@smedbergs.us:
https://bugzilla.mozilla.org/show_bug.cgi?id=944876 may be relevant: in that
bug I'm willing to mentor somebody to add a hidden pref for additional
control over autoplay behavior.
Sounds good. I feel this approach is more smart like roc said.
13 matches
Mail list logo
