Bug 48613 - <meter min=0 max=100 value=100> should be optimum.
Summary: <meter min=0 max=100 value=100> should be optimum.
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: data:text/html,<meter min=0 max=100 v...
Depends on:
Reported: 2010-10-28 20:33 PDT by Kent Tamura
Modified: 2010-10-29 05:44 PDT (History)
2 users (show)

See Also:

Patch (357.22 KB, patch)
2010-10-28 23:47 PDT, Hajime Morrita
tkent: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kent Tamura 2010-10-28 20:33:42 PDT
<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).

> 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.
Comment 1 Hajime Morrita 2010-10-28 23:47:15 PDT
Created attachment 72296 [details]
Comment 2 Kent Tamura 2010-10-29 00:26:05 PDT
Comment on attachment 72296 [details]

Comment 3 Hajime Morrita 2010-10-29 02:47:23 PDT
Committed r70856: <http://trac.webkit.org/changeset/70856>
Comment 4 Yael 2010-10-29 05:44:44 PDT
(In reply to comment #3)
> Committed r70856: <http://trac.webkit.org/changeset/70856>

Thanks for taking care of this:-)