ampproject / ampproject/amphtml

[amp-consent] Chrome 103+ on android breaks amp consent rendering on refresh

Open
#38,370 2 comments 0 reactions 0 assignees View on GitHub
Component: amp-consent P3: When Possible Stale Type: Bug WG: components
Dominant language
JavaScript
Stars
14.9k
Forks
4.1k
PR merge metrics
No merged PRs in 30d

Description

### Description

Using an android phone and using chrome(103)
Go to test page https://achspcmptest.000webhostapp.com/xamp.html where consent message is set to always show

expected: consent message shows up on initial page load. without making any actions and refreshing the page, the consent message to show up again.

Current behavior: Consent message shows up on initial page load. Without making any actions and refreshing the page, the message doesnt show up, and only results in a grey overlay.

https://www.loom.com/share/26b18a9d1b874fc08c1c5e9e6a60288d

### Reproduction Steps

Use android mobile phone, with latest version of chrome 103, and go to this test page:
https://achspcmptest.000webhostapp.com/xamp.html

refresh the page without making any actions, and the overlay is there, but the message doesnt show up.

so it looks like some rendering issue with this version of chrome on android device.
'Mozilla/5.0 (Linux; Android 12; SM-G781V) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Mobile Safari/537.36'

Device information: Samsung Galaxy 20, but has been reproduced on other devices.

This doesnt happen to firefox on android, and chrome/safari/firefox on ios and desktop work fine.

### Relevant Logs

```shell
no console errors.
```

### Browser(s) Affected

Chrome

### OS(s) Affected

android 12

### Device(s) Affected

samsung galaxy 20

### AMP Version Affected

2207071723000

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue at the provided test page on Chrome 103+ for Android, refreshing without taking action, and compare the result with the listed unaffected browsers. Investigate the amp-consent rendering path for the refresh case; done means the consent message appears again instead of leaving only a grey overlay, without regressions on the other reported platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.