New issue
Advanced search Search tips

Issue 761956 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Feature



Sign in to add a comment

suppress fullscreen warning

Reported by software...@gmail.com, Sep 5 2017

Issue description

UserAgent: Copyright is nonsense

Steps to reproduce the problem:
1. Go to any website
2. Enter fullscreen mode
3. Observe the annoying message

What is the expected behavior?
There should be an option to disable the message

What went wrong?
I realize that Chrome developers doesn't want the message to be suppressed by an easy way, because they think it may harm users by malicious websites. However, I'm a developer and I find your "Press F11 to exit full screen" message extremelly annoying and disturbing. There should be a way to disable it. No matter how hard it would be, the way must exist.

Not sure if this is going to be closed as WontFix (probably), but I will ask you, before you close this issue, to explain how to disable the message? I've already disabled Chrome's updates (I literally deleted all executable files which whose task was to update Chrome) and now I can modify any Chrome's executable binary files.

So, pleas etell me (before you close this issue), where and in which executable is the assembly procedure which causes the message? I spent more than a week analyzing Chrome's executable files and dll's, but I couldn't figure it out. My goal is to modify Chrome's exe file in order to completelly remove the message (because you obviously don't want to provide easier way to achieve it).

It would be great if someone from your team briefly explain where and in which file is the assembly code which displays the message. Once I succeed to disable it, I can help a lot of other users which asked the same questions: "how to disable the fullscreen warning in chrome". However, every answer I saw  is telling that "it is impossible, Google didn't provide a way to do so".

However, I would really really do anything in order to disable the message. So please, I know this will be closed as WontFix, but before you close it, please let someone from your team (who actually know the answer) to explain here in comments what exactly is causing the message to be displayed (which executable file/ dll file, and which section of the file?). Please don't close the question before someone from your team explain it briefly.

I need to successfully disable the message and completelly get rid of it. Because, you know, it is extremelly annoying and disturbing, I feel like a retard when I see Chrome explaining me that I need to press f11 to exit full screen. How isulting is that? It really insults developers.

So, just to remind and summarize again everything I said, please let someone from your team explain where and in which binary file is the assembly procedure which displays the warning, so I can disable it. Thank you in advance.

Please, don't close this question before someone explain it. Thanks.
P.S. Sorry for bed inglish, I'm not from usa.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 60.0.3112.113  Channel: stable
OS Version: 6.3
Flash Version: I don't see what the heck flash has to do with my issue
 
Labels: M-63 ET-Triage Needs-Triage-M60 OS-Linux
Status: Untriaged (was: Unconfirmed)
@Reporter: Considering the above issue as feature ,Hence marking it as untriaged

Note: Press F11 to exit full screen message is not seen on Mac OS

Comment 2 by e...@chromium.org, Sep 6 2017

Components: -Blink>Fullscreen UI>Browser>FullScreen
Labels: -Type-Bug -Hotlist-Interop -Via-Wizard-API -M-63 -Needs-Triage-M60 -ET-Triage Type-Feature
This is a UX requests, Over the the browser UI team.
Exit full screen (F11) this is a problem on
touch screen display  
20171213_231357.jpg
1.1 MB View Download
Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment