Jump to content

Extension talk:InputBox

About this board

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


using inline= for types other than search2?

1
NowInHD (talkcontribs)

Hey, how come the parameter inline= is limited to search2? Is there any way I could use it with the create type?

Reply to "using inline= for types other than search2?"

Use input in preloadparams[] possible?

1
Andre601 (talkcontribs)

Is it possible to use the provided input value as a preloadparams[] value to pre-fill the template with it?

Reply to "Use input in preloadparams[] possible?"

Autocomplete possible?

5
95.174.66.61 (talkcontribs)

Is autocompletion possible in search type InputBox?

Quiddity (WMF) (talkcontribs)
165.225.73.45 (talkcontribs)

Use Case: Build a google-like start page

Krabina (talkcontribs)
Lostraven (talkcontribs)

Interestingly, we have autocomplete working in our InputBoxes. However, the problem we're encountering is even when we tell InputBox to limit the search to a specific namespace, the autocomplete does not also limit its suggestions to that specific namespace. I found an old inactive extension that advertises "autocomplete is provided on predefined namespace," which is exactly what I'm looking for, but the extension is soooo old. I'll comment on that phabricator request too.

Reply to "Autocomplete possible?"

How to deselect "Main" namespace in search

3
School4schools (talkcontribs)

From your documentation, I see that "Main" is "checked by default." How can I uncheck it, or search for ONLY a different namespace, such as File ?

I have tried these and it still returns results from (Main)

<code>prefix=File:</code>

<code>namespace=File</code>

Thanks for help!

The wub (talkcontribs)

Even with only one namespace, you still need the parameter to be plural e.g.

<inputbox>
type=search
namespaces=File
</inputbox>
School4schools (talkcontribs)

Thanks for taking the time to fix my silly mistake.

Reply to "How to deselect "Main" namespace in search"

Is it possible to add a minimum or maximum length?

1
QuickQuokka (talkcontribs)

Hello!

I recently came across w:Wikipedia:Wikipedia Signpost/Templates/Crossword cell, which uses this feature of MediaWiki, but you can enter more than one character per cell.

I think that it would be useful if we could add a minimum or maximum length to the text. Would this be possible to implement?

Reply to "Is it possible to add a minimum or maximum length?"

Button color/class and new section heading

5
Dvorapa (talkcontribs)

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?

Quiddity (WMF) (talkcontribs)

@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.

KHarold (WMF) (talkcontribs)

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

Quiddity (WMF) (talkcontribs)

@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. :-)

JPxG (talkcontribs)

I will second, or third, or whatever this request. I'd also like to be able to give the input field a class name, so that I can style an individual inputbox without having to make a rule that styles every one on the page.

Reply to "Button color/class and new section heading"
Bertux (talkcontribs)

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?

Reply to "type=move"

Help with preloadparams[] application

1
Sdkb (talkcontribs)
Reply to "Help with preloadparams[] application"

%5B0%5D inserted into URL in stead of %5B%5D

2
Evolution and evolvability (talkcontribs)

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?

Ciencia Al Poder (talkcontribs)

comment and page don't work together

3
Adamw (talkcontribs)

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.

Adamw (talkcontribs)

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.

Arjunaraoc (talkcontribs)
Reply to "comment and page don't work together"