HTML5 required attribute breaks hack for form submission about codemirror-v1

[marijnh]

The problem seems to be that A) the validation attributes are checked before the onsubmit event is fired, so if CodeMirror clears the textarea, it'll be happily submitted, because it had something in it before, and B) the hint that pops up when the form is not submitted (which happens when the texarea was empty to begin with), seems to be placed in such an incoherent way (at least on Chrome) that it either doesn't show up at all (when the textarea has an absolute position) or ends up way in the wrong place (when the textarea is given a height of 0).

There doesn't appear to be a way to make CodeMirror play nice with such attributes, short of reimplementing them, which is out of CodeMirror's scope.

[qpleple]

Yes indeed.

So what do you choose? Saying that CodeMirror work only without requiredattribute or maybe find a fix?

If you don't want to extend CodeMirror scope to reimplementing such attributes, would you accept checks for these attributes and notice if they're here ?

[marijnh]

It could easily notice the attribute, or some other HTML5 validation attribute, is there, but how would it respond?

[qpleple]

Not creating the CodeMirror object and fail with a log message so that the developer knows something is wrong and that he has to remove the requiredattribute to make it work.

[marijnh]

I'd say it is the library user's responsibility to not create CodeMirror instances for his/her textareas in such a case. There are a lot of other broken ways to use CodeMirror, and I don't want to start testing for all of them in the library (mostly for file size reasons -- such extra code adds up).

[qpleple]

All right, fair enough.