
Some visual properties are for the page, and some are for the widget. Right now, all are propagated by WidgetMsg_SynchronizeVisualProperties. This is incorrect since it's possible for a renderer to have a page but not a widget. This CL begins the process of fixing this incorrect routing. It adds a new IPC message ViewMsg_UpdateLocalMainFrameVisualProperties, which allows us to begin routing visual property messages through the Page object. This CL should not have any behavior changes. Bug: 998273 Change-Id: I4f4b46f8bd51e2d64b652db6aa1df6e6c3b076a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1788201 Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Auto-Submit: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#694936}
14 lines
480 B
C
14 lines
480 B
C
// Copyright 2019 The Chromium Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
#ifndef CONTENT_COMMON_COMMON_PARAM_TRAITS_H_
|
|
#define CONTENT_COMMON_COMMON_PARAM_TRAITS_H_
|
|
|
|
// This file provides declarations of IPC serialization macros that are used
|
|
// in more than one IPC message file.
|
|
|
|
#include "content/common/common_param_traits_macros.h"
|
|
|
|
#endif // CONTENT_COMMON_COMMON_PARAM_TRAITS_H_
|