Closed Bug 1259958 Opened 8 years ago Closed 8 years ago

After update, clicking a URL field in email does not open a webpage in Firefox (Win10, Tbird 38.7.1)

Categories

(Thunderbird :: Untriaged, defect)

Product:
Thunderbird
Component:
Untriaged
Version:
38 Branch
Platform:
x86_64
Windows 10
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: bob_gilman, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160315153207

Steps to reproduce:

open email with Thunderbird 38.7.1
select a message to read
click on URL in message to view webpage


Actual results:

Thunderbird flashed (twice?)


Expected results:

webpage should have opened in a Thunderbird tab.
Severity: normal → major
Priority: -- → P1
Summary: After update, clicking a URL field in email does not open a webpage in Firefox (Win10, Tbird 28.7.1) → After update, clicking a URL field in email does not open a webpage in Firefox (Win10, Tbird 38.7.1)
This may be a Windows 10 bug - after a restart, the feature works as expected.
The summary says the webpage should open in "Firefox", but the bug description says it should open in a "Thunderbird" tab. Which is the really expected behavior?
Priority: P1 → --
Bob?

(In reply to Masatoshi Kimura [:emk] from comment #2)
> The summary says the webpage should open in "Firefox", but the bug
> description says it should open in a "Thunderbird" tab. Which is the really
> expected behavior?
Severity: major → normal
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #3)
> Bob?
> 
> (In reply to Masatoshi Kimura [:emk] from comment #2)
> > The summary says the webpage should open in "Firefox", but the bug
> > description says it should open in a "Thunderbird" tab. Which is the really
> > expected behavior?

Oops. I meant "in a Firefox tab".  Sorry for the confusion.  BTW, I've not had this problem since that time, and I can't reproduce it.
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Thanks for the update
Resolution: INCOMPLETE → WORKSFORME
You need to log in before you can comment on or make changes to this bug.