# Talk:WYSIFTW

## Name

Can you tell me what "WYSIFTW" or "WYSIWTF" stands for? Thanks. Kenrick95 14:54, 7 January 2011 (UTC)

The original acronym is WYSIWYG - "What You See Is What You Get", meaning the document you edit on screen looks exactly like the result you print or publish. I replaced the last three letters with WTF, to indicate that the page will look more, but not quite like the normal wiki page. It was then suggested to use FTW instead. --Magnus Manske 16:41, 7 January 2011 (UTC)
Do you mean WTF = "what the f***" and FTW = "for the win" ? Kenrick95 15:09, 23 January 2011 (UTC)
Exactly. --Magnus Manske 13:07, 24 January 2011 (UTC)

## Bugs

Unfortunately, couldn't insert any text. I could delete it, and backspace it, but not insert anything. Opera 10.63 under Win7, if it's any help. Can it interefere with other gadgets? Maybe I should switch sth off? It looks too good to give up on it :D It seems also to be rather CPU consuming, am I right? (large page loaded looong)--Felis domestica 21:01, 7 January 2011 (UTC)

Yeah, i can confirm. Latest revision in toolserver (link) has some speed issues with Arora (Webkit based browser) but it seemed to work. With Opera 11.00 and Firefox 3.6.13 there is error "elm.children is not function in line 240" of wysiwtf.js. More specific error is in "postProcessBoldItalics : function ( elm )". With Google Chrome editor worked fine. For general usage i think that user experience would work better if templates, refs would expand as whole when one clicks them. Now user needs to click first ref open, then template open... eg.
After bug reporting i have to say that your editor is great! Thanks :) --Zache 08:32, 9 January 2011 (UTC)
ref suggestion implemented, speed issues are being worked on and should have improved already, FF 3.6.11 works, didn't check Opera. --Magnus Manske 13:09, 24 January 2011 (UTC)

## Speed on complicated pages

I just tried editing en:Anonymous (group). 218 seconds to parse before I could start editing (browser unusable in this time), and too slow to be able to edit effectively. This is on a Dell Mini 9 (1.6GHz Atom, 2GB memory) running Ubuntu 10.10 and editing in Firefox 3.6. How fast is it to open that page for editing for others? (Need numbers before trying to fix :-) ) - David Gerard 14:25, 16 January 2011 (UTC)

10.5 sec on a two-year-old iMac, using Mac OS and Chrome 10.0.634.0. Either is too long for mass usage, but tuning before all functions are working can backfire. Premature optimisation killed the lolcat! --Magnus Manske 22:59, 16 January 2011 (UTC)
For what it's worth:
 Dell Mini 9, Ubuntu 10.10 en:Anonymous (group) Firefox 3.6.13 218 sec Firefox 4.0b9 71 sec Chromium 8.0.552.224 145 sec Opera 10.62 260 sec
- David Gerard 12:09, 17 January 2011 (UTC)

Holy crap! 30 sec in FF 4b9, 17 sec in Chromium 8.0.552.237! - David Gerard 19:06, 19 January 2011 (UTC)

Now down to 8.9 sec in FF 4b10. This is approaching usable. Whatever you're doing, keep doing it :-) - David Gerard 22:04, 27 January 2011 (UTC)

## Pages with inherent differences

These pages do not survive the parsing/unparsing process unalteredorange, though mostly with only minor changes. Please add them when you find them - they are great "real life" test cases!

What about adding a link to "report this page" to pages with "inherent differences" so that users can easily inform which pages contains problematic markup? Helder 01:26, 23 January 2011 (UTC)

## Colors for expanded template with parameters

It would be good if, when we expand a template with multiple parameters, it used different colors to different kind of data. E.g.:

{{Template|param1=some text for first parameter|param2=and something else for second one}}

Helder 01:26, 23 January 2011 (UTC)

## Templates without parameters

I think the images and for "show/hide parameters" shouldn't be displayed for templates which doesn't have parameters. Helder 01:29, 23 January 2011 (UTC)

What if the user does want to add parameters? --Magnus Manske 13:11, 24 January 2011 (UTC)

## Subpages markup

In the current page, the wiki code [[/Subpage/]] generates a link to the page "Talk:WYSIFTW/'''Subpage'''" having the text "Subpage" (check: Subpage). Nonetheless, the script is currently displaying the text "/Subpage/", as if it were the displayed text. The bars shouldn't be displayed. Helder 01:45, 23 January 2011 (UTC)

## Math markup

Currently the tooltip displayed when hovering the mouse over a $or a$ tag say it is used for formatting. I think it would be better to say that it is used to insert formulas and other things like that. Besides, it could show a link to meta:Help:Displaying a formula (which has translations in some other languages), using the same style currently used when hovering over links.

Another useful thing would be to have a preview for big formulas, like the following from w:Heat_equation#Inhomogeneous_heat_equation:

$u(x,t)=\frac{1}{\sqrt{4\pi kt}} \int_{-\infty}^{\infty} \exp\left(-\frac{(x-y)^2}{4kt}\right)g(y)\,dy$
${\displaystyle u(x,t)={\frac {1}{\sqrt {4\pi kt}}}\int _{-\infty }^{\infty }\exp \left(-{\frac {(x-y)^{2}}{4kt}}\right)g(y)\,dy}$

Helder 02:13, 23 January 2011 (UTC)

## Positioning of cursor at the end of text

Currently the script doesn't allow us to insert text after the last character. For example, the article w:Trustmark ends with "US-bank-stub", but we can't put the cursor after the last "b". Helder 13:08, 25 January 2011 (UTC)

## Search box

If we click on WYSIFTW and after the script is loaded we click on search box and try to add some text (like "test") it is actually written in the article's beginning. The script should let us do a search (and maybe ask about leaving the page), and this would be another way to cancel the edit mode. Helder 13:08, 25 January 2011 (UTC)

