Open Bug 581817 Opened 14 years ago Updated 2 years ago

Edit Event: Print option grayed out

Categories

(Calendar :: Dialogs, defect)

Sunbird 1.0b1
x86
Linux
defect

Tracking

(Not tracked)

People

(Reporter: andrew, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.7) Gecko/20100715 Ubuntu/10.04 (lucid) Firefox/3.6.7 GTB7.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091211 

When opening an event the Edit Event: window opens.  Under the File menu, the Print Ctrl P option is grayed out and cannot be selected.  Page Setup option opens but has no effect on the Print option.

Reproducible: Always

Steps to Reproduce:
1. Double click any event
2. File menu
3. Print option grayed out
Actual Results:  
No change

Expected Results:  
I should be able to print an individual event with all its details to the printer.
Version: unspecified → Sunbird 1.0b1
To print an event/task please select the event in the main calendar view and execute menu File > Print.
Component: Printing → Dialogs
QA Contact: printing → dialogs
(In reply to comment #2)
> To print an event/task please select the event in the main calendar view and
> execute menu File > Print.

That is what I have tried to do but the option is greyed out. In addition, the this original bug report is for Sunbird 1.0b1, the bug I am reporting is for 1.0b2 (the version I am using). From what I can see, this was supposed to be fixed in 1.0b2 but I am having the same issue as others seemed to have had in 1.0b1. If I can supply you with any additional information, please let me know.
Confirming, seeing this with Lightning 1.0b4 rc1.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I have the same issue in Lightning 1.9 - after opening the event, the print option is greyed out. Work-around to print the event from the main calender works, but is cumbersome.
Is there no interest in fixing this counterintuitive UX-bug at all?
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.