<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/02/2015 18:48, Russ Thomas wrote:<br>
</div>
<blockquote
cite="mid:CAJe+eoHiJxXW_rsPj2rExatbuJ=kum9U-zMqqyf_wGK8wMY_iw@mail.gmail.com"
type="cite">
<div dir="ltr">On Wed Feb 11 2015 at 11:15:52 AM Gijs Kruitbosch
<<a moz-do-not-send="true"
href="mailto:gijskruitbosch@gmail.com" target="_blank">gijskruitbosch@gmail.com</a>>
wrote:<br>
<div>
<div class="gmail_quote">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>On 05/02/2015 14:14, <a moz-do-not-send="true"
href="mailto:teoteoteoteo@virgilio.it"
target="_blank">teoteoteoteo@virgilio.it</a>
wrote:<br>
</div>
<blockquote type="cite"><span><span>I'm writing to
you to explain why the task '</span></span><span><span>Add
an item in config:about to stop autoplay of
videos inserted by <video> tag' should
be priorer than other Mozillian activities (I
know it is not absolutely right, but I think
that a problem feeled since 3 years ago should
be priorer than others)!<br>
<br>
1. First of all we can say that almost all
sites are starting to insert HTML5
advertisement videos in their pages that start
as soon as the page is opened.<br>
</span></span></blockquote>
</div>
<div bgcolor="#FFFFFF" text="#000000"> "Almost all
sites" is clearly an overstatement. But this in
particular is something where data would be really
useful. How many sites (not in your personal
experience, but compared with something like the
Alexa top N sites, etc.) do this? Do they use the
autoplay attribute, and/or how many use JS instead
and trigger .play() themselves ? Can we get data
from advertising networks on how many of these types
of video ads they run and what the trends there are?</div>
</blockquote>
<div><br>
</div>
</div>
</div>
<div dir="ltr">
<div class="gmail_quote">
<div>Forgive me Gijs, but that would not help answer the
question "Are we doing the right thing?" <br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
Nobody is denying that we're not doing the perfect thing here. Just
like all kinds of other UX problems (e.g.:
<a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/showdependencytree.cgi?id=561125&hide_resolved=1">https://bugzilla.mozilla.org/showdependencytree.cgi?id=561125&hide_resolved=1</a>
). It doesn't help to belabour the "but it's a really serious UX
issue" point.<br>
<br>
I could spend all year, and probably longer, trying to fix every
issue in the list I just linked to, and I probably wouldn't manage.
Even if all the current active contributors worked on that list
together and gave up everything else we're doing, we wouldn't have a
"perfect UX Firefox" at the end of the year. And on top of that,
we'd be neglecting all kinds of other important things (like
performance, like important new features that we should be adding to
stay competitive, like code bitrot, like visual design issues, like
UX issues that aren't even in that dep tree, and the list goes on).<br>
<br>
The debate is about prioritizing it over other issues, of which
there are legion. Prioritization is essential, and that's what I'm
asking about. You can't just throw cost/benefit analysis out of the
window by shouting about how important you think the benefit part
is.<br>
<br>
~ Gijs<br>
</body>
</html>