Observe what survives the dark screen
When a screen goes dark during viewing, the word freeze may hide several different events. The display might dim while sound continues. The device might lock or sleep. The player might stop advancing while the operating system remains awake. The next useful action is to identify which of these happened, because each points to a different part of the setup.
Before changing settings, note whether audio continues, whether the pointer or remote wakes the display, and whether the playback position has advanced when the picture returns. Do not repeatedly press play during this observation: that can turn a paused screen into a running one and erase the evidence. If you are unsure, make one short repeat with a nonessential authorised sample.
Use a hypothetical timeline
Imagine a laptop showing a ten-minute sample. At minute three the display dims; sound continues; touching the trackpad restores the same ongoing scene at minute four. That supports a display-management observation. It is different from a player still showing minute three after the display wakes. Neither observation alone identifies why the setting or application behaved that way.
A useful log has four entries: when the screen changed, whether sound persisted, what action restored the display, and the position afterward. Include whether the page remained visible or was switched to a background tab. These details are more useful than a speed-test result when the symptom is tied to inactivity rather than busy scenes or network load.
Understand the limit of a wake lock
The web Screen Wake Lock API allows a supported, secure page to request that its screen remain awake. Availability and the active document's state matter. It is not a promise that every site uses the API or that every device will keep running through lid closure, operating-system sleep or a battery condition. A site can also lose a previously granted wake lock.
Use the device's normal display and power controls when an inactivity setting is the actual obstacle. Choose a setting appropriate to the session, then restore your preferred everyday behaviour afterward. Avoid installing an unknown keep-awake utility merely because a video page did not prevent dimming. First establish whether the browser and device already provide the required control.
Escalate the correct symptom
If the device locks despite active viewing, provide the platform version, browser and approximate inactivity interval to the relevant support route. If the display stays awake but the timeline stops, return to playback diagnosis and record the player state. If sound continues after the picture disappears, include the output path and whether the display itself reports sleep or loss of input.
After a change, repeat a short session under the same conditions. A successful repeat establishes that the particular symptom did not recur during that observation. It does not establish uninterrupted service for all future sessions. Keep the conclusion at the scale of the evidence: one display setting changed, one repeat completed, and the observed behaviour differed.
Questions answered
Does a dark screen always mean buffering?
No. Display dimming, locking, device sleep and a stopped media timeline can look similar. Sound and the position after waking help distinguish them.
Can a website prevent my laptop sleeping with the lid shut?
Do not assume that. A screen wake lock is a limited browser facility; system sleep and lid behaviour are separate device controls.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.