Last modified: 2014-03-01 00:14:44 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 T52735, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50735 - VisualEditor: Transclusion dialog informing you that there are "no unused parameters" looks odd; improve message?
VisualEditor: Transclusion dialog informing you that there are "no unused par...
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: Low minor
: ---
Assigned To: Editing team bugs – take if you're interested!
:
: 54094 (view as bug list)
Depends on:
Blocks: ve-templatesupport
  Show dependency treegraph
 
Reported: 2013-07-04 11:22 UTC by Oliver Keyes
Modified: 2014-03-01 00:14 UTC (History)
6 users (show)

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


Attachments
Screenshot (18.50 KB, image/png)
2013-07-04 11:22 UTC, Oliver Keyes
Details

Description Oliver Keyes 2013-07-04 11:22:10 UTC
Created attachment 12753 [details]
Screenshot

See screenshot; not sure this is how it's meant to look, but it's how it looks. If there are no unused parameters it seems like the box notifying you of such should overwrite, rather than sit under, the search box - that's unnecessary functionality if all available parameters exist.
Comment 1 James Forrester 2013-08-30 23:16:39 UTC
Possibly we could say "No known parameters" and "No more known parameters" to make it clearer?
Comment 2 Oliver Keyes 2013-08-30 23:20:52 UTC
Possibly? Offering people the ability to do something when the system knows it won't end in what they want probably isn't the direction we want to be going in, however.
Comment 3 James Forrester 2013-08-30 23:25:24 UTC
(In reply to comment #2)
> Possibly? Offering people the ability to do something when the system knows
> it won't end in what they want probably isn't the direction we want to be
> going in, however.

But the system doesn't 'know' that. TemplateData is hinting, not a binding-contract-of-doom. It's (intentionally) possible to add parameters that aren't in the hinting, because the hinting is out-of-date or doesn't cover this "secret" parameter, or because the name of your parameter is generated (e.g. {{CURRENTDAY}}=Easter Egg! or something more useful). Remember that there's almost no end to the level of flexibility that WT allows users…
Comment 4 Oliver Keyes 2013-08-30 23:50:08 UTC
Urk. Tis true. In particular, I'm thinking of scenarios where you have an infinite number of parameters (templates that merely order and format a set of inputted data, for example). "No more known parameters" would work.
Comment 5 Chris McKenna 2013-08-31 00:06:32 UTC
Yes, "No more known parameters" would work. 

Not essential, but if it's not too much work, including a link to an explanation (that there may be unknown parameters and that these can be used) and/or the template documentation (if there isn't one provided elsewhere on that view) would be good. Obviously both should open in a new window/tab.
Comment 6 James Forrester 2013-10-09 18:10:30 UTC
*** Bug 54094 has been marked as a duplicate of this bug. ***
Comment 7 John Mark Vandenberg 2013-10-21 06:49:52 UTC
Just noting that bug 54094 (which was marked as a duplicate) is about the "Unknown parameter" message which appears (briefly) after the user has typed in '1'/'2' but not pressed enter yet.

(In reply to comment #5)
> Yes, "No more known parameters" would work. 
> 
> Not essential, but if it's not too much work, including a link to an
> explanation (that there may be unknown parameters and that these can be used)
> and/or the template documentation (if there isn't one provided elsewhere on
> that view) would be good. Obviously both should open in a new window/tab.

That is essentially bug 49772.

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


Navigation
Links