Issue 688573 link

Starred by 1 user

Status:	WontFix
Owner:	kylec...@chromium.org
Closed:	Jun 2017
Cc:	danakj@chromium.org weiliangc@chromium.org █ fsam...@chromium.org varkha@chromium.org mustash-bugs@google.com
Components:	Internals>Compositing Internals>Services>WindowService
EstimatedDays:	----
NextAction:	----
OS:	----
Pri:	3
Type:	Feature
displaycompositor

exo::Surface should not use DirectSurfaceReferenceFactory

Project Member Reported by samans@chromium.org, Feb 3 2017

As long as exo::Surface uses DirectSurfaceReferenceFactory, we can't move it to a different process from where SurfaceManager resides.

Cc: danakj@chromium.org fsam...@chromium.org
Owner: samans@chromium.org

Blocking: 601863
Components: Internals>MUS Internals>Compositing
Labels: displaycompositor
Status: Assigned (was: Untriaged)

Owner: kylec...@chromium.org

This is likely blocked on surface references being used everywhere so I'm reassigning to kylechar@.

Labels: Type-Feature

Cc: weiliangc@chromium.org

Cc: varkha@chromium.org

Status: WontFix (was: Assigned)

I'm marking this as WONTFIX as we are actively working on surface references now.

Blocking: -601863

Components: -Internals>MUS Internals>Services>WindowService

►