New issue
Advanced search Search tips

Issue 695473 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

windows 7: some windows have a black titlebar when using a basic theme

Reported by huglovef...@gmail.com, Feb 23 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3018.3 Safari/537.36

Steps to reproduce the problem:
1. right click the desktop and select "personalize", then select a theme under "basic and high contrast themes" (not available on windows 8 and newer)
2a. open chrome's dev tools, select "undock into new separate window" under menu > dock side
2b. or: click the first link on http://www.popuptest.com/goodpopups.html

What is the expected behavior?
the titlebar should be gray with the rest of the UI

What went wrong?
it's black

Did this work before? Yes 57.0.2987.74 beta

Chrome version: 58.0.3018.3  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 25.0 r0

 
stable.png
240 KB View Download
beta.png
255 KB View Download
dev.png
248 KB View Download
canary.png
232 KB View Download
Labels: -Pri-2 hasbisect-per-revision M-58 Pri-1
Owner: thomasanderson@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on windows-7 using chrome canary 58.0.3025.0

This is regression issue broken in M58. Please find the bisect information as below

Narrow Bisect::
===============
Good :58.0.2991.0 --   (build revision 445609)
Bad:: 58.0.2992.0 --   (build revision 445908)

ChangeLog: 
================
https://chromium.googlesource.com/chromium/src/+log/86f05da3c1fe8ca3d242e96c8717dcdb69950f6c..2bbf4303d8af1e49e748bb2d7e131d114daa7354

Review-Url: https://codereview.chromium.org/2628043002

thomasanderson@ could you please look into this issue if it is related to your change,else please help us in finding the appropriate owner for this issue.

Thanks,
Cc: pkasting@chromium.org
Status: Started (was: Assigned)
I believe this is related to the GetTopAreaHeight change here:
https://codereview.chromium.org/2628043002/diff/160001/chrome/browser/ui/views/frame/opaque_browser_frame_view.cc

+pkasting, I guess we could just do this?

    const int kHeight = 64;
    if (browser_view()->IsTabStripVisible()) {
      return GetBoundsForTabStrip(browser_view()->tabstrip()).bottom();
    } else {
      return frame_image.isNull() ? kHeight : frame_image.height();
    }

I'd really like to avoid doing that if possible...

Can you first check why returning a 0 in this case causes a black frame here?  Maybe the right fix isn't in GetTopAreaHeight() itself, but in more correctly handling a 0 return from it at some place in the call chain.
Status: Available (was: Started)
I can't repro this on my Win 10 machine.  pkasting@ is there anyone with a Win7 machine that can debug this?
I have one in my office.  I'm not in there until next week, so you'd be welcome to use it.  Dunno if it's easy to let you log in to my machine, though?

Comment 6 by bsep@chromium.org, Mar 8 2017

Cc: bsep@chromium.org
You can get that frame on Windows 10 by launching with --disable-dwm-composition, I just tested and it reproduces. I can dig into it more if you'd like.
Cc: thomasanderson@chromium.org
Owner: bsep@chromium.org
Status: Assigned (was: Available)
Thanks bsep@, assigning to you for now
Project Member

Comment 8 by bugdroid1@chromium.org, Mar 9 2017

Comment 9 by bsep@chromium.org, Mar 9 2017

Status: Fixed (was: Assigned)
 Issue 718886  has been merged into this issue.
This issue is still seen in the latest stable #58.0.3029.96.

bsep@ - Could you please merge the fix to M-58.

Thanks...!!
Labels: Merge-Request-58
Status: Assigned (was: Fixed)
Reopening as per c#11
Cc: gov...@chromium.org
Labels: -Merge-Request-58
Status: Fixed (was: Assigned)
Re-closing this issue.

Discussed this with govind@ offline and this bug does not warrant a merge to M58.
Cc: marcore@google.com
 Issue 727328  has been merged into this issue.

Sign in to add a comment