Open Bug 336295 Opened 18 years ago Updated 3 years ago

Dragging broken GIF shouldn't call imgContainerGIF::GetFrameAt(0)

Categories

(Core :: DOM: Copy & Paste and Drag & Drop, defect, P5)

Product:
Core
Component:
DOM: Copy & Paste and Drag & Drop
Type:
defect

Tracking

()

People

(Reporter: jruderman, Unassigned)

Details

Dragging a broken GIF shouldn't call imgContainerGIF::GetFrameAt(0).

Bug 329889 was fixed by adding a range check in imgContainerGIF::GetFrameAt, but several comments there (starting with #19) question why it's being called with an out-of-range index.
QA Contact: drag-drop
Dragging and dropping a GIF image from Firefox into Explorer should result in the GIF image being saved in Explorer.  Instead, dragging a GIF image from Firefox into Explorer results in a single frame being saved as a BMP image.  That's absolutely the wrong behavior, and should be corrected ASAP.

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.