Closed
Bug 271936
Opened 20 years ago
Closed 20 years ago
need .shtm, .xhtm in CFBundleTypeExtensions in Info.plist
Categories
(Camino Graveyard :: OS Integration, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Camino0.9
People
(Reporter: alqahira, Assigned: jaas)
References
()
Details
Attachments
(1 file, 1 obsolete file)
2.11 KB,
application/octet-stream
|
mikepinkerton
:
superreview+
|
Details |
Camino 2004112008 (v0.8+) won't accept saved pages via drag-drop to its icon if the the page has a file extension .shtm .xhtm (and perhaps a few other more "obscure" Windows-versions of webpage extensions) and the file has no file type set. These do work if dragged into a Camino window, though. And .shtml and .xhtml are already in the Info.plist (.htm is there, too). Is this what causes Camino to append the .html extension when saving a page with an .shtm extension, or is that bug 259903?
Apart from adding SHTM, XHTM I also added CSS drop support as that is also something users might want to do.
Geoff cc-ing you, could you perhaps create a patch for this bug? Mike and Joash want a patch.
just added both extensions to each file's HTML document extensions list
Attachment #168844 -
Flags: superreview?(pinkerton)
Attachment #167566 -
Attachment is obsolete: true
we have a patch so throwing this on the 0.9 list to get it in and over with
Target Milestone: --- → Camino0.9
Comment 5•20 years ago
|
||
Comment on attachment 168844 [details]
updated plist files for static and non-static v1.0
would like to see a patch, but if you say it's right....
sr=pink
Attachment #168844 -
Flags: superreview?(pinkerton) → superreview+
If I remember correctly Mano stoped by at camino irc and said that he was working on a related kind of issue with FF. He had made a far more extensive search for file types then I did because FF and camino support way more then what is now in our plist. Unfortunatly I can't find that bug anymore, so we could see what he did.
Reporter | ||
Comment 7•20 years ago
|
||
(In reply to comment #6) That's bug 233712; I did some of the early legwork for it on bug 266008 (and filed this one as a result). You can compare the current status of SeaMonkey, Firefox, and Camino Info.plist by searching for that file in LXR. Part of me tends to agree with CSS (comment 1), too, but the other part says that's a bit esoteric and I've got my .js and .css files set to open in my HTML editor, which is more useful. I don't recall any other extensions included in the Fx patch that we really need here, just these missing "variants" of extensions already included.
landed on trunk
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•