[Webkit-unassigned] [Bug 34924] Add checks if setNeedsWillValidateCheck() and setNeedsValidityCheck() are called correctly

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Feb 14 05:47:36 PST 2010


--- Comment #2 from TAMURA, Kent <tkent at chromium.org>  2010-02-14 05:47:36 PST ---
(In reply to comment #0)
> > If we do cache a value I think it should be a single three-state concept: "will
> > not validate", "valid", "invalid". Treating these as independent makes the code
> > more complicated in places where they overlap. I know the DOM API for this
> > treats them separately, but the style code would be much simpler if it used a
> > single three-state concept.

I couldn't apply the single three-state concept.
According to the HTML5, the validity state should work even if willValidate is
false. So the patch introduces two boolean members.

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