Comment 1:

Labels changed: added priority-soon, removed priority-triage.

Owner changed to @nigeltao.

Status changed to Accepted.

Comment 3 by jsummers3456:

Firefox makes the undefined pixels black. ImageMagick makes them white (i.e. the first
color in the palette). The PNG spec says the file is invalid. What should Go do?

Comment 4:

i think this is WorkingAsIntended.

Comment 5 by darkgray:

That's a pretty sad approach. Suppose someone in the future wanted to write an image
editor. Should they just throw away a ton of possible openable images simply because Go
can't be bothered to parse them? At least make an alternative "MustDecode" version or
something.

Comment 6:

then how do we draw the line between acceptable and unacceptable images?
there will be tons of type of invalid images, how should we treat them?
i argue that whatever we do with them, the user needs a control, and that
unnecessarily complicates the API.
i think if you want to write an image editor, and specifically want to deal with
bad images, you definitely should apply an extra correction step to them
before feeding them to the image package.
that said, if we provide an API to retrieve the metadata of an image without
parsing them, we can accept images with this kind of defeats.
will let nigel to decide.

Comment 7:

This issue was closed by revision de6bf20.

Status changed to Fixed.