[Webkit-unassigned] [Bug 35937] Support for HTMLProgressElement

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Mar 10 15:33:48 PST 2010


https://bugs.webkit.org/show_bug.cgi?id=35937


Darin Adler <darin at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darin at apple.com




--- Comment #9 from Darin Adler <darin at apple.com>  2010-03-10 15:33:48 PST ---
(In reply to comment #6)
> 1. There should be no impact from the addition to html.css on platforms that
> don't support the progress tag. That's because the element would not be
> created.

That’s incorrect. Today I can create a <progress> element and style it with
rules that specify the progress tag. It won’t be a special type of element and
will be handled as an inline element just as <span> is, but those style rules
will change the rendering of existing web pages.

> 2. I don't think "value" and "max" qualify as [reflect] attributes. If they are
> set with invalid values, those values are not accepted and some defaults are
> used instead.

If they are not [Reflect] they still do need to change the attribute you would
get with getAttribute, not just a hidden internal value.

HTMLInputElement has a max attribute. Are you sure this should be different in
this respect? To convince me, you need to demonstrate the expected behavior
with test cases and then show me either another browser or HTML5 specification
to make it clear the behavior it tests is correct.

-- 
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