Last modified: 2011-10-30 13:34:34 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T32479, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 30479 - Input types with JavaScript are not correctly initialized in existing entries of multiple templates
Input types with JavaScript are not correctly initialized in existing entries...
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SemanticFormsInputs (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: s7eph4n
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-08-20 19:49 UTC by s7eph4n
Modified: 2011-10-30 13:34 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description s7eph4n 2011-08-20 19:49:09 UTC
I have a form with a repeating multiple instance template with 2 timepicker fields inside.  The fields save correctly the first time I click "Add Another" and generate the new fields.  I can use the JavaScript timepicker just fine, and the data saves correctly to the page.

However, when I try to ''edit'' that same page, there is a JavaScript error when I click on any of the ''existing'' timepicker icons.  (Any new fields created by clicking "Add Another" work just fine though.)  The JavaScript error on each click reads:

document.getElementById(this.id.replace("_button", "_tp_show")) is null

----

There are problems with other input types, too, e.g. datepicker.
This may be either a problem with MW1.17 (Resource Loader?) or SF 2.2 (names of inputs were renamed, some input types are probably dependent on a specific format for the input names).
Comment 1 s7eph4n 2011-10-30 13:34:34 UTC
Should be fixed in r101055.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links