I found *A VERY SIMPLE WORKAROUND* for this bug:
If you *DRAG A FOLDER* containing images *TO THE Preview ICON IN THE DOCK* (or in the Finder), all images contained in that folder will be opened, even images in nested subfolders.
As a side effect, *ALL THE OPENED FILES WILL BE DE-QUARANTINED*.
(This also works with the corresponding command */usr/bin/open -a Preview.app
folder_name* )
Except, this seems to depend on a certain condition, which is that for some reason, the folder which you drag to the Preview icon must itself have a com.apple.quarantine attribute – which it had in my case.
Let us now think about how these files and folders acquired that attribute:
The attribute was put (by the browser or by the OS ?) on a .zip file when it was downloaded by me, at which time the folder and the files contained in that Zip-file didn't have the attribute.
Then when the content in the archive was extracted, it inherited the attribute from the Zip-file, and how this is done seems to depend totally on the unarchiving utility used. The +Archive Utility.app+ puts the attribute from the archive-file on both folders end files in the extracted content. When I tried /usr/bin/unzip, it put the attribute only on files, not on folders, which made the drag-folder-to-the-Preview-icon trick not work, so I installed StuffIt Expander to give it a try. Turns out that the latest *STUFFIT EXPANDER DOESN'T APPLY THE QUARANTINE ATTRIBUTE*, which makes it *ANOTHER WORKAROUND FOR DOWNLOADED ARCHIVES*.
So because inheritance of the quarantine attribute seems to depend on the unarchiver used, I would guess that applying the attribute on download is also up to the modern browsers themselves (I tried Firefox and Safari), and not enforced by some special magic of the operating system. For example, /usr/bin/ftp doesn't apply the quarantine bit on http download. Maybe someone else can tell us about other browsers.
I can understand the security considerations behind this, and I think the bug is just that Preview.app (and probably other applications?) hasn't been properly implemented to handle this.
Bye the way, this seemed promising:
http://mymacinations.com/2008/02/06/changing-the-systems-default-settings-for-ht ml-files-safe/
I tried to add entries for public.jpeg, jpg and jpeg, but it didn't work ...