292611 - DateTimePickers not showing if XBL file type is bound to an application.

Status: RESOLVED WONTFIX

(Calendar :: Sunbird Only, defect)

Description

[Frédéric Mercille]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

On Windows, if the XBL file type is set to automatically open with a specific
application, then the datetimepickers of the calendar won't show up.

Reproducible: Always

Steps to Reproduce:
1. Open a Windows Explorer window
2. Tools --> Folder Options... --> File Types tab
3. Click on the "New" button, and put xbl as the file extension, then click Ok
4. In the "Details for 'XBL' extension" box, click the "Change..." button, and
choose to "Select the program from a list"
5. Making sure the "Always use the selected program" box is checked, select any
program to open the file (e.g. Notepad)
6. Launch the calendar (it might require a reboot for some reason) and notice
that the calendar on the top left corner doesn't appear. When you double-click
to create a new event, the datetimepicker boxes don't appear either.
Actual Results:  
Calendar launches, but doesn't display any datetimepicker widget, rendering it
unsusable.

Expected Results:  
Calendar should have been able to display the datetimepicker widgets no matter
what the registry settings are for the default application opening XBL files.

To repair, you need to delete every instance of ".xbl" in your Windows registry.

Comment 1

[Rod Whiteley]

I have a default action for XBL to open in an editor.  It does not cause any
problem in Calendar.

I think the problem is the MIME type, not the default action.  If I set the MIME
type to text/xml then Calendar is OK.  If I remove the MIME type, then Calendar
is broken.

I wonder why Sunbird is not affected by this.

Comment 2

[Frédéric Mercille]

(In reply to comment #1)
> I have a default action for XBL to open in an editor.  It does not cause any
> problem in Calendar.
> 
> I think the problem is the MIME type, not the default action.  If I set the MIME
> type to text/xml then Calendar is OK.  If I remove the MIME type, then Calendar
> is broken.

It could be the MIME type and not the default action... not sure how I could
check that on Windows in order to confirm. What I did notice though is that it's
not only the calendar that breaks, but any extension that uses XBL bindings,
it's just pretty obvious on the calendar because one of the main widgets is a
XBL binding. Not sure if the bug should be moved to a different product, so I'll
just leave it here for now.

Comment 3

[Rod Whiteley]

(In reply to comment #2)
> ... not sure how I could check that on Windows...

When I use Windows to edit a file type (in Folder Options), I can specify the
MIME type there.

> ...any extension that uses XBL bindings...

Mozilla applications and most extensions use .xml files to contain XBL. 
Calendar is unusal in using .xbl files.  So Calendar has a particular problem. 
It is less likely that the .xml file type would have an unsuitable MIME type.

Comment 4

[Joey Minta]

(In reply to comment #3)
> Mozilla applications and most extensions use .xml files to contain XBL. 
> Calendar is unusal in using .xbl files.  So Calendar has a particular problem. 
> It is less likely that the .xml file type would have an unsuitable MIME type.

The experimental calendar extension now uses .xml files, rather than .xbl.  I'm curious whether anyone has managed to reproduce this in later builds?

Comment 5

[Martin Schröder [:mschroeder]]

Marking WONTFIX or WORKSFORME because XPI-only?

Comment 6

[Martin Schröder [:mschroeder]]

XPI-only
-> WONTFIX