Closed
Bug 301200
Opened 19 years ago
Closed 19 years ago
Open Link in New Tab/ Ctrl+Click does nothing. In Gecko 20050511 it works.
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: walter.spannagel, Unassigned)
References
()
Details
Attachments
(1 file)
|
423 bytes,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.10) Gecko/20050717 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.10) Gecko/20050717 Firefox/1.0.6 After installing the newest nightly build it was no longer possible to open links in new tabs, neither via context menu nor via ctrl+click. I found this problem also in a nightly build of 1.0.5de last week and returned to 1.0.4de. Now i realized that the problem still exists. (Maybe it's a problem of my extensions(see list attached), but why doesn't appear that problem in 1.0.4de?) Reproducible: Always Steps to Reproduce: 1.Open any website with links e.g. http://www.heise.de/newsticker/ 2.Set mouse to any link 3.DO ctrl+click, or open context menu and choose "Link in neuem Tab öffnen" Actual Results: nothing Expected Results: open that link in a new tab
| Reporter | ||
Comment 1•19 years ago
|
||
Comment 2•19 years ago
|
||
Does it occur if you start firefox in safe mode: kb.mozillazine.org/Safe_mode
Comment 3•19 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050718 Firefox/1.0+ ID:2005071812 Most likely an extensions problem, but WFM either way.
| Reporter | ||
Comment 4•19 years ago
|
||
As told by Adam Guthrie, it _is_a problem of one extension: tabbrowser extensions. I will report this problem to the author of the extension.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 5•19 years ago
|
||
Reopen to resolve invalid as this is an Extension problem
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•19 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•