On 8/6/18 4:03 PM, Jan-Ivar Bruaroey wrote:
On 8/1/18 3:36 AM, Chris Pearce wrote:
I think the only thing that you're missing is how vehemently some
sites are in their desire to avoid the doorhanger prompt.
No, I'm also missing why we should listen to them.
If Netflix fights our doorhanger, then they're fighting our best attempt
to whitelist them.
To clarify, I care about Netflix, which is why I question giving up on
persisting autoplay for them, which is what allowedToPlay does.
AFAICT allowedToPlay's sole purpose is to avoid our doorhanger.
I've heard two reasons to fear our doorhanger:
1. Sites doesn't want to get blocked.
This seems bogus, because "getting blocked" appears no different from
avoiding the prompt with allowedToPlay. Both prevent the prompt.
Try it yourself: https://jsfiddle.net/jib1/rwkLaofx/show
Press "Don't Allow", then click anywhere on the page to play.
In other words, users aren't blocking audio, only un-gestured audio,
which shouldn't matter to sites who already avoid it with allowedToPlay.
Also, allowedToPlay will never suddenly return true if used to suppress
the prompt, because we have no other whitelisting strategy.
2. User testing shows many users don't understand the prompt.
This one makes sense to me. If avoiding our one-time prompt matters more
to them than autoplay itself, it's a sign our prompt isn't great. We
should fix that, not help sites opt out.
Here's my take on our prompt:
I love that we went with a visible user agent feature instead of
breaking the web. Even the permission part, partly. The management part.
But the prompt itself is too complicated. It's hard to glean how little
is at stake: delaying audio by a mere click in many cases.
Try the fiddle again, ignore the prompt and just click somewhere on the
page. Tone.
I think we need to rephrase this as a helpful user agent:
_/\_________________
| |
| Wanna hear sound ? |
| |
| No | Yes |
`--------------------'
or
_/\_______________
| |
| Sound blocked. |
| |
| Don't | Thanks |
`------------------'
Then have the user agent set the permission wisely.
By putting the agent in charge, we might even get away with a path to
whitelisting without a prompt, where the user agent implicitly turns the
permission on for well-behaved sites after users have interacted
sufficiently with gesture-driven audio, without signs of distress.
This seems similar to Google's engagement system, except it's visible,
so users can override the agent should it get it wrong, since it's still
permission-based at heart.
Then allowedToPlay might make sense.
Thoughts?
.: Jan-Ivar :.
cpearce.
.: Jan-Ivar :.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
