Browser-laptop: Mouse cursor visible while in full screen

[Jacalz]

Test plan

1. Open a youtube video (Example: https://www.youtube.com/watch?v=ylTPgMi9SEo )
2. Open fullscreen
3. Mouve the mouse so it isn´t on the bar at the bottom
4. Keep the mouse stationary

---

• Did you search for similar issues before submitting this one?
  Yes
• Describe the issue you encountered:
  Mouse is still visable after entering fullscreen in youtube...
• Platform (Win7, 8, 10? macOS? Linux distro?):
  Windows 10Pro x64
• Brave Version (revision SHA):
  0.13.5 but also found it working on 1.14.0 RC2

• Steps to reproduce:

  1. Open a youtube video (Example: https://www.youtube.com/watch?v=ylTPgMi9SEo )
  2. Open fullscreen
  3. Mouve the mouse so it isn´t on the bar at the bottom
  4. Keep the mouse stationary

• Actual result:
  Mouse is still visable

• Expected result:
  Mouse should be hidden when not moving it
• Will the steps above reproduce in a fresh profile? If not what other info can be added?
  Yes
• Is this an issue in the currently released version?
  Yes
• Can this issue be consistently reproduced?
  Yes

[jonathansampson]

Thank you for filing!

Browser | Behavior
-|-
Chrome | Hides mouse
Firefox | Hides mouse
Edge | Hides mouse
Brave (electron/muon) | Displays mouse
Slack (electron) | Displays mouse

[bsclifton]

Moving to 0.14.3

[alexwykoff]

Hey @srirambv if you can reproduce please let us know, thanks :)

[srirambv]

Confirmed cursor not hidden in full screen.

[alexwykoff]

@srirambv could you check vs slack fullscreen?

[srirambv]

Same on slack fullscreen as well. Cursor is not hidden.

[srirambv]

I think this is fixed in 0.15.3 preview 3. I do not see mouse pointer when viewing full screen video. But will keep the issue open just in case.

[Jacalz]

Yes it looks as to be fixed with 0.15.3, I wonder what fixed it :+1: :confused:

[Jacalz]

If we found what commit fixed it we can have it in the release notes in my oppinion :+1:

[jonathansampson]

@darkdh @bridiver Are either of you aware of a change that would have resolved this issue?

[bsclifton]

@Jacalz can you check if it still happens in 0.15.2? We did update Chromium in that release; perhaps it was fixed there (I don't believe we did anything to fix this, but I could be wrong)

[Jacalz]

Does not happen in 0.15.2 strange :confused: @bsclifton

[Jacalz]

Can somebody also confirm that it got fixed with 0.15.2 so we can close this? :smile:
If so I can not belive my eyes that a chromium update fixed it, would never even think as that being possible so great catch @bsclifton :+1:

[luixxiul]

I confirmed that, closing.

[bsclifton]

@Jacalz not too unbelievable- a Chromium update also introduced it 😄 Thanks for checking all

[Jacalz]

Oh, had no idea that it was introduced by a chromium update 😅 No problem 🤗

[Jacalz]

Also wich release notes should this be put on? Since @bsclifton removed the milestone 😅

[bsclifton]

@Jacalz we can keep a milestone if we want release notes. Sorry- I had removed it since there wasn't any fix

[Jacalz]

Don't be sorry it was more meant as a question if the release notes include tag should be removed or not 😉 @bsclifton

[luixxiul]

I had removed it since there wasn't any fix

I would say that the app fixed itself ;-)