Problem
When navigating between default view and CPC view, the purpose settings will reset to advanced_settings_purposes_default from configuration, effectively reverting any user feedback. This may result in users experiencing unresponsive settings, where input does not propagate properly into the desired sections, which can potentially impact the end user's feeling of trust.
Solution
Add a state-like, mutatable array, which will hold user input temporarily, while navigating between screens and store intended consent settings, regardless of on which screen the final consent is given.
Changes
Added getPendingPurposes, setPendingPurposes, addPendingPurpose, removePendingPurpose and setPendingPurpose utility functions
Implemented utility functions into privacy settings methods
Implemented utility functions into CPC views
Added unit tests for core_pending_purposes
Added test for CPC rendering with pending purposes
side effect: update package-lock from package
Examples
Changes in this PR will propagate into all demos.
A production version is implemented on https://tv2.dk
Related issue: https://github.com/as-ideas/oil/issues/256
Problem When navigating between default view and CPC view, the purpose settings will reset to
advanced_settings_purposes_default
from configuration, effectively reverting any user feedback. This may result in users experiencing unresponsive settings, where input does not propagate properly into the desired sections, which can potentially impact the end user's feeling of trust.Solution Add a state-like, mutatable array, which will hold user input temporarily, while navigating between screens and store intended consent settings, regardless of on which screen the final consent is given.
Changes
getPendingPurposes
,setPendingPurposes
,addPendingPurpose
,removePendingPurpose
andsetPendingPurpose
utility functionsExamples Changes in this PR will propagate into all demos. A production version is implemented on https://tv2.dk