cookie consent popup disappears and defaults to allow when navigating directly to a control sample page

[DetachHead]

What is the issue and how can we reproduce it?

1. open a chrome incognito window
2. Open the sample https://sdk.openui5.org/#/entity/sap.m.Input/sample/sap.m.sample.InputValueState
3. wait for the page to load
4. ... --> Issue: ...

actual behavior

the page seems to reload and the popup disappears

ui5.cookie.popup.mp4

then the cmapi_cookie_privacy cookie is added with the value permit_1|2_functional which i assume means i've accepted functional cookies, which i did not want to do

Expected behavior:

dookie popup doesn't disappear

Which OpenUI5 version is your project targeting?

N/A

Is the issue device- or browser-specific?

tested on chrome and firefox, only happens on chrome

Confirmation

• I have searched the existing issues and reviewed the relevant documentation as well as the API reference.
• I am not disclosing any internal or sensitive information.

[boghyon]

I was able to reproduce the issue only with the network location around the US area. In other locations, the banner has different options and the automatic reload does not seem to happen. Not sure to which extend Demo Kit has control over the banner.

[50gY]

Hello @DetachHead,
Thank you for sharing this finding. I've created an internal incident DINC0715037. The status of the issue will be updated here in GitHub.

[venkatamandavilli-code]

@DetachHead

Thanks for reporting this issue.

This appears to be more than a visual problem because it affects how user consent is handled.

From a user perspective, cookie preferences should only be stored after an explicit action has been taken. If the consent dialog disappears and a consent cookie is automatically created, users may believe that preferences were recorded without their approval.

In enterprise environments, cookie consent behavior is often subject to privacy, compliance, and governance requirements. Consistent handling of consent decisions is important not only for user trust but also for ensuring that applications behave as expected across browsers and navigation paths.

The fact that the issue occurs when navigating directly to a sample page suggests there may be an initialization or routing sequence that bypasses the normal consent flow. Investigating that interaction could help identify why the consent state is being established before the user has made a choice.

Thank you for investigating and working on this issue.