Access and help

Describe an audio issue clearly for support

A useful issue report identifies initial state, action and result. Prepare it locally and decide yourself whether to share it.

Collect the necessary details

Record browser name and version, extension version, normal or restricted page and the exact notice. State whether original audio works with Power off. A play/pause problem needs different details from missing or distorted sound.

If sharing a screenshot, remove private tab titles and visible account data. Passwords, session tokens and browser linking credentials are not required for an audio issue report.

Find the smallest reproducible procedure

  1. Check original audio on a normal website.
  2. Deliberately start the channel in the active tab.
  3. Make exactly one change and note the actual result.
  4. Use another normal source to identify whether the issue is website-specific.

Separate expected and actual results

For example, describe “no sound at 100 percent, audible with Power off” instead of “does not work”. Add timestamp and channel state. This checklist only copies your report; it sends no message and records no audio.

Review the report yourself before sharing

Read the report as someone who cannot see your browser windows. Can they identify the active source, command used and whether original playback worked? Add missing steps but not a guessed technical cause. Mention a successful comparison on another website. If you cannot share the source, describe the player and exact notice without confidential URL or content.

A useful attachment shows only relevant status or error. Review tab titles, email, account state and visible content before sharing. A neutral source is useful if it reproduces the same issue. Copying this template does not create a support case; you choose the recipient and content. Keep the reviewed report with its date to trace later changes.

A worked example

One website fails while another works. Record both results and name whether audio or only playback control is affected. This small comparison prevents a protected specialised player being described as a general extension failure. If the URL is private, state only the page type and describe its setup without access credentials.

Add your observations. This template processes no files and sends no report.

Check the result

If something is wrong

Observation and next step
ObservationNext step
Issue cannot be reproducedRecord timestamp, source and individual action more precisely.
Screenshot contains account detailsRemove private regions and share only the relevant notice.
Only “does not work”Add expected result, actual result and comparison test.

Common questions

Does the template send a report?

No. It is locally copyable text for your own review and sharing.

Should I include a key?

No. Describe status and notices without passwords, keys or tokens.