Extension:Semantic Forms/Known bugs and planned features

From MediaWiki.org
Jump to: navigation, search
Language: English
Semantic Forms - navigation (viewTemplate:Semantic Forms navigation)
Basics Main pageExtension:Semantic Forms (talk) · Download and installationExtension:Semantic Forms/Download and installation · Quick start guideExtension:Semantic Forms/Quick start guide · HostingExtension:Semantic Forms/Hosting · Special pagesExtension:Semantic Forms/Special pages
Using Semantic Forms SF and templatesExtension:Semantic Forms/Semantic Forms and templates · Defining formsExtension:Semantic Forms/Defining forms · The "Edit with form" tabExtension:Semantic Forms/The "edit with form" tab · Linking to formsExtension:Semantic Forms/Linking to forms · Creating query formsExtension:Semantic Forms/Creating query forms
Resources for help Common problemsExtension:Semantic Forms/Common problems · Known bugs and planned featuresExtension:Semantic Forms/Known bugs and planned features · Getting supportExtension:Semantic Forms/Getting support · Developers' documentationExtension:Semantic Forms/Developers' documentation
About Semantic Forms Authors and creditsExtension:Semantic Forms/Authors and credits · Version historyExtension:Semantic Forms/Version history · Sites that use Semantic FormsExtension:Semantic Forms/Sites that use Semantic Forms · Related extensionsExtension:Semantic Forms/Related extensions

Below are some notable known bugs, and major planned features, for Semantic Forms.

You can also see a listing of bugs and requested features in the Phabricator Semantic Forms listing.

Known bugs[edit | edit source]

  • Files whose names contain non-Latin characters get those characters messed up when they are uploaded via forms - the files themselves are uploaded correctly, but the resulting text that shows up in the form is incorrect.
  • There is currently a bug in Semantic Forms in which a "field" tag that ends with more than three brackets in a row will not get parsed correctly. So, for instance, the following in a form would fail: "{{{field|date|default={{CURRENTTIME}}}}}". If you have such a field tag, you can simply insert a space at the end to get around this bug, like "{{{field|date|default={{CURRENTTIME}} }}}". (Inserting a "|" won't work, unfortunately - it has to be a space.)
  • If you use the default MediaWiki URL style, #formlink won't work with the "button" link type. Instead, you should use "post button".
  • The "mandatory" setting does not work within popup forms.
  • If you have "$wgHtml5 = false" in LocalSettings.php, the "listbox" input will show up as a dropdown instead.
  • In some (though not all) installations, having a "placeholder" parameter in textarea inputs leads to the placeholder text getting set as the actual input value, for Internet Explorer 10 and 11; which seems to be due to this IE bug.
  • Most extra JavaScript-based features, like expandable elements and #info tooltips, don't work in multiple-instance templates for instances that are newly-added by the user within the form. (On the other hand, this does work for the tooltips provided by the SimpleTooltip extension, due to that extension's use of a hook.)
  • If you have the Configure extension installed, some combination of configurations may cause a JavaScript error which causes forms to break. If that happens, the best approach may simply be to un-install Configure.

Planned features[edit | edit source]

  • Allow #autoedit to add to and remove from a list of values, instead of just overwriting the entire value, possibly using notation like "Participants+=Joe User"
  • An editable-grid input for multiple-instance templates, possibly using the jqGrid Javascript library (click on "Row Editing > Input types")
  • Add handling in forms for the "Sight this revision" checkbox, if the FlaggedRevs extension is installed
  • Testing scripts using Selenium
  • Allow for the use of the VisualEditor in textareas (this would probably require VisualEditor supporting the editing of sections of a page, something it cannot yet handle)