[webkit-dev] To start <meter> element implementation

Hajime Morita morrita at google.com
Sun Apr 4 21:52:32 PDT 2010


Maciej, Darin, thank you for your feedback!

> I believe <progress> is only currently enabled for the Qt port, in part
> because no one has implemented the other themes.
Yes, there are only Qt port and Mac port available now
and I agree with you that well-behaving one new element is more useful
than half-baked two.
So OK, I'll start porting <progress> to Chromium before I  start
working on <meter>.

On stylability and accessibility, currently I have no idea how to
implement these, and how hard they are.
I would investigate them later after chromium port, or original
<progress> author (Yael) might have
some ideas or code for that, which would be very helpful.
I'll follow the progress of our <progress> implementation.

--
morita

On Mon, Apr 5, 2010 at 11:31 AM, Maciej Stachowiak <mjs at apple.com> wrote:
>
> On Apr 4, 2010, at 7:23 PM, Hajime Morita wrote:
>
>> Hi folks,
>>
>> I'm planning to work on HTML5 <meter> element,
>> which is filed on https://bugs.webkit.org/show_bug.cgi?id=37074 .
>> Although there seems no effort for that element at this time,
>> The <progress> element looks similar to <meter>.
>> So I'll try to go the way as <progress> has been going and
>> share some part of codebase hopefully.
>>
>> Any suggestions and advices are welcome.
>> Thanks in advance.
>
> I don't know if there is much opportunity for code sharing. <meter> is
> pretty different from <progress>. It has a different purpose and should have
> a different default appearance.
>
> I believe <progress> is only currently enabled for the Qt port, in part
> because no one has implemented the other themes.
>
> I believe the big challenges to have really complete versions of <meter> and
> <progress> include:
>
> 1) Fully stylable custom look with CSS - it's hard to figure out how to do
> this, because these elements are both parameterized with an arbitrary level.
> 2) Accessibility support - we can't call these done until they offer at
> least as good an accessibility experience as explicit ARIA markup.
>
> I think it would be a good idea to truly finish <progress> first before
> embarking on <meter>. I would rather have one truly complete new element
> than two that are half-done.
>
> Regards,
> Maciej
>
>



-- 
morita


More information about the webkit-dev mailing list