Ensure Chromium features are propagated to child processes6.7

With the 118 update, the fallback code path that passed Chromium
feature flags via the command line was completely removed in favor
of a shared memory model. Correctly initializing this requires
having a FieldTrialList instance alive somewhere, but some fixups
when integrating 118 rendered that code path unreachable. As a result,
Chromium features were never getting sent to the render process,
and were only visible on the main WebEngine process.

This change adds a FieldTrialList instance inside WebEngineContext,
which allows the FeaturesList class to work correctly, and thus
correctly propagate features to the render process.

Change-Id: I6d07ea4a7c87db83e526ea62ca4d86526463ad1a
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
(cherry picked from commit 1e0c7155877a4cf81c6a3c5d26b02c939b0dd049)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 3fad66045a4482945d223916097b80fbc917b81b)

0 files changed, 0 insertions, 0 deletions