The browser would need to know which <noimg> element to show when an <img> is corrupt.ahagen wrote:As for wanting a fallback for a corrupt image, I don't see how that would affect the proposal for noimg.
They improved their handling of <object> between IE7 and IE8. My speculation is that they can't fix all bugs at once but have to prioritize. Or they are unaware of this being an issue.ahagen wrote:If I may ask, do you have a guess, or have you heard speculation, about why Microsoft has not properly implemented the object element in IE 8?
I actually have a test case for this and have filed a bug about this to Microsoft (I think twice, but my first report disappeared when they opened the bug database again for IE8). Although I don't get a scrollbar but instead IE8 instantiates the QuickTime plugin. It does show an iframe-ish inset border around the image, too.
https://connect.microsoft.com/IE/feedba ... kID=350052
http://simon.html5.org/test/ie8rc1-bugs/003.html
It doesn't break sites (because IE7 didn't support it properly) and people don't whine enough about it, I guess. You can comment or vote on the above-mentioned bug (or file a new more specific bug about this).ahagen wrote:I wonder why it isn't a higher priority.
I doubt it.ahagen wrote:Does Microsoft see the object element as a competitor to Silverlight or another of Microsoft's technologies?
I think that's what we should push for. It would be great if we could use <object> for images in IE, too (without it loading plugins or showing borders or scrollbars).ahagen wrote:As you've said, it is at least possible, if not probable, that Microsoft could fix object image support faster.