[Webkit-unassigned] [Bug 82291] [Blackberry] A page containing multiparts with "multipart/x-mixed-replace" should not be cached.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=82291


Brady Eidson <beidson at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |VERIFIED




--- Comment #7 from Brady Eidson <beidson at apple.com>  2012-03-28 10:18:32 PST ---
(In reply to comment #6)
> (In reply to comment #5)
> > This patch has no explanation of why this is desirable, and no regression test. Is this something all platforms need, or something all other platforms already have?
> 
> "multipart/x-mixed-replace" is HTTP server push. If we stored them in Page Cache, some images( most of cases) can not show up on back/forward. 

Not clear what you're trying to say here.

I think what you're saying is that if we cache such a page, we'd stopAllLoaders therefore cutting off the stream to the image.  Then when the page is restored the user would just see the most recent frame rendered before the loaders were stopped.  Is that correct?

>QT does not support "multipart/x-mixed-replace"

But if they ever add support, they will have this bug.  Correct?

> Chrome has own pageCache management

Currently they simply have no page cache.  They're experimenting with enabling the WebCore page cache now and - when they do - they could presumably be affected.

>Mac has the issue with "multipart/x-mixed-replace" on back/forward.

The same issue as Blackberry?  Therefore this fix should be applied to Mac also?

> I have not a strong power to unify them:). 

There is nothing "blackberry specific" about this bug.  This bug exists for "platforms that use the page cache that also support multipart/x-mixed-replace".  That current includes Blackberry, Mac, and Windows.  Chrome is experimenting with joining that club by enabling the page cache.  If Qt ever supports multipart/x-mixed-replace they will also join that club.

You don't have to make Chrome support the page cache or make Qt support multipart/x-mixed-replace to fix this bug.  You just have to fix it cross-platform in a way they can benefit from in the future.

Also - since this is a cross platform bug and is something that is testable in the layout tests - this patch should include a regression test.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.