Closed Bug 57624 Opened 25 years ago Closed 25 years ago

editing mimeTypes.rdf from prefs horks the file

Categories

(SeaMonkey :: UI Design, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.8

People

(Reporter: spam, Assigned: paulkchen)

References

(Blocks 1 open bug)

Details

2000102021 SEA linux If i add a helper application via preferences, an entry (several) for it will be written to mimeTypes.rdf. If i later modify the entry by "edit"-ing it, the entry in mimeTypes.rdf is not modified: Instead a NEW entry is written there. If i later again DELETE the whole entry from preferences, there are still entries left of it in mimeTypes.rdf. They just won't be displayed in preferences anymore. If i happened to type in errors earlyer, these errors will now remain in mimeTypes.rdf. So I will have to edit it manually to remove all traces of the erronous entry. (path will for instance remain) Perhaps this is the way it's supposed to work, but since i have problems adding both helper types as well as plugins, i thought this was worth mentioning.
Perhaps interesting: After leaving the mimeTypes.rdf as it was the following happened when i clicked a link to a realplayer file on web: A window opened asking whether to save or open the file. I clicked radiobutton to "open with". But I can't type in the form field. So am forced to click "Browse" and use filepicker. Directing filepicker to the correct /usr/local/RealPlayer7/realplay and clicking OK now spawn two dialog windows and no realplayer The two windows are: one saying "Saving file" to /tmp/cnnhn.ram and another one asking "Enter name of file to save to.." The latter has two buttons "Save" and "Cancel" so i click "Save" And then nothing happens. The "Saving file" dialog on first attempt just says Nan Nan" and vanishes. On second attempt it just hangs there and i have to cancel it since nothing happens. Trying this from the start yet once more revealed a hidden save dialog. Dismissing that with a cancel caused a crash. This displayed in console at that point: JavaScript error: chrome://global/content/filepicker.js line 260: nsIFilePicker is not defined (Talkback doesn't work, but that's old news.)
QA Contact: sairuh → shrir
Marking obvious dependency. Scott and Eric: I want to talk to you about this, so I can line up and pay you for the work I would like you to do before any work begins on that much less useful rfe to upload multiple files at a time. This is really important to me. Please email me and let me know when we can all three talk together.
Depends on: 58811
Correct me if I'm wrong, but I believe Ben owns this preferences panel.
Maybe I am wrong, because Matt owns bug 54059.
After deleting an entry, you can't add it back again (apparently somthing may still be written to the file), and trying to download a file of that type can cause a crash. This is the only crash I have seen more than once in the last 2 months.
Given that flaky and broken helper app controls were one of the most prominent complaints of 6.0, beta1 really shouldn't ship with this.
Keywords: nsbeta1
.8, over to pchen, possible dup or dependency.
Assignee: ben → pchen
Summary: editing mimeTypes.rdf from prefs hork the file → editing mimeTypes.rdf from prefs horks the file
Marking mozilla0.8 as other helper apps prefs work is being done in that time frame.
Target Milestone: --- → mozilla0.8
We're past time to cut these low priority bugs from mozilla0.8. Please update these bugs today.
So after carefully reading over this bug, the original problem stated in this bug report was also logged as bug 61079. That fix was checked in last night, so editing of mime types works much better. Marking fixed since the original problem should be fixed, but if you folks still see the other problems in this bug report, please report new bugs.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
mime type editing in Prefs is now fixed and working fine. VERIFIED
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.