[Webkit-unassigned] [Bug 40218] Disable interactive form validation in non-standard modes
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jun 14 15:20:12 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=40218
Maciej Stachowiak <mjs at apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjs at apple.com
--- Comment #10 from Maciej Stachowiak <mjs at apple.com> 2010-06-14 15:20:11 PST ---
(In reply to comment #9)
> (In reply to comment #7)
> > I’m not sure that compatibility mode vs. strict mode is the way to handle this. Maybe someone made the mistake on a website in strict mode too.
>
> We can say "your website doesn't conform to HTML5" in that case. But we can't say it for existing HTML4 sites.
>
> Please look at Bug#40520 too.
Existing HTML4 sites can also be in strict mode. In fact, a fair number of HTML4 sites have a standards mode or almost standards mode doctype. I don't think we should make new features be based on a modeswitch. The philosophy of HTML5 is to make new features backwards-compatible so they can be progressively deployed on existing sites. If HTML5 @required causes too much compatibility fallout, then we should:
(a) Remove HTML5 @required support entirely for now.
(b) Report our findings to the HTML WG and proposed renaming the attribute.
I don't think making the feature strict-mode only is an appropriate fix.
--
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