A website's saved camera permission does not replace Android's permission for the Chrome app. When investigating a blocked request, identify both records before deciding that the camera is faulty. You can inspect them without granting access.
Check both permission layers
Google documents Chrome Settings, Site settings, then Camera or Microphone, together with Android app permissions. Device-level denial can block Chrome. Some managed settings are controlled by an administrator; menus vary by release and device. Google's documented controls.
Document a fictional mismatch
Imagine a demonstration website was allowed to use the camera in Chrome, but Android's Camera permission for Chrome says Don't allow. Write two rows: website permission in Chrome, allowed; Chrome app permission in Android, denied. These describe different layers, not a setting that somehow says yes and no at once.
The website's saved choice cannot overcome the app-level denial. This explains a permission obstacle, but does not establish whether every other requirement for the feature works. Do not mark the hardware broken merely because this configuration prevents the page from opening it.
To report the situation, name the website associated with the browser entry and the app associated with the Android entry. Checking a separately installed game app would not answer the second question about Chrome. If the app name is cropped out of a screenshot, confirm it before attaching that screenshot as evidence.
Keep the decision separate from diagnosis
After identifying the mismatch, decide whether you want to use the camera feature at all. Leaving access denied and closing the page is a valid choice. Do not grant access to every website just to make one warning disappear. This article diagnoses the two settings; it is not a recommendation to relax them.
If a control is managed, document that restriction rather than trying to bypass it. If both recorded permissions allow access but the feature still fails, the original permission mismatch no longer explains the whole problem. Preserve the new observations instead of repeating the same fix or claiming that access is guaranteed.
For a separate reading task, see our guide to checking unclear game-screen information; it is not the source for Android controls.