Or perhaps searches could open in new windows while you use WYSIFTW? – Minh Nguyễn (talk, contribs) 09:01, 26 January 2011 (UTC)

## When to enable/import

I think the script could also be enabled when wgAction === 'purge'. Besides, it seems that those "importScriptURI" in the end of script could be moved into wysiwtf.init, after the following tests:

		if ( wgAction != 'view' ) return ; // Nevermind...
if ( -1 == \$.inArray(wgNamespaceNumber,wysiwtf.site.enable_for_namespaces) ) return ; // Nevermind...


Helder 17:10, 26 January 2011 (UTC)

## Some issues

Awesome tool...

• It doesn't work with the .js userscript, Hide Sidebar, since WYSIFTW blocks the text and can't be moved. Maybe an alternate placement at the page bottom, or a floating edit panel would be better.
• It's having some trouble in lists. Adding items, or playing with spacing between successive bullets *, really anything to introduce a line-break and then try to undo it resulted in sometimes the cursor getting stuck and requiring several deletes to clear.
• Is there a reason it doesn't work in userspace? It might be helpful for testing to be able to use it there.
• After returning from an edit to a section, sometimes the browser seem to doesn't anchor back to that section; instead it always returns to the top of the page. This should only happen if the whole page edit-link was selected.
• Copying text is difficult 'if it crosses section boundaries'.
• If you select a word and then hit delete, the word doesn't delete but the character before the selected word does.
• Sometime clicking in the middle introduces a line break that you can't delete without deleting the above paragraph.

Ocaasi 03:24, 28 January 2011 (UTC)

Hi!

The createTab function is not compatible with the mw 1.17. Could you try to use mw.util.addPortletLink instead, so that the formating of the link is compatible with the other links? I think this is related to rev:74740. Helder 18:08, 4 February 2011 (UTC)

It seems this was fixed on this revision. Helder 02:19, 24 February 2011 (UTC)

Hi!

The "help" link shown in the box (on left and below) still points to meta:WYSIFTW. Could you update it to WYSIFTW? Helder 02:07, 24 February 2011 (UTC)

Never mind, I just noticed this was already in the list. Helder 02:19, 24 February 2011 (UTC)

## Toolbox not visible

The toolbox on the left of the main text area containing the built-in functions (italics/bold, Save, Diff,...) is hidden by the languages box. It is a problem for article with a large number of interwiki links. Snipre 15:51, 1 March 2011 (UTC)

## References out of the text

Google doc have the following approach for references : display them on the right side. I think this may help to clarify the editable text, since recent events articles' code, by example, are almost half made of references. Example such :

 On the evening of 25 February a joint British and German operation consisting of two British military transport planes with [[United Kingdom Special Forces|British Special Forces]] on board and two German [[Transall_C-160|military transport planes]] with [[Fallschirmjäger#After_1945.2FBundeswehr_Fallschirmj.C3.A4ger|Fallschirmjäger]] on board evacuated 22 Germans and about 100 other Europeans, mostly British oil workers from the airport at Nafurah to [[Crete]]. {{cite web|url=http://www.guardian.co.uk/world/2011/feb/26/britons-rescued-libya-desert-raf |title=Libya: Daring SAS mission rescues Britons and others from desert |publisher=guardian.co.uk|accessdate=2011-02-28}}{{cite web|url=http://www.spiegel.de/politik/ausland/0,1518,748020,00.html |title=Riskante Rettungsmission hinter feindlichen Linien |publisher=spiegel.de |accessdate=2011-02-28}}{{cite web|url=http://www.bild.de/BILD/politik/2011/02/27/libyen-aufstand-gegen-gaddafi-so-dramatisch-verlief-die-rettungs/aktion-der-deutschen-durch-die-bundeswehr.html |title=So verlief die spektakuläre Rettungs-Aktion in Libyen |publisher=bild.de |accessdate=2011-02-27}} On the evening of 25 February a joint British and German operation consisting of two British military transport planes with British Special Forces on board and two German military transport planes with Fallschirmjäger on board evacuated 22 Germans and about 100 other Europeans, mostly British oil workers from the airport at Nafurah to Crete. [1][2][3]

Yug 06:03, 2 March 2011 (UTC)

## An editor for everyone ?

I think it is better to implement only basic functions in order to propose this tool for newbies. In my case I am not interested in such a tool because I configured my editing environment using monobook. The idea can be to propose this tool as default in the future for beginners in WP and let the present system available only on request. Snipre 09:31, 2 March 2011 (UTC)

### For all?

Maybe not just newbies.Geofferybard 04:15, 24 May 2011 (UTC)

If I access a thread page (created by LQT extension), like this, using only the WYSIFTW script, the link "Link To" doesn't works anymore.

Could you check what is wrong so that we can test it in normal pages without having problem on LQT pages? Thanks! Helder 14:39, 4 May 2011 (UTC)

## IE9 javascript error: Object doesn't support property or method 'removeAllRanges'

Tried WYSIFTW today, Looks promising telling from the screenshots. Hopefully this is what Visual editor will become. When I try to edit the Installation section on the WYSIFTW page in IE9 I get this javascript error in the console:

SCRIPT438: Object doesn't support property or method 'removeAllRanges'
wysiwtf.js, line 2009 character 6


I can place the cursor but not move it using keyboard arrows or remove text using delete/backspace. However inserting new text works except enter. In Firefox 8.0.1 it works fine though. --John Ericson 13:02, 8 December 2011 (UTC)

## Crashed me

Crashed me, using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110614 Firefox/3.6.18. I blame society first, then the Mozilla Foundation.
RiverStyx23 (talk) 00:54, 9 January 2013 (UTC)