PitsFormCheckVersionInput

Can we do even better than the new "Latest:" button next to the version field?

Demo for one aspect of PITS.01412.

To simulate the future of PITS, edit the version input box in your DOM inspector and set the attribute pattern="^\s*2\.2\.98\s*$" (ideally with current numbers).
- If we want to avoid the required attribute, we can negate the validation (pattern="^(?!(?=\s*2\.2\s*$)).*") and CSS criteria. This should also help if there are browsers that have problems with concluding CSS :invalid from an empty required field.
If your browser doesn't support pattern regexp validation, you can try ticking one of the checkboxes instead. Or both to simulate a broken browser. ;-)
Future versions of PmWiki might generate the pattern via a markup expression like {(preg_quote "{(substr "{$Version}" 7)}")}.

PmWiki Version:	<– latest <– other Latest release: available on the Download page. If you see this, the automated version comparison doesn't work in your browser. Great, your PmWiki is up to date!Looks different from the latest release. Maybe an update can help?
Submit:

0: 00.00 00.00 config start 1: 00.01 00.01 config end 2: 00.21 00.20 MarkupToHTML begin 3: 00.22 00.22 MarkupToHTML end 4: 00.23 00.22 MarkupToHTML begin 5: 00.23 00.23 ReadApprovedUrls SiteAdmin.ApprovedUrls begin 6: 00.24 00.23 ReadApprovedUrls SiteAdmin.ApprovedUrls end 7: 00.24 00.24 MarkupToHTML end 8: 00.24 00.24 MarkupToHTML begin 9: 00.25 00.24 MarkupToHTML end 10: 00.25 00.24 now