Skip to content

app: say why add-ons are off, where people see it #1851

Open

Description

@fujibee

What happens

At startup the app checks that this system's web engine really isolates add-on panes. When the check does not pass (a timeout, an exception, a missing result, WebRTC still present, a navigation that was not refused), every add-on pane is turned off.

Where the reason shows today:

  • Tab bar + menu: File view, Diff view and installed add-on panes are greyed out. The reason is only in the hover tooltip, so most people see disabled items with no explanation.
  • Settings > Add-ons: shows "Add-ons are not available on this computer yet. A safety check did not pass with this system's web engine." followed by "Reason: ...". The reason is the gate's internal English text (for example "the probe frame did not run"), the same in every language.

Expected

When add-ons are off, the app says so where people meet it, with a reason they can act on:

  • The + menu shows a visible line under the greyed items, not only a tooltip: add-ons are off, a short reason, and a pointer to Settings > Add-ons.
  • The reason is written for users and localized. Each gate reason maps to one user-facing sentence, and the technical text stays available (for example in a details line or the log) for bug reports.

Options

  • Settings > Add-ons already has "Check again" for failures and timeouts. Whether the + menu line offers the same button is open; it is not required by this issue.

Scope

App only. The check and its rules stay as they are: this changes only what is shown when it does not pass.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions