I have encountered a bug where changing the Compositor plugin resolution using the web UI would not work for e.g. changing to resolution "720p50Hz".
I found the reason for this is the compositor resolution strings listed in the dropdown menu in the web UI still use the "Hz" suffix. However, the compositor resolutions (specifically the enum to string conversion) defined in Thunder Interfaces (Definitions.cpp) had the "Hz" suffix removed in rdkcentral/ThunderInterfaces@9d15587
To fix this bug, I removed the "Hz" prefix from Compositor resolutions in ThunderUI sources: dist/bundle.js and src/js/plugins/compositor.js.