Aglet

Verify notification permission timing and denial recovery

Verification should prove that notification permission is requested in a clear context and that decline does not strand the person. Test the prompt trigger, rationale, all visible outcomes, and later settings. Keep platform-specific behavior outside the claim when it cannot be observed.

Check whether the outcome improved

  1. Check the contextual trigger

    Reach the feature or user action that benefits from notifications and confirm rationale, timing, and request. Record that the prompt follows a meaningful choice rather than page load. Ensure the underlying feature remains understandable.

  2. Check outcomes

    Allow, deny, and dismiss the prompt where supported. Confirm resulting app state, copy, fallback, and absence or presence of later prompt match the contract. Keep a direct settings path available if the person changes their mind.

  3. Review persistence and layout

    Revisit the feature, settings, narrow layout, focus, and status after each result. State tested platforms and permission states. Leave a partial pass where system prompt behavior or external delivery cannot be directly verified.

What to carry forward

Verification passes when the prompt follows a clear user action, outcomes are explained, and denial leaves a useful recovery path. If platform or later settings behavior is partial, document it. A prompt that appears eventually is not a pass if its context is unclear.

Technical background: Chrome developer documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow