> On Aug 17, 2015, at 5:41 PM, Mike Hommey wrote:
>
> FWIW "Exit Full Screen (esc)" doesn't really sound like lambda users
> would understand as "press esc to exit full screen”.
The idea is that the primary way to exit full screen is to click the button
that says “Exit Full Screen.” The (Esc)
Thanks for the comparison Michael! That does look better, I do appreciate
that it's been downsized and doesn't require the additional user input
anymore. However since the notification is in the black letterbox, I can't
tell - is the message box fully opaque, or partially transparent?
On Mon, Aug
On Mon, Aug 17, 2015 at 10:02:38AM -0500, Michael Verdi wrote:
> Hi, Here’s a quick comparison of the various full screen notifications
> - https://youtu.be/K5S-WGDIvLI Our new interaction is much less
> onerous on the user - comparable to the flash full screen interaction.
> It even requires less
The new UI is much better - good work!
Gavin
On Mon, Aug 17, 2015 at 8:02 AM, Michael Verdi wrote:
> Hi,
> Here’s a quick comparison of the various full screen notifications -
> https://youtu.be/K5S-WGDIvLI
> Our new interaction is much less onerous on the user - comparable to the
> flash full
Hi,
Here’s a quick comparison of the various full screen notifications -
https://youtu.be/K5S-WGDIvLI
Our new interaction is much less onerous on the user - comparable to the flash
full screen interaction. It even requires less interaction than Chrome does.
Thanks,
Michael
--
Michael Verdi •
Ack. Chrome has a dedicated user research team for security UX.
Javaun Moradi | jmor...@mozilla.com | IRC: javaun | @javaun
> On Aug 17, 2015, at 11:00 AM, Javaun Moradi wrote:
>
> The desktop UX team, platform security and media/graphics teams worked
> together to find a good compromise tha
The desktop UX team, platform security and media/graphics teams worked together
to find a good compromise that balanced security with user experience. It was a
long conversation.
The Chrome browser has a similar 2-3 second fullscreen warning, even on Google
sites like Youtube. They have a dedi
First off, I have to say that I do like the new UI, regardless of the
impetus for the change.
However, I'm also not entirely sold that this has a strong impact on
user security. I doubt the practicality of such an attack, since you
would have to reasonably match:
* The OS native theme.
* The
I'm not making any statement as asinine as "there's no point worrying about
security", and it's frustrating that that's something I would even have to
clarify.
Richard stated he thought the current solution had a "small price" and I
disagreed with him.
This boils down to a classic security/usabil
On 17 August 2015 at 07:34, Nicholas Nethercote wrote:
> On Mon, Aug 17, 2015 at 5:15 AM, Richard Barnes wrote:
>>
>> But a 2-3 second box for each
>> fullscreen transition seems like a small price.
>
> The box is very prominent and often blocks part of the video, which I
> personally find quite
On Mon, Aug 17, 2015 at 5:15 AM, Richard Barnes wrote:
>
> But a 2-3 second box for each
> fullscreen transition seems like a small price.
The box is very prominent and often blocks part of the video, which I
personally find quite annoying.
If the notification were less prominent -- e.g. a strip
On Sun, Aug 16, 2015 at 8:07 PM, Eric Shepherd
wrote:
> I have to agree with Gavin here: the risk of this sort of attack occurring
> is very low,
>
Do you have some evidence for this?
-Ekr
> but the potential for annoying or confusing users with this presentation
> is, if not high, at least h
I have to agree with Gavin here: the risk of this sort of attack occurring is
very low, but the potential for annoying or confusing users with this
presentation is, if not high, at least high enough to make it overkill. At
least having a way (even if it's an about:config only thing) to drop this
On Sun, Aug 16, 2015 at 5:52 PM, Eric Rescorla wrote:
>
>
> On Sun, Aug 16, 2015 at 5:49 PM, Gavin Sharp wrote:
>
>> > But a 2-3 second box for each fullscreen transition seems like a
>> > small price.
>>
>> Seems like a pretty large price to me, given a combination of factors:
>> - significant
On Sun, Aug 16, 2015 at 5:49 PM, Gavin Sharp wrote:
> > But a 2-3 second box for each fullscreen transition seems like a
> > small price.
>
> Seems like a pretty large price to me, given a combination of factors:
> - significant added friction to a common user action ("start watching
> this video
> But a 2-3 second box for each fullscreen transition seems like a
> small price.
Seems like a pretty large price to me, given a combination of factors:
- significant added friction to a common user action ("start watching
this video in fullscreen")
- low likelihood that the type of attack this mi
This prompt is an important part of the security story for fullscreen.
Since a fullscreen web app can hijack your entire browsing session, it's
important that the user know that he's entering fullscreen and not looking
at an actual browser window -- and to know that every time something goes
fullsc
IIUC, the reminder is supposed to go away after a few seconds. However, I
have experienced the case, many times, where the reminder stays on screen
for the entire video. IIRC, if I restart the browser and replay the same
video again, then the reminder goes away.
HTH,
Brian
On Sat, Aug 15, 2015 at
Including dev-media and dev-security.
On Fri, Aug 14, 2015 at 11:53 PM, Eric Shepherd
wrote:
> Chris wrote:
>
> After quite a while of watching HTML 5 video content in fullscreen, I'm
> getting a bit tired of being reminded with a huge banner at the top that
> yes, I can still hit ESC to exit fu
19 matches
Mail list logo
