Isolation extended features

Open
#372 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
mobile

Research direction

The issue names no file, test or entry point, so there is no obvious starting point. Start by finding how the existing per-site container assignment works and whether it can carry an isolation mode. Before writing code, get the maintainer to decide between blacklist and whitelist behaviour and where the toggle lives in the favicon menu. Done means that decision is recorded and the chosen behaviour is covered by a test.

Written by the indexing model from the issue text.

Description

enhancement P2

I am suggesting to implement whitelist and blacklist url isolation options. Similarly how certain urls assigned to containers, we could configure in black list mode urls that will be always isolated. Or if we use whitelist mode, all our tabs will be isolated, except thos we put in exclusions.

For that there has to be a setting in webpage menu (when you click on favicon) so we could easely add or remove website from lists.

Dominant language
Dart
Stars
1k
Forks
41
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 FaFre/WebLibre

All issues in FaFre/WebLibre

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.