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

Issue 590872 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocking:
issue 822873
issue 568869



Sign in to add a comment

Move LayerImpl::position_ to LayerImplTestProperties

Project Member Reported by jaydasika@chromium.org, Feb 29 2016

Issue description

SetPosition implicitly uses layer tree hierarchy as position is position with respect to parent. One possible solution here is to replace SetPosition with SetOffsetToTransformParent.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Mar 1 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by ajuma@chromium.org, Mar 1 2017

Status: Available (was: Untriaged)
Summary: Move LayerImpl::position_ to LayerImplTestProperties (was: Remove layer SetPosition calls from impl unit tests )
There's a single call to LayerImpl::position in non-test code (used to get the root layer's position). Once we remove that, |position| can be moved to LayerImplTestProperties.
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 16 2018

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by ajuma@chromium.org, Apr 16 2018

Blocking: 822873

Comment 5 by ajuma@chromium.org, Apr 16 2018

Status: Available (was: Untriaged)

Sign in to add a comment