Last modified: 2014-09-08 10:51:32 UTC
The Heading-field uses the same name/id as the Summary causing javascript tools targetting the summary to mess up. ie. a button to insert a template adds "; template Foobar added" to the summary, which is great otherwise, but when adding a new talkpage heading there is no summary so I'd expect the script to be unable to find a summary and do nothing. Instead it does find a "summary" field and appends it to it. Likewise there are gadgets replacing the summary with "/* Test */ section added" and inserting {{subst:test}}~~~~ This is great when editing the page, since it appends the template to the talkpage and sets the summary correct, but when using the "new section" button (§ion=new) it litterly sets the title of message to "/* Test */ new section". If these different field would have different name/id attribute values they can be targetted, detected and used appropiately.
In other words, EditPage.php should provide separate inputs for the section title and the edit summary, rather than using wpSummary for both.
(In reply to comment #1) > In other words, EditPage.php should provide separate inputs for the section > title and the edit summary, rather than using wpSummary for both. Krinkle is saying there should only be one input on the section=new form, but it should have a different id: "I'd expect the script to be unable to find a summary and do nothing."
EditPage.php can now handle separate section titles and edit summaries (as of 1.19). It should be rather trivial to change the edit form to take advantage of this.
(In reply to comment #3) > EditPage.php can now handle separate section titles and edit summaries (as of > 1.19). It should be rather trivial to change the edit form to take advantage of > this. Adding "easy" keyword then.
