You need to
before you can comment on or make changes to this bug.
We disabled the interactive form validation feature because the implementation was incomplete and there were some compatibility issues. See Bug 40218 and Bug 40520.
We implemented the validation message bubble, Google Chrome 10 was released on March 9 with the interactive form validation feature enabled, and I didn't see many compatibility issues. Also, Firefox 4 was released with the interactive form validation feature.
I'd like to enable the interactive form validation feature by default.
Is bug 44436 somehow fixed now?
(In reply to comment #1)
> Is bug 44436 somehow fixed now?
As for required=no, I think there are no way to fix the issue other than introducing a site specific quirk.
Created an attachment (id=90422) [details]
We're planning to leave the feature off in Safari for the near, since the UI design is not up to our standards. We would like to revise the UI before we turn it on in anything we ship. Therefore, we'd prefer for this feature to stay disabled for now, at lead for ports shipped by Apple.
(From update of attachment 90422 [details])
As far as being enabled on trunk goes, I don't think that this can be landed without fixing bug 44436 first. That is a hugely important single page!
Discussions of how to fix 44436 should go into that bug, of course.
*** Bug 97085 has been marked as a duplicate of this bug. ***
Because I don't recommend to use platform-independent validation message UI with Shadow DOM, enabling the feature by default is not reasonable.