Development that use cross-site resources may encounter issues when Chrome version 80 is released in the month of February 2020.
Development that use cross-site resources may encounter issues when Chrome version 80 is released in the month of February 2020. An example of when issue may occur is when using "domReady". (https://www.cdnpkg.com/require-domReady)
The following may be registered in the Google Chrome Development Tools:
R&D is currently working on a solution, and updates regarding this will be posted here once this information becomes available.
For now, the SameSite security feature is not being enforced by default. If you are using Chrome versions 79 and below, the default setting for SameSite is "default", which is equivalent to "disabled". You can check it here chrome://flags/#same-site-by-default-cookies. In Chrome versions 80 and newer, "default" will be equivalent to "enabled", which enforces this security setting and will require an update to Qlik Sense and QlikView to prevent requests from being blocked. Until an update is provided, a temporarily workaround would be to change the SameSite setting to "disabled".
Edit the domain policy for where a list of specific domains are allowed for the legacy SameSite behavior to be used. See Cookie Legacy SameSite Policies.
Qlik will have official patches and service releases for both Qlik Sense and QlikView available on the Wednesday's, Feb 12th 2020 delivery.
Licensee patches will be available on demand for Qlik Sense as of Feb 3rd 2020, please contact Qlik Support.