[Webkit-unassigned] [Bug 48613] New: <meter min=0 max=100 value=100> should be optimal.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Oct 28 20:33:42 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=48613
Summary: <meter min=0 max=100 value=100> should be optimal.
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
URL: data:text/html,<meter min=0 max=100 value=100>
OS/Version: All
Status: NEW
Severity: Normal
Priority: P2
Component: Forms
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: tkent at chromium.org
CC: yael.aharon at nokia.com, morrita at google.com
<meter min=0 max=100 value=100>
With this element, the current WebKit shows even-less-good gauge (red). But the gauge should be "optimum" (green).
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-meter-element
> If the optimum point is equal to the low boundary or the high boundary, or anywhere in between them, then
> the region between the low and high boundaries of the gauge must be treated as the optimum region, and
> the low and high parts, if any, must be treated as suboptimal.
In this case, low=min=0, max=high=100, optimum is 50. "between the low and hight boundaries" might be ambiguous about inclusive or exclusive. But it should be inclusive because the value on the low value should be optimum if optimum==low. Anyway, this sentence define we doesn't show even-less-good gauge in this case.
--
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