Forum:Edit Page Enhancements

Hi guys. If you have something to say related to the new Edit Page Enhancements, then feel free to put them in this thread so that they're all in one place.--Richard 00:37, 30 April 2008 (UTC)

Expand LinkSuggest to find templates
as it stands LinkSuggest only triggers when you start typing [[ and then stuff.

would it be possible to add another hook that would detect when you type {{ and then autosearch based only in the Template namespace?

to do this now, i have to type   find the template i want, pick it, then go back and change the   part to

you would need to detect if the 1st char after {{ is a { though and cancel the suggest box, otherwise anyone doing templates {{{variables}}} would go nuts.

--Uberfuzzy 22:31, 29 April 2008 (UTC)


 * I have a related request, and that is to expand LinkSuggest to find redirect links. Thanks. --LordTBT {{sup|Talk! }} 22:57, 29 April 2008 (UTC)


 * It also would be nice that it could handle Image suggest using the local language-specific prefix like '' Ciencia Al Poder (talk) {{sup|-WikiDex}} 15:13, 2 May 2008 (UTC)


 * The same with categories. --Ciencia Al Poder (talk) {{sup|-WikiDex}} 18:09, 12 May 2008 (UTC)

Control LinkSuggest window width via css?
the new linksuggest is nice, (especially glad to see it works out of NS:0 too), but is there a css class we can target to make the list window wider? --Uberfuzzy 19:47, 29 April 2008 (UTC)

Underscores
I just noticed that if I use LinkSuggest to input an article with a space in the title, let's say "Link Suggest", then instead of keeping the space, it turns that character into an underscore, so when reading the article it appears as "Link_Suggest". This should not be occuring, imo. --LordTBT Talk! 02:45, 30 April 2008 (UTC)
 * I agree, I'd like to see the underscores disappear.--Richard 21:25, 30 April 2008 (UTC)


 * Wow, it seems as if Wikia has rectified this already (and the redirects!) Thanks team! --LordTBT Talk! 22:59, 30 April 2008 (UTC)

Editing tips translation
Ok, I read the ''Admins: a few months after the initial rollout of this feature we will make the help text editable for you. At the start, though, we want to maintain some consistency so we can see how the feature is performing.''

But if we couldn't either translate it to our wiki language, then it's useless. What about Translations/Edit_tips? --Ciencia Al Poder (talk) -WikiDex 20:09, 1 May 2008 (UTC)


 * Hi... I believe the comm team is working to do a first translation (mandarin, german, spanish, polish, japanese)... obviously, translations are good and we want them... what we're more interested in is keeping the text targeted at newbies until we have some data to see if it's helping them. The concern with opening it up for all wikis to edit right out of the gate is that some admins may immediately change the text to suit more advanced users and then our test of whether this helps newbies is invalidated. I'll let the comm team respond about where they want the translations to live... just wanted to give you a bit more background on the decision. Johnq (talk) 19:31, 5 May 2008 (UTC)

Opinion
I liked much of the new tool that the Wikia released for inexperienced and experient users, I see myself them that she needs to be perfected like the comments above they said already (that at the same time they also are my opinions on the tool), but with the time I believe that she will be working fully, but the rest I liked very much. --Brunoy Anastasiya Seryozhenko ( Talk )  22:16, 1 May 2008 (UTC)

Monobook support
Only Link suggest has support for Monobook skins. Ok, I know that it was focused to the widget-style of monaco. But LinkSuggest has no CSS associated in the CSS for monobook, so it renders out of the edit area and without a list-appearance.

I solved that locally putting the following CSS code on MediaWiki:Monobook.css, but it should be fixed globally.

.navigation-hover { background-color: #e0efff; }

/*** Search suggest ***/ .yui-ac-container { z-index: 1000; position: absolute; top: 25px; left: 5px; width: 171px; } .yui-ac-content{ border:1px solid #808080 !important; color: #000; position: absolute; width: 100%; background:#fff; overflow:hidden; z-index:9050; } .yui-ac-content ul { float: none !important; margin: 0 !important; padding: 0 !important; width: 100%; } .yui-ac-content li { float: none !important; font-size: 9pt; margin: 0 !important; /*padding: 2px 5px !important;*/ padding: 1px 0px 0px 3px; cursor: default; white-space: nowrap; }

--Ciencia Al Poder (talk) -WikiDex 15:18, 2 May 2008 (UTC)


 * Oh! That's why i was thinking it did not worked on Monobook, it was appearing under the edit box. — TulipVorlax 18:10, 2 May 2008 (UTC)


 * Added the CSS code but it still appear under the edit box on GuildWars Wikia fr. Duh! — TulipVorlax 18:13, 2 May 2008 (UTC)


 * Because you put it inside a CSS comment (/* */) =P --Ciencia Al Poder (talk) -WikiDex 19:25, 2 May 2008 (UTC)


 * Oh! In reality, i just forgot to close a comment... lol. — TulipVorlax 23:45, 8 May 2008 (UTC)

LinkSuggest and non-ascii characters
When typing a link with non-ascii characters, the LinkSuggest receives a list of titles starting from the next character near the non-ascii character, ignoring the whole word. This is not a JavaScript problem but a server-side problem.

The following HTTP requests are made, one without a non-ascii character and other with a non-ascii character. If you see the response you'll understand what is the problem (in bold the real request):
 * Typing Pok.
 * Typing Pok é mon.

--Ciencia Al Poder (talk) -WikiDex 15:38, 4 May 2008 (UTC)