Closed Bug 638442 Opened 13 years ago Closed 13 years ago

Clicking the "related link" on the dialog for a read-only meeting does nothing

Categories

(Calendar :: Dialogs, defect)

Lightning 1.0b2
x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 541310

People

(Reporter: bugzilla, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110221 Ubuntu/10.10 (maverick) Firefox/3.6.14
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8

When opening a meeting from a read-only remote calendar a very basic dialog is shown, containing the title, start and end time and a "related link", which should take you to the meeting details in the remote calendar.

However, nothing happens when you click on this link, at least on my system (Ubuntu Maverick 32-bit).

Reproducible: Always

Steps to Reproduce:
1. Add a read-only remote calendar
2. Open a meeting from the read-only calendar
3. Click on the Related Link
Actual Results:  
Nothing happens.

Expected Results:  
The link should be opened in a web browser.
Does it work in a normal, non-read-only calendar, i.e. is Thunderbird capable of opening links at all? Could you check Tools > Error Console for calendar related messages when testing your problem?
Version: unspecified → Lightning 1.0b2
Normal non-read-only events don't have links I can click on, but I can open links in emails by clicking on them with no problem.

There are indeed lines in the error console when I click on the link in the read-only event dialog. The following two lines appear when I do it:

No chrome package registered for chrome://navigator/content/navigator.xul
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMJSWindow.open]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://global/content/bindings/text.xml :: open :: line 357"  data: no]
Based on that message it seems to be a duplicate of Bug 541310.
It does look like the same issue, yes, although in my case there's a second, more nasty looking line in the error console (both lines appear at the moment I click on the link).
Ok, lets take a look at the issue in the mentioned bug.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.