We have two prefs for dumping the compositor-side layer tree: `layers.dump` and `layers.dump-host-layers`. They have subtly different behaviours: * `layers.dump-host-layers` is a no-op in a non-`MOZ_DUMP_PAINTING` build (e.g. a default opt build) * `layers.dump` is a no-op for advanced layers, which seems to be the default, at least ofr local builds I can see an argument for keeping both (`layers.dump-host-layers` for symmetry with `layers.dump-client-layers`, `layers.dump` because a lot of people know and use that), but there's no reason they should have subtly different behaviour; we should make them exact synonyms. More specifically, they should both work in opt builds, and they should both work for advanced layers.
Bug 1558276 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We have two prefs for dumping the compositor-side layer tree: `layers.dump` and `layers.dump-host-layers`. They have subtly different behaviours: * `layers.dump-host-layers` is a no-op in a non-`MOZ_DUMP_PAINTING` build (e.g. a default opt build) * `layers.dump` is a no-op for advanced layers, which seems to be the default, at least for local builds I can see an argument for keeping both (`layers.dump-host-layers` for symmetry with `layers.dump-client-layers`, `layers.dump` because a lot of people know and use that), but there's no reason they should have subtly different behaviour; we should make them exact synonyms. More specifically, they should both work in opt builds, and they should both work for advanced layers.