Extensions can't run on file:// pages: no way to enable "Allow access to file URLs" (per-space setting is inconsistent)

Open
#975 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
swift
Domain
desktop

Research direction

Start by reading the extension management and per-space settings code to find where Yab stores extension preferences and exposes them in the UI; the issue does not name specific files or tests. Check how the existing newAllowFileAccess value is read and written. Done means users can enable file URL access for an extension in each space and the extension works on local file:// pages.

Written by the indexing model from the issue text.

Description

Environment

  • Yab 0.49.1 (macOS), Chromium engine
  • Extension: Tell AI Where v1.2.0 (mmjhngepomedhjijcfdagcembihoghao, Chrome Web Store, MV3, uses activeTab + scripting)

Problem
Clicking the extension on a local file:// page does nothing in one space but works in another. In Chrome this is controlled by the "Allow access to file URLs" toggle on chrome://extensions, but Yab has no chrome://extensions page and no equivalent setting, so there is no way to turn it on.

What I found

  • In my work space, the extension's newAllowFileAccess is true in Secure Preferences (looks like it was carried over during import), and the extension works on file:// pages.
  • In my Personal space, newAllowFileAccess is unset, and the extension does nothing on file:// pages.
  • Same Yab install, same extension version. The only difference is this flag.

Steps to reproduce

  1. Install an extension that injects with activeTab + scripting (e.g. Tell AI Where).
  2. Open a local file (e.g. a .html) in Yab.
  3. Click the extension.

Expected: Users can enable file URL access per extension (as in Chrome), and the extension works on file:// pages.
Actual: The extension silently fails, and there's no UI to enable access. Whether it works depends on hidden per-space state.

Related: #927 (another extension compatibility issue).

Dominant language
Swift
Stars
648
Forks
56
Avg merge
21h 14m
Merged PRs (30d)
22

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yetanotherbrowser/yab

All issues in yetanotherbrowser/yab

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.