Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Launching browser in maximised position causes a 1px gap between browser window and the taskbar #8784

Closed
srirambv opened this issue May 10, 2017 · 6 comments
Labels
bug fixed-with-brave-core This issue will automatically resolved with the replacement of Muon with Brave Core. upstream wontfix

Comments

@srirambv
Copy link
Collaborator

  • Did you search for similar issues before submitting this one?
    Yes

  • Describe the issue you encountered:
    Launching browser in maximised position causes a 1px gap between browser window and the taskbar

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    Windows 10 x64

  • Brave Version (revision SHA):
    Brave 0.15.2
    rev af7ef42

  • Steps to reproduce:

    1. Set browser to maximised position
    2. Close and relaunch the browser
    3. Browser launches in maximised position but is actually in restore position
    4. There is a 1px gap between browser window and taskbar
    5. CLick on maximise button, fits the browser window correctly on top of the taskbar
  • Actual result:
    Launching browser in maximised position causes a 1px gap between browser window and the taskbar

  • Expected result:
    Should launch in a maximised state and should properly fit on screen above the task bar

  • 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?
    No

  • Can this issue be consistently reproduced?
    Yes

  • Extra QA steps:
    1.
    2.
    3.

  • Screenshot if needed:

  • Any related issues:
    Maximizing window puts the bottom 1px of window behind the taskbar #7215
    Marking it as 0.15.400. Feel free to pull it back in to 0.15.300 if required

@srirambv srirambv added this to the 0.15.400 milestone May 10, 2017
@bsclifton bsclifton removed their assignment May 23, 2017
@bsclifton bsclifton removed this from the 0.16.100 milestone May 23, 2017
@srirambv
Copy link
Collaborator Author

@bsclifton bsclifton added upstream and removed bug labels Jun 2, 2017
@bsclifton
Copy link
Member

This is upstream from us (Chromium). More info here:
electron/electron#8332

@Struisvogel93
Copy link

I got the exact same issue, specs here:

Brave: 0.18.23
rev: 36ae2ec
Muon: 4.3.10
libchromiumcontent: 60.0.3112.90
V8: 6.0.286.52
Node.js: 7.9.0
Update Channel: dev
OS Platform: Microsoft Windows
OS Release: 10.0.15063
OS Architecture: x64

@luixxiul luixxiul added the bug label Aug 29, 2017
@Struisvogel93
Copy link

If I could fix this myself, I would've done it (unskilled in any form of programming). But can someone please look at this? I love the Brave Browser, but this is my Nr. 1 annoyance with Brave, has been for months lol :)

@NejcZdovc
Copy link
Contributor

@Struisvogel93 there are some fixes in 0.20 version for maximize/fullscreen, so please check out 0.20.x when it will be in the beta channel

@Struisvogel93
Copy link

@NejcZdovc Thanks for your response, I will, as soon as it hits :)

@bsclifton bsclifton added this to the Triage Backlog milestone Nov 27, 2017
@bsclifton bsclifton added wontfix fixed-with-brave-core This issue will automatically resolved with the replacement of Muon with Brave Core. labels Aug 30, 2018
@bsclifton bsclifton removed this from the Triage Backlog milestone Aug 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed-with-brave-core This issue will automatically resolved with the replacement of Muon with Brave Core. upstream wontfix
Projects
None yet
Development

No branches or pull requests

5 participants