Bug 36224

Summary: Support for indeterminate progress bar
Product: WebKit Reporter: Yael <yael>
Component: DOMAssignee: Yael <yael>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: darin, tkent
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: All   
Bug Depends on: 36113, 36206, 36664    
Bug Blocks:    
Attachments:
Description Flags
Patch v1
none
Patch.
none
Patch none

Yael
Reported 2010-03-17 09:09:09 PDT
From http://www.whatwg.org/specs/web-apps/current-work/complete.html#the-progress-element-0 , user agents should distinguish between determinate and indeterminate progress bars.
Attachments
Patch v1 (20.55 KB, patch)
2010-03-19 09:17 PDT, Yael
no flags
Patch. (69.69 KB, patch)
2010-03-22 12:49 PDT, Yael
no flags
Patch (69.95 KB, patch)
2010-03-23 07:05 PDT, Yael
no flags
Yael
Comment 1 2010-03-18 08:17:30 PDT
Created http://bugreports.qt.nokia.com/browse/QTBUG-9171 for a Qt API to support this in the Qt port.
Yael
Comment 2 2010-03-19 09:17:22 PDT
Created attachment 51160 [details] Patch v1 This patch is blocked by https://bugs.webkit.org/show_bug.cgi?id=36206, so it contains the code from there. I will update as soon as https://bugs.webkit.org/show_bug.cgi?id=36206 changes status. This patch adds the possibility to animate the progress bar. The time interval and if the animate the progress bar is queried from the RenderTheme. It also removes some optimization code I previously added that was not welcome.
Yael
Comment 3 2010-03-22 12:49:00 PDT
Created attachment 51337 [details] Patch. Updated the tests from the previous patch. This patch adds support, test results and enables the PROGRESS_TAG flag on the Mac port of Safari.
Yael
Comment 4 2010-03-23 07:05:34 PDT
Created attachment 51423 [details] Patch Update XCode project file after 56360 and 56361, to make the GTK build bot happy.
Yael
Comment 5 2010-04-01 07:58:05 PDT
The original issue reported here was resolved in https://bugs.webkit.org/show_bug.cgi?id=36664 *** This bug has been marked as a duplicate of bug 36664 ***
Note You need to log in before you can comment on or make changes to this bug.