Bug 48613

Summary:

<meter min=0 max=100 value=100> should be optimum.

Product:

WebKit

Reporter:

Kent Tamura <tkent>

Component:

Forms

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

morrita, yael

Priority:

Version:

528+ (Nightly build)

Hardware:

All

OS:

All

URL:

data:text/html,<meter min=0 max=100 value=100>

Attachments:

Description	Flags
Patch	tkent: review+

Kent Tamura

Reported 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). 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.

Attachments
Patch (357.22 KB, patch) 2010-10-28 23:47 PDT, Hajime Morrita	tkent: review+	Details Formatted Diff Diff
View All Add attachment proposed patch, testcase, etc.

Hajime Morrita

Comment 1 2010-10-28 23:47:15 PDT

Created attachment 72296 [details] Patch

Kent Tamura

Comment 2 2010-10-29 00:26:05 PDT

Comment on attachment 72296 [details] Patch ok.

Hajime Morrita

Comment 3 2010-10-29 02:47:23 PDT

Committed r70856: <http://trac.webkit.org/changeset/70856>

Yael

Comment 4 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:-)

Note You need to log in before you can comment on or make changes to this bug.