Reviewed by Dan Bernstein.
WKPageGetEstimatedProgress returns wrong value after a mainframe provisional load has started
https://bugs.webkit.org/show_bug.cgi?id=53358
* UIProcess/WebPageProxy.cpp:
(WebKit::WebPageProxy::didStartProgress): Start progress at the magic initial value, not 0.
git-svn-id: http://svn.webkit.org/repository/webkit/trunk@77043
268f45cc-cd09-0410-ab3c-
d52691b4dbfc
+2011-01-28 Maciej Stachowiak <mjs@apple.com>
+
+ Reviewed by Dan Bernstein.
+
+ WKPageGetEstimatedProgress returns wrong value after a mainframe provisional load has started
+ https://bugs.webkit.org/show_bug.cgi?id=53358
+
+ * UIProcess/WebPageProxy.cpp:
+ (WebKit::WebPageProxy::didStartProgress): Start progress at the magic initial value, not 0.
+
2011-01-28 Anders Carlsson <andersca@apple.com>
Yet another build fix (What was I thinking?)
parentFrame->appendChild(subframe);
}
+
+// Always start progress at initialProgressValue. This helps provide feedback as
+// soon as a load starts.
+
+static const double initialProgressValue = 0.1;
+
void WebPageProxy::didStartProgress()
{
- m_estimatedProgress = 0.0;
-
+ m_estimatedProgress = initialProgressValue;
+
m_loaderClient.didStartProgress(this);
}
void WebPageProxy::didChangeProgress(double value)
{
m_estimatedProgress = value;
-
+
m_loaderClient.didChangeProgress(this);
}