[Webkit-unassigned] [Bug 35633] New: [Qt] Provide a way to directly invalide the page cache in a QWebPage

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Mar 3 02:59:07 PST 2010


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

           Summary: [Qt] Provide a way to directly invalide the page cache
                    in a QWebPage
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Other
        OS/Version: Mac OS X 10.5
            Status: NEW
          Keywords: Qt
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: vestbo at webkit.org


This bug report originated from issue QTBUG-8438
http://bugreports.qt.nokia.com/browse/QTBUG-8438

--- Description ---

Since Qt 4.6, there has been a QWebPage:: ReloadAndBypassCache page action. But
it doesn't work when the page content has been set directly with
QFrame::setContent, and the HTML used references (for instance) CSS files on
disk. Even if those CSS files are changed after the page is loaded, triggering
both Reload and ReloadAndBypassCache does not change the styles applied (the
cache is used and the page doesn't see the changes).

<p>I'm not sure but I think the ReloadAndBypassCache action call doesn't work
because the initial load was from setContent, and not from an URL. Whatever the
reason, it doesn't work. We need an invalidatePageCache() function call.</p>

--- Comments ---

...and even deleting the QWebPage object and creating a new one doesn't clear
the cache, for God knows what reason. The only workaround I came up with was to
add "?rnd=<randomNumber>" to the end of local urls (with the QWebElement
API) so that the cache is bypassed.

It would be even better if I could tell the QWebPage which links not to cache
from now on, and for which links I want the cache to be invalidated right now.

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



More information about the webkit-unassigned mailing list