Hi,
I think two prefs are needed.
In addition to the pref discussed in this topic, "make all media on any tabs be
click-to-play" is needed to ensure the Web Accessibility.
UAAG2 (User Agent Accessibility Guidelines 2.0) LCWD [1] contains two "Level A"
success criteria related to this topic.
-
Henri Sivonen schrieb:
If autoplay is disabled by default, Web authors will take
counter-measures and start playback from JavaScript. However, if
autoplay is honored by default but the user can turn in off as a pref,
it could be that Web authors won't bother to take counter-measures.
It probabl
On 12/11/2013 4:18 PM, Alex Jordan wrote:
On Dec 10, 2013 6:30 PM, "Chris Pearce" wrote:
We could add a pref that caused HTMLMediaElement.play() to only work if
called from inside a user generated event handler (i.e. mouse click, key
press). That would achieve most of what you want, and is ver
On Dec 10, 2013 6:30 PM, "Chris Pearce" wrote:
> We could add a pref that caused HTMLMediaElement.play() to only work if
called from inside a user generated event handler (i.e. mouse click, key
press). That would achieve most of what you want, and is very easy to
implement.
This seems like it migh
On 12/11/2013 3:07 PM, Tetsuharu OHZEKI wrote:
2013/12/11 Hubert Figuière :
It should be noted that here on desktop I do have
`media.autoplay.enabled=false` (I hate videos that autoplay) and this
still doesn't stop YouTube. [1]
I seem that Gecko's implementation of HTMLMediaElement.play() doesn
2013/12/11 Hubert Figuière :
> It should be noted that here on desktop I do have
> `media.autoplay.enabled=false` (I hate videos that autoplay) and this
> still doesn't stop YouTube. [1]
I seem that Gecko's implementation of HTMLMediaElement.play() doesn't
handle `media.autoplay.enabled`.
http://m
2013/12/11 Hubert Figuière :
> Power? How about not blowing through your data cap allowance or paying
> and other hefty charges
>
> Very few countries have cheap unlimited data over cellular.
Of course, it includes network data traffic. I hope it saves power/data cost :)
--
Tetsuharu OHZEKI
On 08/12/13 04: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?
>
> 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 addres
On 09/12/13 08:44 PM, Tetsuharu OHZEKI wrote:
> For mobile, this delaying approach is well for saving power. I feel
> this approach make sense.
Power? How about not blowing through your data cap allowance or paying
and other hefty charges
Very few countries have cheap unlimited data over cell
2013/12/10 Benjamin Smedberg :
> 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.
> For desktop Fi
2013/12/10 Reuben Morais :
> 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
https://lists.mozilla.o
On Dec 9, 2013, at 19:17, Chris Pearce wrote:
> On 12/10/2013 4:38 AM, Henri Sivonen wrote:
>> On Sun, Dec 8, 2013 at 11:49 AM, Robert O'Callahan
>> 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 addre
On 12/10/2013 4:38 AM, Henri Sivonen wrote:
On Sun, Dec 8, 2013 at 11:49 AM, Robert O'Callahan 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 autoplay might be, though
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
__
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.
https://bugzilla.mozil
On Sun, Dec 8, 2013 at 11:49 AM, Robert O'Callahan 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 autoplay might be, though.
If autoplay is disabled by default, Web
On Mon, Dec 9, 2013 at 4:48 PM, Gervase Markham 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 problem on th
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 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 whi
Maybe we can build something clever based on the per-window volume and
muting infrastructure in bug 923247? I think easy per-tab muting is a good
thing to try here.
Rob
--
Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?
2013/12/8 Robert Kaiser :
> I personally have not yet seen any arguments that would really apply for
> making things different between mobile and desktop in your discussion, and I
> think we should not make functionality different between form factors or
> products when there is no good reason to m
Tetsuharu OHZEKI schrieb:
I propose that we should disable "autoplay" feature of
HTMLMediaElement on mobile.
I personally have not yet seen any arguments that would really apply for
making things different between mobile and desktop in your discussion,
and I think we should not make functiona
2013/12/8 Robert O'Callahan :
> Don't these arguments apply to desktop Firefox used at work, in an Internet
> cafe, or in a library, as well?
True.
This proposal could be applied to desktop Firefox. But I seem it would
be hard because of historical reasons.
On today's web, there are many "interact
Don't these arguments apply to desktop Firefox used at work, in an Internet
cafe, or in a library, as well?
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.
Rob
--
Jtehsauts tshaei dS,o n" Wohfy
Hi,
In Last week, I proposed the following mail to mobile-firefox-dev mailing list.
I feel this proposal is related to not only Fennec, but also B2G.
So I would like to hear your opinions.
Best Regards.
-- Forwarded message --
Hello,
I propose that we should disable "autoplay"
25 matches
Mail list logo
