"Apply when the last tab closes" isn't working as expected (loads random tab in background)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- dart
- Domain
- mobile-dev
Research direction
Locate the tab close handling logic in the Dart codebase, find the code that runs when the last open tab is closed, and fix the condition for the 'Apply when the last tab closes' setting so it opens the configured home page instead of a random background tab. Test the fix on an Android device to confirm the unwanted background tab no longer loads.
Written by the indexing model from the issue text.
Description
The "Apply when the last tab closes" option in the Home & New Tab settings section isn’t working properly
Even when this option is enabled and "Home page" is selected in the setting above, closing the last tab in a container still opens a random tab from some other container
The only difference when "Apply when the last tab closes" is enabled is that this opened tab isn't displayed on the screen. Nevertheless, it loads fully in the background and gets recorded in history, including in all browser features that remember recently opened tabs.
This disrupts their sequence with pages the user never intended to open
Environment:
- Device: realme 9 pro+
- OS: Android 14
- WebLibre version: 0.30.0-alpha-3
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FaFre/WebLibre
-
bug enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
enhancement needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 60/100
-
enhancement needs-triage
Difficulty 5/5 Over a week Newbie friendliness 8/100
-
bug enhancement needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
needs-triage
Difficulty 4/5 1-2 days Newbie friendliness 48/100
Similar issues
-
bug from-telegram platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiddify/hiddify-app#2592 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cogwheel0/conduit#1122 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bannzai/shoppinglist#779 ·
Maintainers usually reply within 1 day
-
Android bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PostHog/posthog-flutter#731 · 1 comment ·
Maintainers usually reply within 1 day
-
[BUG] JEFIT import fails because # characters are not recognisedPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day