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

NEW
Unassigned

Status

()

Core
Drag and Drop
12 years ago
3 years ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
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

Comment 1

3 years ago
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.
You need to log in before you can comment on or make changes to this bug.