Extension talk:InputBox

For the page history, see also here. / previous talk on this page

Previous page history was archived for backup purposes at Extension talk:InputBox/LQT Archive 1 on 2015-07-10.

Hi, how is type=move supposed to work? Using the example code at Extension:InputBox#Box types I can only specify the new name, not the name of the page that should be renamed.

From gerrit:97559 I gleaned -perhaps incorrectly- that the page= parameter should provide the original page name.

Is there a way for the user to specify the original name interactively or is a template or script necessary?

At w:Wikipedia:Requests for undeletion, the input form currently fills in the name of the page to be undeleted in the section title, but fails to do so within the text body. Could preloadparams[] be used to do this automatically? Adding a variable at w:Wikipedia:Requests for undeletion/example seems simple enough, but then how do I set that variable equal to the input in the box at w:Wikipedia:Requests for undeletion/header?

There seems to be an issue with the preloadparams[] = parameter, where instead of including %5B%5D the text %5B0%5D is included, where the extra "0" prevevnts it from functioning.

see example: wikiversity.org/wiki/WikiJournal_Preprints

Any ideas for fixing this?

Looks like something you should report on phabricator

The documentation suggests that the type=comment mode can be used to add a section to an existing page, when the page= parameter is provided:

<inputbox> type=comment page=Project:Sandbox </inputbox>

This would be great but it seems to not be how the feature works. Instead, the page parameter is ignored and the input text is used as the title of a new page. Not terribly useful when adding a section. I'd like to tweak this behavior to align with the documentation.

I've searched for this syntax on all wikis using the search insource:inputbox insource:/type=comment/ -insource:/type=commenttitle/ insource:/inputbox.*page=.*\/inputbox/ and it seems that the few existing usages are a mistake. However, I don't think that I shouldn't simply change the behavior, because a few usages combine default= and hidden=yes to add a blank section to an existing page. It would be confusing if the input field was used as the page title only when page= is not present.

@Adamw

Thanks for sharing your finding. I also tried and was disappointed. I found out that even Lua Scribunto also can not handle form input. Right now, we just have to depend upon the new section template , wherever interactivity with general users is concerned.

I'd like to propose two new functions to this extension. The first is a button color/class option. E.g. green button could be managed by "buttoncolor=green" or by 'buttonclass=mw-ui-progressive". The second is the level of the new section heading. E.g. 3rd heading could be managed by "headinglevel=3" What do you think? Could they be added?

@Dvorapa: Re: button colors - One goal of the ongoing design work, is to make a User Interface that is consistent, as in, once people are familiar with a button's action/outcome, they can expect consistent results. Hence, the button to submit a form (as in this extension, and others) should always be a single color (blue in our case). There's some related information at this (slightly outdated) page: Wikimedia Foundation Design/Color usage#Functional Colors.

Re: heading levels - I almost filed a feature-request for this in phabricator, but then I couldn't find any examples (I checked a few dozen pages linked from en:WP:Requests). Here's what I had drafted; please add your use-case, and any pre-existing examples you can find, and post it in phab.

Title: Allow inputbox to create an H3 heading

Description: Suggested feature: The addition of a new parameter, which would let an inputbox specify what Heading level to use, when creating the `section=new`. This would allow editors to use it more flexibly, on pages where the desired practice is to create feedback in a series of H3 sections. Example pages where this practice is wanted (or already done but manually) include ...

Note: I'm not sure if this is technically feasible though. The current system just hooks into the standard "New topic" tab on all talkpages. Adding new code to allow changing the H-level might be more complex than is desired.

This would be super helpful - it is difficult to design a page around the light grey color of the 'create' button.

@KHarold (WMF) I've commented at Phab:T88038 on the accessibility issues with the current light grey. See my answer to Dvorapa above, re: customizing colors. Hope that helps. :-)

I would like users to be able to look up an article based on pageid.

Using ?curid=PAGEID I can add the pageid to a url and go directly to the page. I would like to have a search function where the user input the pageid into a field, mediawiki appends the URL and the desired page opens up.

This should be easy. The only thing I cannot figure out is how to have the user type the pageid into a field and hit enter. From there I can turn it into a variable and inject it into the URL.

I was looking for the same thing. Guess you have to use the Extension:PageForms for this (Query form).

I would like to create lexemes in a specific language with a specific lexical category from a wikipage. See https://phabricator.wikimedia.org/T195446#6783459 for an url

For wikis with the VisualEditor installed, I think it would be handy to have a setting that enables a selector that allows a user to choose between creating an article in the VisualEditor and the source editor. It would certainly be neater than having two separate boxes.

+1

Hi, is it possible to modify the button colours, borders etc? And maybe the search box also?

Haven't tried this for the input box, but you can make custom changes to the mediawiki CSS via the MediaWiki:Common.css page. Giving it a quick look the CSS classes your interested in is "mw-ui-button", "mw-ui-input", "mw-ui-input-inline", and possibly "mw-inputbox-centered" for the whole form area. (I just pulled these from the browser via the JS dev tools)

A bit late, but maybe it is useful to you or someone else.

I tried this. Changing MediaWiki:Common.css worked for me.

.mw-inputbox-centered {text-align:left} /* not centered any more */

Ni! Especially for new page creation, it would be very useful if there was a parameter to launch the editor/action in a new tab or window. Quite often a page will have a button to create or edit another page, while the documentation pertaining to the activity to be developed on the next page is to be found in the original page where the inputbox is. There's a (very low) limit to what we can do to help users with only preloaded comments. I deal with this problem very frequently in my Wikiversity courses, but also in the organization of wikiprojects and editathons/workshops. This seems like a low hanging (and tasty) fruit. Abraços!

That sounds like a good idea to me! I've quickly searched Phabricator and I don't see an existing request for this feature idea. Please do file a new task there. (Ideally, include a specific example or two). Thanks!

Thanks for the support and pointing me to the right place, Quiddity ! :)

Here it is:

https://phabricator.wikimedia.org/T253940