New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 867981 link

Starred by 1 user
Status: Assigned
Owner:
malaykeshav@chromium.org
Cc:
dchan@chromium.org
malaykeshav@chromium.org
dhadd...@chromium.org
osh...@chromium.org
spang@chromium.org
█ patricia@chromium.org
kylixrd@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Write unit test(s) for broken UI(compositor) as crbug.com/866010 - UI elements scaled size should match match the physical pixel size of the display

Project Member Reported by ka...@chromium.org, Jul 26 
 Issue 866010  was a P0 RBD issue, and no test caught it in advance.

It is essential for the UX, and product quality  to set tests at different level - unit tests, browsertest, bvt autotest - to be able to stop such regression at earliest possible time.

Comment 1 by ka...@chromium.org, Jul 31

Summary: Write unit test(s) for broken UI(compositor) as crbug.com/866010 - UI elements scaled size should match match the physical pixel size of the display (was: Write tests for broken UI(compositor) as crbug.com/866010)
Per email conversation I am setting this bug to track implementing unit test for the particular  issue 866010 .

Comment 2 by spang@chromium.org, Aug 2

Owner: malaykeshav@chromium.org
I suppose unit tests for that would just check that compositor has the same pixel size of PlatformWindow::GetBounds().size() at several resolutions and scales.

Comment 3 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment