At a glance

1 · What is claimed?

Only the report text below — no validator has restated it as checkable claims yet.

2 · What does it affect?

Not yet mapped to any requirement or component.

3 · Is it reproducible?

No validation has been run yet.

4 · What remains unclear?

• Not validated yet: no claims, no reproducer.

5 · What happens next?

Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

First, thank you for all of the work on this great project. I really like the introduction of the "bare" option. 

The problem is that even with the bare option, we still install Chromium. This can of course be uninstalled and keybindings updated to the browser of choice (Brave), but doing so also breaks the web2app function and any previously created desktop entries as this feature only support Chromium.

Possible solutions:
- An interactive choice of Brave or Chromium on install, which could then be reflected in the web2app function.
- Bare doesn't install Chromium and web2app has an additional argument (optional) to pass your chromium based browser 

Brave's ad-blocking is really helpful for media apps so it would be really cool to see web2app support Brave. 

Also, I would be willing to implement this if any of these ideas are of interest. Thank you!

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.