When a .webarchive file is saved, any background images in <tr> tags are not serialized to the output file.
Created attachment 12098 [details] WebArchive layout test (as patch) WebArchive layout test formatted as a patch.
This one is going to be very easy to fix with the new archive setup in WebCore However, I have a question... I find no evidence that <tr>s can officially have background images, standards-wise. Therefore, I'm guessing this is some Mozilla or IE compatibility thing we added. Looking at the HTMLTablePart code, it appears *any* table part can have a background image. Is that correct? If so, shouldn't this patch make sure all table parts get their background images saved?
(In reply to comment #2) > This one is going to be very easy to fix with the new archive setup in WebCore > However, I have a question... I find no evidence that <tr>s can officially > have background images, standards-wise. Therefore, I'm guessing this is some > Mozilla or IE compatibility thing we added. > > Looking at the HTMLTablePart code, it appears *any* table part can have a > background image. Is that correct? > > If so, shouldn't this patch make sure all table parts get their background > images saved? At the time, I think I only tested <tr> tags. If HTMLTablePart supports background images on all parts, then we should archive them.
A few further points of discussion: -The background attribute isn't officially supported for anything but <body>, I think, so its weird and nonstandard that we support it for any table parts -The background attribute for HTMLTablePart is fed directly into inline style information and handled in a very CSSey fashion. -Therefore, while we could support archiving the resource pointed to by the background attribute for table parts specifically, there's a broader-reaching problem of archiving resources referred to by all inline style. Not saying I don't plan to fix this specific bug, but... the more accurate we get with esoteric subresources (like background images of <tr>s), the more apparent it is that we're ignoring a large class of subresources
WAR export isn't supported these days.
Oops, thought this was filed as an inspector bug.