Closed Bug 338354 Opened 20 years ago Closed 19 years ago

Firefox causes Palm Desktop to display a .pdb file in garbage chars

Categories

(Firefox :: File Handling, defect)

1.5.0.x Branch
PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: david.sloan, Unassigned)

Details

(Whiteboard: CLOSEME 06/27)

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Build Identifier: Firefox for Mac 1.5.0.3. Steps to reproduce: 1. Install Palm Desktop from CD. 2. Have Firefox as the default browser 3. Click on Additional Resource icon in Palm CD installer 4. Click on Bonus Software 5. Click on Bejeweled and Install button 6. The list of Bejeweled files is displayed. 7. Click on the Bejewled.prc file and save to the disk, they get stored in a Downloads bucket, as expected. 8. Click on the Bejeweled-music1.pdb file. Actual results: It is displayed as text with garbage characters. Expected results: Expected the.pdb files to be added to the Downloads bucket. To reproduce, download any .pdb file from the web and attempt to sync it to a Palm device via HotSync. Install HotSync from the Palm website if you don't have it. Reproducible: Always Steps to Reproduce: see above Actual Results: see above Expected Results: see above see above
What is the .pdb file actually supposed to do?
Summary: na → Firefox causes Palm Desktop to display a .pdb file in garbage chars
A .pdb file (and a .prc file) should queue up in the HotSync manager so they are ready to get synced over to the device upon next HotSync. So, the files are to be moved to the Downloads bucket in the HotSync app on the desktop. The files shouldn't display on the desktop. Firefox shouldn't try to open the file. They are device files. A pdb is a "palm database" file.
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
No response from reporter re: comment 3 -->INCOMPLETE. Reporter, if you still see this problem with the latest release of Firefox 2, please reopen this bug. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.