mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3989] First link to Firefox Opens New Window Instead of New Tab #2496
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#2496
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Shimergo on GitHub (Feb 14, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3989
Firefox is firejailed. The first time I click on a URL in another application, it opens a new Firefox window with just my home page and not the link I want. It happens from any application (Thunderbird, KeePass, LibreOffice), and it doesn’t matter whether that app is firejailed or not. But clicking on subsequent weblinks (again any application), it then works fine, ie. it opens a new tab in the original Firefox window.
If Firefox is not firejailed, then I don’t get this weird first link-click behaviour.
Any idea how I can get that first click on a URL to open a new tab in the firejailed Firefox window? Presumably it’s something clever in ~/.config/firejail/firefox.local since this seems to be a Firefox ‘feature’?
@Shimergo commented on GitHub (Feb 23, 2021):
Although there’s a little extra info here regarding other applications affected, this issue is now being dealt with in #3982 , where it evolved from different symptoms found under a slightly older Firejail release.