New issue
Advanced search Search tips

Issue 873931 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Plumb RendererPreferences once per-process

Project Member Reported by dcheng@chromium.org, Aug 14

Issue description

Right now, it looks like we send an IPC for each view and each worker for RendererPreferences updates. This is a bit odd, since RendererPreferences should be process-global.

The tricky part is that workers don't live on the main thread, so the replication is probably going to be a bit tricky. But at the least, we can use in-process observer lists for any replication needed within the process.
 
Thanks for filing this :)
Per-process model sounds reasonable to me. 

I'd like to change the architecture once after we make updating of RendererPreferences work, in order not to block 853085.
Status: Untriaged (was: Available)
Available, but no owner or component? Please find a component, as no one will ever find this without one.

Sign in to add a comment