User talk:Cacycle/wikEd#CSS-Error in wikEd.user.js.

This script is trying to access the deprecated globals skin, wgServer, wgTitle, wgCanonicalNamespace, wgArticlePath, wgScript, wgScriptPath, wgUserName, wgCurRevisionId, wgContentLanguage, wgUserLanguage, wgEnableAPI, wgPageName, wgNamespaceIds, wgFormattedNamespaces, wgVersion and wgPageContentModel instead of using mw.config.get('wg...') to acess them (check the multiple warnings in the console). Helder 23:30, 14 January 2015 (UTC)

: Helder: Thanks, I will check into this (it may take a while as I am quite busy in real life at the moment...). Cacycle (talk) 11:31, 22 February 2015 (UTC)

{{ping|Cacycle}} It’s been a while since the above message. If you don’t care about pre-RL clients, the following line should fix the problem (instead of lines 18347–18350):

globalScopeCode += 'wikEd.wikiGlobals.' + names[i] + '=mw.config.get("' + names[i] + '");';

—Tacsipacsi (talk) 16:46, 9 September 2017 (UTC)

:I didn’t look at the source of wikEdDiff, but I see warnings for that as well (and this code says it’s copied there, so there shouldn’t be big differences). —Tacsipacsi (talk) 16:50, 9 September 2017 (UTC)

Still a problem, shouldn’t be archived yet. —Tacsipacsi (talk) 18:25, 10 October 2017 (UTC)

:I've now fixed this. It was kind of annoying during debugging, so better get it out of the way. —TheDJ (talk • contribs) 21:04, 10 October 2017 (UTC)

::Almost. In line 1371, 'if (typeof ' + names[i] + ' != \'undefined\') {' still tests the global variables even in modern environments. —Tacsipacsi (talk) 21:42, 10 October 2017 (UTC)

::P.S. This refers to wikEdDiff.js, the main wikEd code is OK. —Tacsipacsi (talk) 21:45, 10 October 2017 (UTC)

Wow, this took care of about [https://grafana.wikimedia.org/dashboard/db/mw-js-deprecate?refresh=1m&orgId=1&panelId=7&fullscreen&from=1503060302686&to=1508244302686&var-Step=24h 2/3 of the remaining calls] to these legacy variables. —TheDJ (talk • contribs) 12:54, 17 October 2017 (UTC)

While checking log entries to see how many daily requests would be broken by fixing T41936: Limit on number of piped values in API should throw an error, I noticed a request that seems to be due to your editor. In particular, I see in wikEd.LinkInfoCall() that you're extracting links without batching them to the maximum number allowed for the titles parameter. You can check the maximum by making a call to action=paraminfo, or you would be reasonably safe in hard-coding it to 50 (500 for users with the 'apihighlimits' right, e.g. sysops).

I can reproduce the issue while logged out (in a private browsing window) by going to https://en.wikipedia.org/w/index.php?title=Paul_Warfield&action=edit and using the code at User:Cacycle/wikEd installation#Complete version to load wikiEd. Getting your bug report thing to work in that situation was something of a pain (it doesn't seem to like being used while logged out), but eventually I monkey-patched it well enough to produce output:

• Date: 2017-07-17 15:53:18 UTC
• wikEd version: 0.9.148 (March 20, 2017)
• Browser: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 (Linux x86_64)
• Skin: vector (detected: vector_new)
• MediaWiki: 1.30.0-wmf.7
• Gadgets:
• MediaWiki scripts: RefToolbar.js, RefToolbarMessages-en.js, RefToolbarConfig.js
• Scripts: User:Cacycle/wikEd.js, User:Cacycle/diff.js, User:Cacycle/wikEdDiff.js
• URL: https://en.wikipedia.org/w/index.php?title=Paul_Warfield&action=edit
• User subpages: None, IP user
• User/skin.js: None, IP user
• User/common.js: None, IP user
• Error console: No error messages are produced. But if you open the one POST to api.php and look at the response, it includes a warning "Too many values supplied for parameter "titles". The limit is 50.". The request includes 114 titles.
• Problem description: See above
• Steps to reproduce: Just load the editor on the page. Note that bots and sysops have the 'apihighlimits' right, so you'll want to either use an unprivileged account or find a page with over 500 links.

Also, a suggestion: If you set the Api-user-agent HTTP header in your API requests to something appropriate, it will be easier for me to identify when an issue is due to wikiEd and you'll be able to use Special:ApiFeatureUsage to watch for issues yourself.

Thanks! Please ping User:Anomie if you need a reply from me, otherwise I'm not likely to see it. BJorsch (WMF) (talk) 16:03, 17 July 2017 (UTC)

Hello, I'm using wikEd with Chrome 49 in german Wikipedia and I'm getting english buttons "Preview" and "Changes" when this feature is activated. Also "wikEd help" link should go to the german help page.--Sinuhe20 (talk) 07:21, 19 July 2017 (UTC)

{{Tracked|T183647}}

WikEd appears to add hard spaces from time to time such as [https://en.wikipedia.org/w/index.php?title=Parkinson%27s_disease&type=revision&diff=791796008&oldid=791791493]

Can we have it stop per [https://en.wikipedia.org/wiki/User_talk:WhatamIdoing#Hard_spaces]? Doc James (talk · contribs · email) 17:25, 23 July 2017 (UTC)

: WikEd is not adding non-breaking spaces. They are already there, and wikEd just makes them 'visible' in the code by changing them to  . — JJMC89 (T·C) 18:22, 23 July 2017 (UTC)

::I started a section at the help page with a convenient shortcut since this appears to be a common query elsewhere. Review WP:WIKEDNBSP. The rationale for why wikEd does this might reasonably be included there (I believe it's because we expect invisible characters always to be visible in some way). --Izno (talk) 14:53, 25 July 2017 (UTC)

:::User:Izno can we have wikEd convert "invisible non-breaking space" into normal spaces? WikEd can than fix some glitch that is occurring some place else. Doc James (talk · contribs · email) 16:43, 5 December 2017 (UTC)

::::{{ping|Doc James}} I don't think the request is an unreasonable one either technically or socially, but that might look even more confusing to editors than nbsp's mushrooming. --Izno (talk) 16:48, 5 December 2017 (UTC)

:::::Why do you think it would be confusing User talk:Izno? If people want to add real hard spaces than they will need to add them visibly. Doc James (talk · contribs · email) 17:27, 5 December 2017 (UTC)

::::::{{ping|Doc James}} Because they will see a space replaced with a space in the diff. I guarantee that will generate as many questions as nbsp does. --Izno (talk) 21:52, 5 December 2017 (UTC)

::::::::Better than the adding of all the _ _ though Doc James (talk · contribs · email) 21:55, 5 December 2017 (UTC)

:::::::::I have filled out a phabricator ticket here.[https://phabricator.wikimedia.org/T183647] To try to get this issue fixed. Doc James (talk · contribs · email) 01:51, 24 December 2017 (UTC)

::::::::::Your request doesn't have consensus, and anyway isn't a part of MediaWiki but instead this script, so the request on Phabricator will likely close as invalid. --Izno (talk) 02:23, 24 December 2017 (UTC)

:::::::::::Please fix it. Some "dumb as posts" admins have already warned me, and removed comments, for editing other user talk page comments because the editor inserts the nbsp character anywhere it sees fit. It shows in diffs as a change by an editor that they didn't make and can't undo. The editor should not make any changes in a work where the edit is attributed to a user. It's a false attribution. Run a bot if the wiki needs changes, not a random fix by the editor. --DHeyward (talk) 08:31, 26 December 2017 (UTC)

::::::::::::It's irritating for authors when wikEd executes automatic changes (corrections) because most users of wikEd don't know that wikEd does this and thus don't expect this behaviour and are puzzeled about this changes, they didn't make. Furthermore they dont have any clue where these changes might come from or will expect an edit-conflict which of course can't be found in the history of the page, what also leaves them puzzeld.
DHeyward correctly mentioned the problem, that by this behaviour also signed contributions of other users (e. g. in talk pages and other pages requesting singning of contributions) are changed, what thwarts the idea of signig ones contributions. If this replacement function should be kept, it must be disabled for any edits in Talk namespaces and other namespaces and pages that request the singning of contributions.
The automatic replacement also causes problems in the name-parameter of the Template:Coord (also in eqivalent templates in other languages wikipedias like :de:Vorlage:Coordinate), because any entity placed in the value of this parameter, is put into the URL which is created by the template, in a way, that it is passed to the GeoHack as entity, and also appears als entity (e. g. ″ ″) in the headline of the GeoHack. Thus a non-breaking space in the value of the parameter name of the Coordinate-Templates must not be changed into an entity  . If the general automatic replacement function should be kept, wikEd must learn to distinguish between the mentioned cases, and behave apropriate to the context (namespace and template-parameter). --X:: black ::X (talk) 12:15, 8 February 2018 (UTC), updated 12:23, 8 February 2018 (UTC) and 12:31, 4 May 2018 (UTC)

:::::::::::::I fully agree with other editors' concerns about this function. Please either 1) remove it entirely, or 2) make it optional via a user-side parameter, or 3) replace the found non-standard characters with regular blanks instead of NBSPs (whichever option is best from a technical POV). I greatly appreciate all the work you have done to provide a lot of useful functionality for editors, but this one is actually counterproductive. GermanJoe (talk) 09:38, 2 March 2018 (UTC)

:::::::::::::: According to the Phabricator ticket, it turns out Visual Editor was adding invisible   and wikEd was simply making them visible. — Dispenser 13:03, 2 March 2018 (UTC)

{{outdent}} The WikEd feature still changes editor signatures (which is discouraged as cosmetic change of talkpage messages imo) and in article content derived from other sources (like old browsers or external editing software). Hopefully the VE flaw will be fixed, but that doesn't solve the underlying problem in this tool itself. GermanJoe (talk) 11:31, 11 March 2018 (UTC)

:As long as wikEd isn't able to use this nbsp-replacement feature only in those contexts where it is useful, or this nbsp-replacement feature isn't removed entirely, it should be made optional (e. g. by customization of wikEd). User:Cacycle/wikEd customization#Customization describes the options to customize wikEd. Among the user configurable variables in User:Cacycle/wikEd.js is already:

// convert all   character entities to actual characters for textarea editing and saving (not recommended)
if (wikEd.config.nbspToChar === undefined) { wikEd.config.nbspToChar = false; }

.
This one will perhaps not solve this problem, but if it's possible to have replacements the one and the other way round, it should also be possible to just leave both, the character and the nbsp-entity, as they are. The above mentioned template-case shows, that in some cases it's necessary to have both within one page. --X black X (talk) 12:31, 4 May 2018 (UTC)

Hi,

I am trying to use wiked in Tamil wikisource. First, when wikEd is enabled I am unable to choose other languages in input method. second the wikEd option is not enabled in header and footer section of wikisource. Thanks. Regards Balaji ^{(Let's talk)} 02:06, 15 August 2017 (UTC)

To install WikiEd on the Haitian Creole Wikipedia, do I just translate th variables and cut and paste to its own .js page? Barbara (WVS) ✐ ✉ 11:32, 26 August 2017 (UTC)

: Barbara (WVS): please check User:Cacycle/wikEd_installation for details. You probably need the "complete version" on your your common.js page. Cacycle (talk) 20:45, 12 November 2017 (UTC)

I noticed that in some browsers there is a problem with pasting text from links - often the Left-to-right character is inserted as well. I don't know that this is particular to wikEd, but it would be nice if wikEd had a feature or button to make it easy to cleanup Left-to-right characters, and maybe other invisible characters, before posting. -Furicorn (talk) 20:31, 30 August 2017 (UTC)

Im along time user of Wikipedia and WikEd but lately I've developed minor vision issues. I've figured out how to magnify the text of Wikipedia without magnifying images and basic layout elements (i.e. without using browser zoom), and I like it that way.

One feature that's right next to the "Text zoom cycling" button is labeled "Simple view: hide refs, templates, and table code" and whichever setting I choose for that sticks with me between edit sessions. But I seem to have to set the text zoom manually on every edit which requires a few clicks (either four or shift plus two). Also, at least in this session, zooming seems to have made it so my usual method of saving an edit (tab,tab,enter) doesn't work and I have to manually click the Save button. Is this intentional, and is there any other way I can make the magnification permanent? i.e. using CSS properties perhaps?

I'm glad to see WikEd is still being actively developed in order to keep up with changes in Wikipedia and to add new features. Thank you for your effort and time. —Soap— 16:38, 7 September 2017 (UTC)

:Reply to self ... still interested, but while researching the next question I looked through the code and it seems that WikEd simply inherits its text size from the internal editor, which explains why the text is also not magnified when I turn off WikEd. —Soap— 23:00, 20 September 2017 (UTC)

::Further reply ... [https://en.wikipedia.org/w/index.php?title=User:Soap/monobook.css&diff=prev&oldid=801644152 this edit] solved my problem for the mainspace and anything that uses the same CSS style (possibly nearly everything except other code pages). The coloring seems different somehow, but that's probably just an illusion caused by the text becoming less bold as it gets larger. —Soap— 23:11, 20 September 2017 (UTC)

I could have sworn there used to be a section in the Customization doc about increasing the height of the main box, but I can't find the right code anywhere. Does anyone know how to do it? Pariah24 (talk) 01:47, 15 September 2017 (UTC)

:I guess I can just drag the box down every time; it would be nice to not have to do that though. Pariah24 (talk) 02:56, 15 September 2017 (UTC)

::I may be able to help. In the JavaScript source code for WikEd there is a series of lines that says

:::// frame

::::'.wikEdFrameHtml': 'height: 100%; width: 100%; padding: 0; margin: 0; background: transparent; background-image: url({wikEdImage:resizeGrip}); background-attachment: fixed; background-position: right bottom; background-repeat: no-repeat; line-height: normal;',

::::'.wikEdFrameBodyPlain': 'height: auto; min-height: 100%; width: auto; background: transparent; margin: 0; padding: 0; padding-left: 0.25em; overflow: auto; font-family: monospace;',

::::'.wikEdFrameBodySyntax': 'height: auto; min-height: 100%; width: auto; background: transparent; margin: 0; padding: 0; padding-left: 0.25em; overflow: auto; font-family: monospace;',

::::'.wikEdFrameBodyNewbie': 'height: auto; min-height: 100%; width: auto; background: transparent; margin: 0; padding: 0; padding-left: 0.25em; overflow: auto; font-family: monospace;',

:::Have you tried changing the height: values in those lines? You probably would only need to change one, since it looks like WikEd has three modes, and I've only ever used the Syntax mode. I was able to resize the window in Chrome's toolbox by changing the height: value of .wikEdFrameBodySyntax to a random number. This might mean that making a similar change in your userspace would resize the textbox permanently. But whereas I solved a problem of my own by editing my CSS file, I think you would need to edit your custom.js file instead. —Soap— 23:19, 20 September 2017 (UTC)

::::You should be able to change CSS using CSS subpage (e.g. .wikEdFrame { height: 35em; }). If it doesn't work for first, try adding !important (i.e. .wikEdFrame { height: 35em !important; }). CodeEditor will complain about it, but it's OK. —Tacsipacsi (talk) 19:04, 21 September 2017 (UTC)

:::::{{ping|Tacsipacsi}} Are you saying to put it in common.css rather than common.js? Pariah24 (talk) 19:06, 22 September 2017 (UTC)

{{outdent|:::::}} If you have pure CSS code, it should go to common.css. If you have styles in JavaScript for some reason, it should go to common.js. So the following is CSS:

.wikEdFrame {

height: 35em;

}

while this is JS:

wikEd.config.frameCSS['.wikEdFrame'] = 'float: left; width: 100%; border: 0; height: 35em;';

(you have to add all the default styles in the latter form in order not to override them, it's automatically done when you use CSS).

--Tacsipacsi (talk) 20:34, 22 September 2017 (UTC)

Hi there, Cacycle! I love this editor of yours with the helpful syntax highlighting and improved changes comparison display. My only problem is that while I can use your editor on almost every wiki (including third-party wikis), for some reason I can't use it on Wikipedia itself (it is displaying a "Incompatible script, gadget, or addon: Code Editor - wikEd 0.9.149" error). I've enabled it in gadgets and I've also written down the complete code in my userpage. Help is greatly appreciated. Thanks! --Tenryuu (talk) 22:30, 19 September 2017 (UTC)

: Hi {{U|Tenryuu}}. CodeMirror/Code Editor/Wikitext syntax highlighting cannot be used with wikEd. CodeMirror can be disabled in your beta preferences. — JJMC89 (T·C) 01:24, 20 September 2017 (UTC)

:: Hi {{U|JJMC89}}, thanks for the help. It is now working properly. --Tenryuu (talk) 02:13, 20 September 2017 (UTC)

Hi, {{U|Cacycle}}! I have a minor visual problem I was hoping you could resolve. So when I try to do a pipe trick (e.g., ) the live preview doesn't seem to render it properly (it'll come out as ). Clicking the standard "Show Preview" button renders it properly as an internal link. Any fixes for this tiny problem? Thanks! --Tenryuu (talk) 22:28, 24 September 2017 (UTC)

It's not only about the pipe trick, but everything which is changed while saving, like template substitutions, signatures etc. It's because wikEd doesn't use the pst parameter, so

// API request

if ( ( wikEd.wikiGlobals.wgEnableAPI === true || wikEd.wikiGlobals.wgEnableAPI === 'true' ) && livePreview === true ) {

var postFields = {

'format': 'xml',

'action': 'parse',

'title': wikEd.pageName,

'text': textValue

};

should be changed to

// API request

if ( ( wikEd.wikiGlobals.wgEnableAPI === true || wikEd.wikiGlobals.wgEnableAPI === 'true' ) && livePreview === true ) {

var postFields = {

'format': 'xml',

'action': 'parse',

'pst': '1',

'title': wikEd.pageName,

'text': textValue

};

(maybe it could use mw.Api for easier response processing and maintenance). --Tacsipacsi (talk) 12:38, 25 September 2017 (UTC)

::Sorry for the late response {{U|Tacsipacsi}} and thanks for letting me know about this. Would I have to go into my common.js to add that line? --Tenryuu (talk) 20:29, 2 October 2017 (UTC)

:::No, it should be changed in the main script (i.e. User:Cacycle/wikEd.js)—I hope Cacycle knows this… (Although I recommend you to blank your common.js and load the script as a gadget as described in User:Cacycle/wikEd installation#Gadget, just to make it clear that you don’t have to maintain anything.) --Tacsipacsi (talk) 18:49, 3 October 2017 (UTC)

::::{{replyto|Tacsipacsi}} simple enough change.. I just did it. since Cacycle seems to be away a lot lately. —TheDJ (talk • contribs) 20:19, 3 October 2017 (UTC)

:::::{{reply to|TheDJ}} Thanks! --Tacsipacsi (talk) 21:48, 3 October 2017 (UTC)

File:WikEd logo displayed on top of the pages next to the log out link.png

It is not clear how to enable this gadget.

It is frustrating that this page is locked down and cannot be edited by other users. 11:15, 2 October 2017 (UTC) — Preceding unsigned comment added by Moscowamerican (talk • contribs)

{{-}}

{{edit fully-protected|User:Cacycle/wikEd|answered=y}}

Please add this screenshot to the page:

:File:WikEd logo displayed on top of the pages next to the log out link.png

It is currently not clear in the instructions how to enable this gadget. Moscowamerican (talk) 11:16, 2 October 2017 (UTC)

:{{ping|Moscowamerican}} please be more specific. Where exactly is it going? Is a caption, or further text required alongside? And please resolve the copyright tag on the image otherwise it may get deleted. — Martin (MSGJ · talk) 12:08, 2 October 2017 (UTC)

::This is why most pages are not protected by administrators, it hampers editing with unnecessary bureaucracy.

:: I added it to the help page here: User:Cacycle/wikEd_help#Enabling_WikEd, a similar section could be created to this protected page. Use your imagination :)

::Also, if I wouldn't have come back to wikipedia, the image would have been deleted by a bot, even though it is clearly a free image of wikipedia. No one bothers to take less than a second to fix this?

::Admins often seem so paralyzed, really doing nothing but keeping the status quo. Moscowamerican (talk) 04:34, 3 October 2017 (UTC)

:::Moscowamerican: Point 2 from Wikipedia:Edit requests says "Any edit request must be accompanied by a detailed and specific description of what changes need to be made. Clearly indicate which sections or phrases should be replaced, and what they should be replaced with." If you had made your request specific, it would probably have been done on 2 October. — Martin (MSGJ · talk) 12:25, 5 October 2017 (UTC)

{{edit fully-protected|User:Cacycle/wikEd|answered=y}}

This page is locked for the following reason:

:

I suggest:

1. putting the security-sensitive code in a subpage,
2. protecting the subpage,

1. nesting the subpage in this page, or creating a link to the security-sensitive code subpage,

....so that normal non-administrators like me, who have over a decade of mediawiki and wikipedia experience, but happen not to be administrators, can edit this page.

In addition, if a link was created to the security-sensitive code if would make the main page easier to read.

Thank you for your consideration. Moscowamerican (talk) 11:22, 2 October 2017 (UTC)

:That should work. {{ul|Cacycle}}: are you okay with that? — Martin (MSGJ · talk) 12:08, 2 October 2017 (UTC)

:: Moscowamerican, MSGJ: I protected this page because of the embedded wikEd installation code. Somebody changing that code could potentially cause harm. Moving that code to a subpage and unprotecting the main page would not help at all - anybody could then replace the templates with plain text code. Cacycle (talk) 14:27, 2 October 2017 (UTC)

:::Excuse my ignorance, but what sort of harm could be caused by malicious editing? E.g. could it allow someone to install something different on your computer? — Martin (MSGJ · talk) 18:56, 2 October 2017 (UTC)

::::People can follow incorrect instructions and accidentally install malware. It's not that common, and likely this page is watched by enough people that it wouldn't last more than a few hours... Usually we don't bother with things like this, but wikEd is rather widely used, also outside of English Wikipedia, and as a greasemonkey script. —TheDJ (talk • contribs) 20:22, 3 October 2017 (UTC)

:::::I had a look around :Category:Wikipedia tools and couldn't see any other examples where the installation instructions were protected. That probably indicates that the risk is not high. I think we could consider lowering protection to semi perhaps? — Martin (MSGJ · talk) 10:49, 5 October 2017 (UTC)

:::::I've lowered to semi protection. If that is deemed insufficient, then a compromise may be extended confirmed, but there are no other tools that protect pages like this, so I'm not convinced it is needed. — Martin (MSGJ · talk) 07:13, 6 October 2017 (UTC)

:User:Cacycle is your page, so the community has little say it what would make the page better in the long run.

:Do this extensions ever move by the owner to public space? Moscowamerican (talk) 04:28, 3 October 2017 (UTC)

CharInsert (mw:Extension:CharInsert) doesn't work with wikEd: if one clicks on a character in MediaWiki:Edittools (on a wiki where it's visible, unlike enwiki), nothing happens. As it's an extension, this gadget should be fixed to work with CharInsert, not vice versa. --Tacsipacsi (talk) 19:10, 11 October 2017 (UTC)

: Tacsipacsi: It works fine for me. On my private wiki I had to update the gadget Edittools to the latest version (≥ May 27, 2016) for mw:MediaWiki:Edittools to work at all (unrelated to wikEd). Hope that helped... Cacycle (talk) 23:28, 11 November 2017 (UTC)

::I don't know where and how this gadget works, but, as I said, the problem is with the CharInsert extension. Not a gadget, but a real extension developed by WMF employees, hosted on Git. (See link above.) So I won't update anything as I have no right to do that. (P.S. I forgot to mention a wiki where the bug does occur: e.g. huwiki.) --Tacsipacsi (talk) 12:29, 12 November 2017 (UTC)

:As far as I know, this (and many similar problems) would also be solved by making WikEd compatible with jQuery.textSelection. Helder 11:24, 19 November 2017 (UTC)

::Why is there not even a response or acknowledgement of the problem? Or is it not regarded as a problem at all? —Loginnigol 17:21, 3 December 2023 (UTC)

WikEd blocks the keyboard shortcuts on Google Chrome. Is there a work around?

question also found here:

[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#WikEd_blocks_the_keyboard_shortcuts_on_Google_Chrome_and_Firefox.] (until archived)

I created a video - https://www.youtube.com/edit?video_id=11LoI-eSI1Y&video_referrer=watch

The shortcuts work on Firefox, but not on Google Chrome. Imaginelenin (talk) 19:47, 23 December 2017 (UTC)

: I've verified that the same thing happens in Chromium. The Transhumanist 07:30, 29 December 2017 (UTC)

Do you know how to use WikEd colors within [https://meta.wikimedia.org/wiki/Community_Tech/Wikitext_editor_syntax_highlighting#Color_and_style_customization Syntax highlighting]?

Doc James (talk · contribs · email) 01:50, 24 December 2017 (UTC)

WikEd has a very nice tool for fixing Unicode characters, but there is a bug that make it practically unusable.

All occurences of the sequence of characters "uad" as in "squad" is replaced to ­ (soft hyphen) and then words like "squad" become "sq­".--Luizdl ^Talk 16:14, 7 January 2018 (UTC)

I love WikiEd and use it every day. And when I do, other editors come on by and reformat the references. The funny thing is that each of the articles I edit with WikiEd gets formatted from the WikiEd reference formatting inconsistently to a variety of other preferred formats by other editors. I stopped caring a while ago but what a waste of time. What actually means that sometimes editors come on by to format refs one way and another follows and re-formats the refs another. I personally believe it to be a waste of time to make such tidy formatting changes, but hey! It's WP and anyone can edit the encyclopedia any way they would like. I guess in my perfect version of WikiEd, editors could sail on by and select a citation style they prefer. So if there was a change that could be made it would be to give referencing options for other editors so they could be able to reformat all the references in an article into their preferred formats. Best Regards, Barbara (WVS) ✐  ✉ 14:44, 14 January 2018 (UTC)

:[https://en.wikipedia.org/w/index.php?title=Urogenital_fistulas&diff=next&oldid=821004625 Here] is the perfect example of what I am talking about. Barbara (WVS) ✐  ✉ 15:23, 18 January 2018 (UTC)

Using wikEd 0.9.155 (November 5, 2017) on Chrome browser: From my sandbox, when I go to fullscreen mode, the left Wikipedia column text (the column that's common to all en.wikipedia.org articles) interferes with the view of wikEd toolbar and editing window.

(I took a screenshot of the same problem when doing this bug report in full screen, but I cannot yet figure out how to insert the image - sorry.) -- Bwefler (talk) 04:16, 22 January 2018 (UTC)

:Here is a screenshot of the bug report with the interference. -- Bwefler (talk) 04:53, 22 January 2018 (UTC)

thumb

:Operating system: Windows 10 (version 1709, OS build 16299.192) (Hope the wikEd build is the most recent—just selected it from Gadgets and started using it yesterday.)-- Bwefler (talk) 17:12, 22 January 2018 (UTC)

:This also happens for me. I'm on Windows 10 64-bit using Firefox 68.2.0esr (32-bit). FWIW, I've noticed this problem for several years. —danhash (talk) 16:26, 6 December 2019 (UTC)

Hi guys, I'm trying to get the WikEd extension to appear on Wikia sites, but I'm not sure if it's skin specific. I've tried disabling syntax colours and other editing stuff but nothing worked. Help is greatly appreciated! --Tenryuu (talk) 02:54, 19 March 2018 (UTC)

Can WikEd perform macros? There are some functions that I'd like to perform with one button click. --Tenryuu (talk) 00:43, 29 March 2018 (UTC)

: {{u|Tenryuu}}, it is possible to create custom buttons, see User:Cacycle/wikEd_customization#Custom_buttons. This requires some JavaScript savvy, though. GregorB (talk) 12:52, 18 June 2018 (UTC)

Wanting to get auto-updates.

https://en.wikipedia.org/wiki/User:Cacycle/wikEd_installation#Site-wide_installation

thx

--Johnywhy (talk) 03:09, 13 April 2018 (UTC)

:It is needed for offline version only. If you have a stable internet connection (as is the case almost always), you don’t need it. You will always load the latest version. —Tacsipacsi (talk) 11:21, 21 April 2018 (UTC)

I found the instructions a bit confusing re sitewide install-- seemed in one place i only needed your install script, but elsewhere it seemed that i was required to place the entire codebase into common.js.

Both worked. — Preceding unsigned comment added by Johnywhy (talk • contribs) 06:06, 13 April 2018 (UTC)

:Copying the entire codebase is only required if you don’t have a stable internet connection (and the wiki is not accessed through the internet, e.g. runs on the local machine or somewhere on the local network). —Tacsipacsi (talk) 11:26, 21 April 2018 (UTC)

{{ping|Cacycle}} I've translate it to Indonesian language, you can find the translation here. -- Bagas Chrisara (talk) 11:34, 18 April 2018 (UTC)

'xyz'.replace(/x(y|(no match))(z)/g, function(p, p1, p2, p3) { alert(p2==undefined); }); yields p2 as undefined on Pale Moon, Firefox, and Chrome.

It looks like wikEd.FixRedirectReplace is a victim if (linkText !== '') { (linkText is looks to be undefined. — Dispenser 21:45, 12 May 2018 (UTC)

: Here what needs to be added:

:

// Add fallbacks in wikEd.FixRedirectReplace()

var fragmentId = p5 || p14 || "";

var linkText = p7 || p16 || "";

:Which fixed it Dabfix. — Dispenser 23:44, 12 May 2018 (UTC)

wikEd.LinkInfoCall does not batch the titles it passes to the API. This results in it only checking the first 50 (500 for admins) links/images/templates/etc on the page, and triggering the "too-many-titles-for-query" warning from the API if it's attempting to check more.

To avoid this, you'll need to split the titles into batches and make an API query for each batch. You could do batches of 50 always, or you could increase the batch size to 500 if the user has the apihighlimits right.

FYI I'm planning on turning that warning into an error soon, at which point wikEd's redirect checking will break entirely on pages with too many links/images/templates/etc until this issue is fixed.

Thanks! BJorsch (WMF) (talk) 20:56, 18 May 2018 (UTC)

: FYI, the changing of the warning into an error is now scheduled for 1.32.0-wmf.6, which should be deployed here on May 31. Anomie⚔ 12:52, 23 May 2018 (UTC)

I found [http://cacycle.altervista.org/wikEd-diff-tool.html Online wikEd-diff-tool] and it is great!

It would be superb if made into a Talk page template that might be dropped into a contentious section, enabling pacification of edit warriors. Keeping Talk page section size (with margins and chrome) and screen size in mind, default would be one article section of existing article or x# of words max.

Alternatively, perhaps simpler, would it be possible to extend existing Online wikEd-diff-tool functionality by either::

1. generating a URL link to a particular diff (preferred), or
2. exporting to clipboard &/or text file of color-coded diff wikitext, for paste back onto Talk page to show effect of proposed additions, deletions, and block moves. Footer bar for color-coded legend.

(If 1, additional note on restful URL, following toolname base URL: PAGENAME#SECTION-DATETIME perhaps ideal, if navigation to &/or paste of article section name allowed; otherwise just DATETIME, if unidentified text copy pasted)

As is, it requires each interested editor to: perform two copy and pastes, switching back and forth between Talk page proposed text, online tool, article text, back to tool, and then back to Talk page to maybe say what they saw, what they liked and why, and what they didn't like and why -- each and every time they want to compare two versions. That ain't happening on the flaming pages I've visited over the years: not known (why a Talk page template would increase use and visibility far more than alternatives 1 & 2), too laborious, and not verifiable without repeating each step.

Even if it did happen, seeing is believing. This enhancement proposal, like your diff tool when used, has the potential to quench a lot of fires. Thanks for your hard work! -- Paulscrawl (talk) 16:06, 19 May 2018 (UTC)

Been having a problem over the last two weeks with wikiEd running paragraphs together and inserting extraneous newlines. Running with Vector in Firefox on Windows and MacOS Hawkeye7 (discuss) 05:16, 30 May 2018 (UTC)

:: I get the same with Firefox, Monobook, Windows 10. The item in the next section below is the same. Chiswick Chap (talk) 12:05, 30 May 2018 (UTC)

:: Same here. The annoying part is that these newlines are initially not visible, at least not until one clicks on "Preview". When copy-pasting, one is therefore forced to preview the changes first and delete the superfluous newlines before saving. No such behavior with Chrome 67.0.3396.79. GregorB (talk) 08:49, 12 June 2018 (UTC)

{{u|Hawkeye7}}, {{u|Chiswick Chap}} - things did not get better I presume? For me, it's as if it has gotten worse: paragraphs stick together and there is no way to separate them other than turning wikEd off. GregorB (talk) 09:55, 7 July 2018 (UTC)

:You can use the preview function to look at them, then go back in and insert additional newlines so it looks right. There are two related problems: it also inserts newlines when you don't want them; and the cursor insertion point is frequently wrong. In the Mac I've switched to Safari, which doesn't have the problem. I hoped that Firefox 61 would fix the problem., but it doesn't. Hawkeye7 (discuss) 11:04, 7 July 2018 (UTC)

::Preview doesn't work for me anymore - newlines inserted in preview now disappear when the page is saved. GregorB (talk) 11:51, 7 July 2018 (UTC)

::: I noticed things changing but getting more confused rather than actually better - I had the impression that several fixes had been attempted, none of which got to the root of the problem; and like other editors, I have found it a continuing source of difficulty. Chiswick Chap (talk) 08:15, 10 July 2018 (UTC)

::::{{replyto|Chiswick Chap}} FYI, no significant changes have been made to wikEd since November 2017. The primary maintainer of the code has not really been active since then. —TheDJ (talk • contribs) 07:26, 11 July 2018 (UTC)

::::: Well, as a user all I can say is that over the past ten years, it's worked really well, and in the past few months, something really odd has happened with it. Perhaps the issue is not with wikEd but with something that it interfaces with (maybe some interfaces have been helpfully updated, and the lack of wikEd maintenance has meant it hasn't kept up), I have no way of knowing, but wikEd no longer behaves as it did, as I and others have truthfully reported. Chiswick Chap (talk) 07:34, 11 July 2018 (UTC)

::::::I'm not disputing your claim, other than the "I had the impression that several fixes had been attempted"-part. —TheDJ (talk • contribs) 08:06, 11 July 2018 (UTC)

:::::: This is all caused by Firefox updates. IIRC, new releases of Firefox broke the c/p and newline behavior at least 3 or 4 times. I imagine this is not easy to fix at all, particularly while maintaining compatibility with Chrome. Unfortunately wikEd is borderline usable for me at the moment, I have to keep it switched off half the time. GregorB (talk) 08:22, 11 July 2018 (UTC)

I'm experiencing these issues, too, using Win10 and Firefox 61 (64-bit). The random, (but frequent) insertion of extraneous newlines is "relatively new" (I think – I've been inactive, so it could be years old), as is the (rare) "sticking together" of 'graphs (workaround seems to be to insert an HTML comment on it's own line in between the 'graphs). The insertion of a newline in front of pasted text and inconsistent failure of {{Key|BS}} and {{Key|DEL}} to delete it (i.e. re-join the lines), is pretty old. I really like WikEd, and don't want to have to switch to something else. Are there any plans to work on it? —[AlanM1(talk)]— 08:02, 15 August 2018 (UTC)

:I'm bumping this topic - unfortunately there seems to be no progress, and it's been months now since I've disabled wikEd due to this issue (i.e. messing up newlines while doing most non-trivial edits). I really hope it gets fixed some day - no wikEd for me in the meantime, regrettably (I do turn it on temporarily, for certain edits, but that's all). GregorB (talk) 12:18, 28 November 2018 (UTC)

::Is it possible that this issue relates to the Firefox config editor.use_div_for_default_newlines which defaults to true? Changing it to false as Firefox offshoots like Waterfox & Pale Moon have as the default value seems to take the problem away for me. Nthep (talk) 15:35, 24 May 2019 (UTC)

::: I've tried it and it seems to work for me! Thanks! GregorB (talk) 16:40, 24 May 2019 (UTC)

::::This issue has been reported several times; see #paragraph errors and #wikEd bug report: blank lines deleted. editor.use_div_for_default_newlines is indeed the solution. Pol098 (talk) 18:24, 24 May 2019 (UTC)

Please see this discussion Wikipedia:Village pump (technical)#Issue with editing - End of paragraph and "return". Please ping or respond there. Regards, Cinderella157 (talk) 06:05, 30 May 2018 (UTC)

: For what is worth, the linked section was archived as Archive 165. -- Rafaelff (talk) 13:11, 23 June 2019 (UTC)

Hi! Is there a way to stop wikEd from doing this: [https://en.wikipedia.org/w/index.php?title=Talk:Open_world&diff=844844219&oldid=844792062]. Upon editing the section, wikEd transforms the (what I assume is one of the Unicode white-) space character into the   ; entity. I tried disabling wikEd and I couldn't reproduce, so I assume it is part of wikEd logic. —  HELLKNOWZ   ▎TALK 10:30, 10 June 2018 (UTC)

:{{ping|Hellknowz}} this issue has been discussed above (see the section "Stop adding ..."), but with no solution on wikEd's side so far. Can't really help with the issue itself (I am only another user of this great tool) - just adding this note here for your information in the meantime. GermanJoe (talk) 09:34, 7 July 2018 (UTC)

::Oh, whoops, I didn't see that. I quickly scanned the previous sections but must have missed it. Thanks for the pointer. —  HELLKNOWZ   ▎TALK 10:39, 7 July 2018 (UTC)

Observed in Chrome 67. Best --FriedhelmW (talk) 10:16, 12 June 2018 (UTC)

This is caused by wikEd, see Wikipedia:Village pump (technical)#Left hand column with menu (Main page, contents, languages etc) showing while in edit field stopping me from saving. Doug Weller talk 14:40, 18 June 2018 (UTC)

:{{replyto|Doug Weller}} did you accidently turn on wikEd's Fullscreen mode ? it's known to be broken. —TheDJ (talk • contribs) 10:30, 23 June 2018 (UTC)

::{{re|TheDJ}} I clicked on a box that says "use wikEd instead of classical text area. That's from an edit screen that has a top menu starting with B I and ending with cite, a dropdown template box, Named references and Error check under that, and at the right and lower down a small grey box with 2 rows, the first row starting with a click box to turn on simple view. I find this setup very useful, but I miss the search and replace I used to be able to get. Thanks. Doug Weller talk 10:45, 23 June 2018 (UTC)

{{edit fully-protected|User:Cacycle/wikEd.js|answered=yes}}

I recently changed my username. Please change User:Aftabuzzaman/ to User:আফতাবুজ্জামান/ in the code. Thanks. --আফতাব (talk) 16:25, 25 June 2018 (UTC)

:File:Yes check.svg Done — Martin (MSGJ · talk) 07:17, 26 June 2018 (UTC)

WikEd interferes with the syntax highlighting provided by :mw:Extension:CodeMirror. Whenever both the gadget and the extension are enabled, users write in the wrong text box without any clue of what is happening and why they're not saving anything. Could someone please prevent that by updating the script to check whether the wikitext editor contains a div with class "CodeMirror"? A solution could be like a popup explaining that CodeMirror must be disabled to make WikEd work.--Sakretsu (talk) 23:06, 13 September 2018 (UTC)

File:MovingProblem3.jpg

The little pencil on a piece of paper in the right upper hand corner loads slower than the rest of the page. When it loads it shifts everything over resulting in misclicks. Wondering if you can hold a space for the icon so that shifting does not occur? Discussion was [https://en.wikipedia.org/wiki/Wikipedia_talk:Twinkle/Archive_39#Button_load_issues here] for a similar issue that occured with another button. Fix was by User:MusikAnimal Doc James (talk · contribs · email) 01:15, 27 September 2018 (UTC)

::Wondering if anyone has had a chance to look at this? User:ערן or User:Ladsgroup? Doc James (talk · contribs · email) 16:46, 21 October 2018 (UTC)

:::User:ערן, User:Ladsgroup, User:MusikAnimal another year and a bit has passed. I am happy to ask User:Fz-29 to take a look at seeing if he can fix this but I think MusikAnimal fixed the last ones.

:::Either hold a space for the wikEd icon or move it to the left of the user name. Doc James (talk · contribs · email) 14:17, 27 February 2019 (UTC)

::::Okay have asked User:Fz-29 if he can figure out how to fix this. Doc James (talk · contribs · email) 10:41, 2 March 2019 (UTC)

On some wikis that use darker skins (and contrasting bright text), the editor appears to use its own skin and causes the text to become near unreadable such as [https://snag.gy/rOMyJ6.jpg here] (The Cancel text, "This is a minor change", and "Watch this page" are legible only when highlighted). Is there a solution to this? — Preceding unsigned comment added by Tenryuu (talk • contribs) 16:09, 5 October 2018 (UTC)

I've tried to follow instructions reporting this. I do the control-click and I get a message box with useful information. I cannot figure out how copy the contents of this box to paste here. I am using Chrome on Windows 10. Let me know what I can try here to get this information to you.

I have accidentally activated full screen mode. As reported above this creates a messy situation and so obviously you don't want to use this feature. The problem is I am unable to get out of full screen mode. I can disable WikEd using the button I control-clicked on above. When I re enable, it is not in full screen mode but the full screen mode button is pressed and I can't unpress it. WikiEd is now coming up in this unusable full screen mode by default.

The documentation says there is a cookie associated with this mode and I have searched my cookies but there are a lot of cookies on my computer and I can't find what I'm looking for. ~Kvng (talk) 16:32, 10 November 2018 (UTC)

Clearing my browser cookies has resolved this. Full screen mode is to be avoided. ~Kvng (talk) 16:31, 29 December 2018 (UTC)

It seems the last version is not working correct any more!

When i enter empty lines to get an paragraph, they are disappearing when saving.

This is happening random in different lines.

For me this Editor is not usable any more. — Preceding unsigned comment added by 89.0.185.231 (talk) 09:29, 28 November 2018 (UTC)

: See #wikiEd running paragraphs together and inserting extraneous newlines above. GregorB (talk) 12:19, 28 November 2018 (UTC)

: O.K. Where can i find the last version before that was working without this problem?

: Then i would try to make an local installation of wikEd of this version.

:: My guess is that the problem was actually caused by a new version of Firefox (I'm assuming here you use Firefox). If that is true, the solution is rather to:

::# Use Chrome (no problems in Chrome, as far as I can tell), or

::# Downgrade Firefox to a sufficiently old version (I'm guessing 59) that does not cause this behavior.

::Unfortunately, none of the above is really an option for me. GregorB (talk) 20:09, 17 December 2018 (UTC)

::: Thank you for your answer and your work at wikEd!

::: Indeed i am using Firefox under Debian 8 and it has get an security update to Firefox 60.4.0.esr.

::: There are additional other problems with Firefox, like etherpad is not working any more.

::: It seems really that Firefox is not usable any more :-(

::: But [https://sputniknews.com/science/201804041063197557-chrome-files-scanning-concerns/ Chrome Spyware] can't be really the alternative.

{{Outdent|:::}}This has been reported in other sections; the solution has just been posted in a previous section:

{{quotebox|text=This issue relates to the Firefox config editor.use_div_for_default_newlines which defaults to true. Changing it to false ... takes the problem away for me. Nthep (talk) 15:35, 24 May 2019 (UTC)}} Pol098 (talk) 18:24, 24 May 2019 (UTC)

[Added April 2019: this seems to be the same issue as reported in the previous section, "paragraph errors"]

Issue which may be due to WikEd: with 32-bit Firefox (FF) under Windows10/64 (both up-to-date as of 23Ja19), since a few months ago (with several updates to FF and Windows), blank lines are squeezed out when saving edited Wikipedia pages. This was [https://en.wikipedia.org/wiki/Wikipedia:Help_desk/Archives/2019_January_23#Bug_when_editing_-_closes_up_spaces reported by another user on 23 Jan 19]. In my experience the problem manifests under FF but not Google Chrome (I haven't tested other browsers, but expect they're OK) if WikEd is enabled, but not if WikEd is turned off. Syntax highlighting is enabled.

Issue: when editing a Wikipedia page, if carriage return is pressed twice at the end of a paragraph and more text typed, it should appear below with one intervening blank line. What actually happens is that the edited text appears in the editor as normal, but on saving (or previewing) the new text follows immediately after the existing text, with no blank line. This happens when entering new text or editing existing text. If I paste text with line breaks from a text editor, it seems to be OK. Existing text which I haven't edited does not have this problem.

With FF32, Win10/64, WikEd enabled, edit section Halogen lamp#Phase-out. Position the cursor at the end of text. Press CR twice, and type a line of text. Press CR twice and type another line. Press CR 3 times (2 blank lines), and enter a last line. Click preview.

What shows on the screen, correctly, before the preview:

vvvvvvvvvv

[blah blah] August 2018}}

This is the first test line, preceded and followed by 2 CRs

This is another line, followed by 3 CRs (2 blank lines)

This is the last line.

^^^^^^^^^^

After the preview, in edit mode (I've typed in breaks to show the editor page):

vvvvvvvvvv

[blah blah] August 2018}}

This is the first test line, preceded and followed by 2 CRs

This is a another line, followed by 3 CRs (2 blank lines)

This is the last line.

^^^^^^^^^^

The saved/previewed text runs on without paragraph breaks, of course.

• Date: 2019-01-26 15:34:24 UTC
• wikEd version: 0.9.155 (November 5, 2017)
• Browser: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 (Win32)
• Skin: vector (detected: vector_new)
• MediaWiki: 1.33.0-wmf.14
• Gadgets:
• MediaWiki scripts: RefToolbar.js, RefToolbarMessages-en.js, RefToolbarConfig.js
• Scripts: User:Ucucha/duplinks.js, User:Markhurd/hidetopcontrib.js, User:Cacycle/wikEd.js, User:Evad37/duplinks-alt.js, User:Cacycle/diff.js, User:Cacycle/wikEdDiff.js
• URL: https://en.wikipedia.org/w/index.php?title=Halogen_lamp&action=edit§ion=2
• User subpages: https://en.wikipedia.org/wiki/Special:PrefixIndex/User:Pol098/
• User/skin.js: https://en.wikipedia.org/wiki/User:Pol098/vector.js
• User/common.js: https://en.wikipedia.org/wiki/User:Pol098/common.js
• Error console: ____ (Firefox: Tools → Web Developer → Browser console; push clear and reload the page. Chrome: Control button → Tools → JavaScript console. Copy and paste error messages related to wikEd.js)
• Problem description: Described above
• Steps to reproduce: Described above

;Phase-out (this is the short section I use as a reproducible example)

In 2009, the EU began its phase-out of inefficient bulbs. The production and importation of directional mains-voltage halogen bulbs was banned on 1 September 2016 and non-directional halogen bulbs followed on 1 September 2018.{{cite web|url=https://www.lyco.co.uk/advice/the-light-bulb-phase-out-schedule/|title=The light bulb phase out schedule / Lighting Advice - Lyco|author=|date=|website=www.lyco.co.uk|accessdate=30 April 2018|deadurl=no|archiveurl=https://web.archive.org/web/20171027025028/https://www.lyco.co.uk/advice/the-light-bulb-phase-out-schedule/|archivedate=27 October 2017|df=}} Australia will ban halogen light bulbs from September 2020.{{cite web|url=https://www.ledinside.com/news/2018/8/halogen_bulbs_to_be_banned_in_the_eu_market_from_september|title=Halogen Bulbs to be Banned in the EU Market from September - LEDinside|website=www.ledinside.com|accessdate=26 August 2018}}

{{Reflist-talk|title=}}

Pol098 (talk) 16:22, 26 January 2019 (UTC)

:===(New comment on bug)===

:I was just going through the preliminaries to reporting this myself, and am glad to see that {{u|Pol098}} has already done so - but thought that I may as well add the only differences in my environment compared to theirs (that I know of) - else all the same:

:*Browser: Firefox 64.0.2

:*Gadgets: Twinkle. (Don't know of any scripts, apart from WikEd?]

:*URLs - multiple. Most recently https://en.wikipedia.org/w/index.php?title=Zip-line&action=edit

:*I found it impossible to reproduce consistently, sorry - but I think that it may only happen with Syntax Highlighting (sometimes).

:I must also add the link to my [https://bugzilla.mozilla.org/show_bug.cgi?id=1522378 BugZilla report], which I made before before the suggestion from Pol098 that it was related to WikEd. They're asking for further info there now but I might just point them at this entry. Laterthanyouthink (talk) 06:02, 28 January 2019 (UTC)

::Additional issue: sometimes an unwanted blank line is inserted. In particular, when adding text with several points preceded by "*" there should be no blank lines between the items. I was careful not to type in unnecessary CRs (and the edit page did not show any before saving), but found that blank lines had been inserted between several (but not all!) pairs of items. Pol098 (talk) 20:26, 29 January 2019 (UTC)

:::I suggested a few workarounds on the WP:Help page cited; here they are:
1: after a paragraph I press Enter twice or more, then
, then Enter once or twice more, followed by more text. I preview the result, and find that most line breaks have been removed, but typically there is
on a line by itself, followed by one or more blank lines (sometimes there is a blank line before the
). I put the cursor on the last blank line, and backspace to delete all except the first blank line. When I save that it is usually OK.
2: I open the page in Google Chrome, which does not have this problem, if necessary copying the page in edit mode with my edits from Firefox.
3: I think that copying the edit page into a text editor (Notepad++), getting the blank lines right, and copying back, works. I don't remember as I rarely do this.
Note: the obvious trick of adding a line containing one space—CR, space, CR, instead of CR, CR— adds two blank lines instead of one, though one can then be deleted. Pol098 (talk) 16:04, 3 April 2019 (UTC)

::::10 May 19 update: I have the impression that the problem has got slightly worse with the release of Firefox 66.0.5 (32-bit in my case). Inserting blank lines and
s, previewing, and deleting redundant blanks and breaks sometimes doesn't work unless more blank lines than previously needed are added. Whether this whole issue is due purely to FF, or WikEd has a part, I can't say. Pol098 (talk) 14:53, 10 May 2019 (UTC)

{{Outdent|::::}}SOLVED I hadn't spotted it, but this is the same issue already reported. The solution has just been posted in that section:

{{quotebox|text=This issue relates to the Firefox config editor.use_div_for_default_newlines which defaults to true. Changing it to false [in about:config]... takes the problem away for me. Nthep (talk) 15:35, 24 May 2019 (UTC)}}

This has worked for me too (on a quick test, but no reason to doubt it). Pol098 (talk) 18:13, 24 May 2019 (UTC)

:{{Ping|Randykitty}}, this will interest you, i think. Headbomb {t · c · p · b} 19:42, 24 May 2019 (UTC)

:::Thanks, trying this out now! --Randykitty (talk) 18:11, 26 May 2019 (UTC)

::Changing editor.use_div_for_default_newlines from true to false in Firefox is the fix, but if anyone wants to know the detail: this is entirely down to Firefox, nothing at all to do with WikEd. A few revisions ago Firefox decided to change the default way its rich text editor rendered a paragraph break. The change is described [https://www.fxsitecompat.com/en-CA/docs/2018/rich-text-editor-s-newline-behaviour-has-been-changed-now-generates-div-instead-of-br/ here]. 'If you type “Firefox” and hit Enter between “Fire” and “fox”, the result HTML would be

:{{Ping|DannyS712}} this might be something for the Script++ newsletter / Signpost tech news. Headbomb {t · c · p · b} 23:13, 24 May 2019 (UTC)

If I have both wikEd and Wikipedia:Citation expander enabled, the Citation expander gadget doesn't work. Disabling wikEd solves this, but then I lose wikEd. Headbomb {t · c · p · b} 05:34, 28 February 2019 (UTC)

:{{u|Headbomb}}, citation expand doesn't support jQuery.textSelection (the abstraction layer which allows multiple tools to edit wikitext content at the same time). wikEd only supports it partly. Citation expander also doesn't work with WE2017 for this reason. —TheDJ (talk • contribs) 08:12, 4 April 2019 (UTC)

Love this tool! Any plans to extend WikEd to the source editor of the new editor? -Furicorn (talk) 08:25, 24 March 2019 (UTC)

:{{u|Furicorn}}, which features of wikEd do you miss in WE2017 ? Have you considered filing bugreuports to have those officially supported by WE2017 ? —TheDJ (talk • contribs) 08:13, 4 April 2019 (UTC)

::{{u|TheDJ}} I immediately missed the functionality of using ctrl-click to follow a link in the edit window (it's especially useful for trying to fix templates). I submitted some feedback [https://www.mediawiki.org/wiki/Topic:Uwmpf7ysbq4243bn here], but I would be happy to submit a further bugreport if I knew how to or where. -Furicorn (talk) 11:54, 4 April 2019 (UTC)

Wikia recently change their domain from Wikia to Fandom

https://community.fandom.com/wiki/Help:Fandom_domain_migration

And they remove their own Monobook skin long time ago

https://community.fandom.com/wiki/Thread:1456214

I can't find a way to make your code run in my wiki anymore. Can you take a look at their site and make a fix? Thank you 117.4.253.117 (talk) 03:33, 14 June 2019 (UTC)

Please have a look at this line:

if ( ( wikEd.wikiGlobals.wgEnableAPI === true ) || ( wikEd.wikiGlobals.wgEnableAPI === 'true' ) && ( livePreview === true ) ) {

Because of the boolean priority, and because wgEnableAPI is always true (but this will change soon, see Tech News 2019-25), the conditional is always true and the according branch is executed, whether livePreview is true or false.

So there are two things to review and eventually fix:

• the conditional / code branching (until now, the first branch was always executed, and the other branch was never executed… but no one complained?)
• wgEnableAPI shouldn't be tested against, as it will be removed soon (thus it won't equal true anymore).

Od1n (talk) 07:35, 19 June 2019 (UTC)

When I enable the "wikEd: alternative full-featured integrated text editor for Firefox, Safari, and Google Chrome (documentation)" gadget, I receive an edit conflict with about 75% (approximately) of my edits, even though the edit goes through. It might be interacting with another gadget I have enabled, or a script perhaps. I have tried in Chrome and Edge, on different computers in different locations. I had someone else try and they said they did not encounter the issue. Kees08 (Talk) 22:31, 10 August 2019 (UTC)

:Hm, I hadn't thought of that as the reason for my edit conflicts that aren't really edit conflicts. I've had the problem for weeks. Doug Weller talk 13:37, 11 August 2019 (UTC)

I have exactly the same problem running wikEd in Google Chrome browser under Windows 10 Pro (all always up to date). The problem began around mid-2019. I used the same setup for several years before mid-2019 with no false edit conflict notices. Do you have any idea what might have changed in wikEd, or in Chrome, to cause false edit conflict notices? Does the problem occur in other browsers?—Finell 05:58, 29 December 2019 (UTC)

Fine in Chrome. Just disappeared from Foxtrot. ¬¬¬¬ — Preceding unsigned comment added by Doug Weller (talk • contribs) 16:32, 11 August 2019 (UTC)

{{edit semi-protected|User:Cacycle/wikEd|answered=yes}}

Please add {{distinguish|Wikipedia:Wiki Ed}} at the top of the page. 83.31.194.166 (talk) 19:10, 11 October 2019 (UTC)

:File:Yes check.svg Done Sceptre (talk) 00:44, 12 October 2019 (UTC)

I'm on the latest Chrome version (78.0.3904.70) on Manjaro Linux.

Uncaught Error: Another textSelection API was already registered

at jQuery.fn.init.$.fn.textSelection (:39:865)

at Object.wikEd.TurnOn (index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:3842)

at Object.wikEd.Setup (index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:2396)

at Object.wikEd.Startup (index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:2080)

at index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:19215

:wikEd works for me, in Google Chrome browser under Windows 10 Pro, in Talk, Help, WP, and User namespaces (at least) in English Wikipedia and also in Meta-Wiki (meta.wikimedia.org). According to wikEd documentation, wikEd should work at any website that runs MediaWiki software.—Finell 06:11, 29 December 2019 (UTC)

WikEd can add or remove Wikilinks, which is very useful. To add a link, select a portion of text and mouse-click the Wiki link icon in the bar above WikEd (the first icon in the second row, for me at least). To remove a link, highlight a section of text with several links, then click the Wiki link icon, and all Wikilinks will be removed.

Accurate selection is required. It would be useful to add a little flexibility:

• If already linked text is clicked without the delimiting square bracket pairs, at present WikEd adds an extra "...". It would be useful to check if the text is already linked and, if so, delete the link as if the whole link, with delimiters, had been selected. E.g., if selecting {{font color, it would be useful for the Wiki link button to change this to "some text" (without brackets) rather than the present "[[some text]]". This would be particularly useful for single-word links: double-click to highlight the word to unlink without surrounding brackets, then click Wiki link button.
• Possibly if selection for unlinking is slightly inaccurate, with only one of the two square brackets selected, check for this possibility: treat "[{{font color|white|#00AAFF|[linked text]]}}" as "{{font color|white|#00AAFF|linked text}}"

Perhaps wait and see if others agree or disagree with this suggestion, then consider implementing it if reasonably straightforward?

Best wishes, Pol098 (talk) 14:06, 30 October 2019 (UTC)

I would like to see the feature "Capitalization of headers and lists" removed because it is capitalising things inappropriately like infobox parameters and headings that shouldn't be capitalised. This feature is also not helpful in any way and there are far too many false positives. [https://en.wikipedia.org/w/index.php?title=C8orf58&diff=prev&oldid=933426008 This capitalisation] of "mRNA" is inappropriate and I had to revert it in the next edit. The feature to convert HTML to wikicode is extremely helpful but the capitalisation feature is not at all helpful and should be removed. Pkbwcgs (talk) 09:29, 1 January 2020 (UTC)

:{{reply to|Pkbwcgs}} As described under User:Cacycle/wikEd_help#Fix, these buttons are to be used on selected text and not for unsupervised fixing of whole articles. Cacycle (talk) 07:36, 30 March 2020 (UTC)

I'm not sure if the Fandom domain has some sort of Javascript or other code that prevents the editor from appearing, but even after following the instructions for complete installation in my user page's common.js, I still can't get the WikEd toolbars to appear on any Fandom sites. Am I doing something wrong? --Tenryuu (🐲 • 💬 • 🌟) 07:50, 17 February 2020 (UTC)

:{{reply to|Tenryuu}} I see a warning “visit your preferences to switch to the old MediaWiki editor” on Fandom with JavaScript disabled. I don’t have a Fandom account, so I can’t use Special:Preferences; have you tried that? For me wikEd seems to load cleanly, but nothing appears, probably because there’s nowhere to add the wikEd UI to. —Tacsipacsi (talk) 17:09, 18 February 2020 (UTC)

::{{Re|Tacsipacsi}} Are you saying that you can't get the toolbars to appear? I don't see anything that allows me to switch to the old MediaWiki editor in my preferences. --Tenryuu (🐲 • 💬 • 🌟) 23:36, 18 February 2020 (UTC)

{{edit fully-protected|Template:WikEd|answered=y}}

Please add the closing {{tag|pre|c}} as shown in the sandbox. This should prevent the documentation from being formatted with the pre tag, and it removes a Linter error. Thanks. – Jonesey95 (talk) 19:02, 21 February 2020 (UTC)

:The suggested change would have included a stray </pre> which would have caused lint errors on the pages on which the template is substed. I've removed them entirely. --Izno (talk) 20:35, 21 February 2020 (UTC)

{{reply to|Cacycle}} hello, i have copied and pasted code given at https://en.m.wikipedia.org/wiki/User:Cacycle/wikEd_installation on https://meta.m.wikimedia.org/wiki/User:Leela52452/global.js. unfortunately, wiked is not working. Leela52452 (talk) 02:46, 30 March 2020 (UTC)

:{{reply to|Leela52452}} Is it working when using another browser (e.g. the default Android browser) or when using a different device or a PC? Then it is probably related to the cache not being cleared. Cacycle (talk) 07:14, 30 March 2020 (UTC)

:{{reply to|Cacycle}} i always clear private data on quit if i add or remove anything in js or css files. browser 5.1 [ preinstalled browser on device ] has same issue. Leela52452 (talk) 08:35, 30 March 2020 (UTC)

:{{reply to|Cacycle}} it is not working on browser 5.1. i had cleared all data using clear private data when quit before reporting. excuse for late reply, Leela52452 (talk) 00:49, 1 April 2020 (UTC)

::{{reply to|Leela52452}} Maybe because you use the mobile interface? The mobile editor is so different from the desktop one that the wikEd user interface would need to be almost rewritten from scratch to support it. There’s a “Desktop” link at the bottom of each page that lets you switch to the desktop view. wikEd should work there. (If you’d like to stick to the mobile view by default and switch to desktop view just sometimes, instead of the “Desktop” link, you can check the Request desktop site checkbox in Firefox’s three-dot menu, and then remove the “m.” from the domain in the URL bar, e.g. change https://en.m.wikipedia.org/wiki/User:Cacycle/wikEd to https://en.wikipedia.org/wiki/User:Cacycle/wikEd.) —Tacsipacsi (talk) 19:53, 1 April 2020 (UTC)

:{{reply to|Tacsipacsi}} activated as gadget. your suggestion using "desktop hyperlink" is working flawlessly. thank you. Leela52452 (talk) 06:06, 2 April 2020 (UTC)

Cacycle, have you ever looked into setting up Special:Tags for edits made in wikEd? AWB did it a while ago at phab:T111663. It could be an "advertising tool" for wikEd. I'm sure you remember the nbsp thing a couple of years ago, and I think we would have figured out what was going on sooner if we'd been able to see the editing tools that people were using. Ping me if you need help (or maybe talk to Reedy, who of course knows a lot more about how to do it than I do). I'd love to see tags on wikEd edits. Whatamidoing (WMF) (talk) 19:23, 31 March 2020 (UTC)

• Date: 2020-04-01 10:04:44 UTC
• wikEd version: 0.9.155 (November 5, 2017)
• Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36 (Win32)
• Skin: vector (detected: vector_new)
• MediaWiki: 1.35.0-wmf.25
• Gadgets:
• MediaWiki scripts: RefToolbar.js, RefToolbarMessages-en.js, RefToolbarConfig.js
• Scripts: User:Enterprisey/reply-link.js, User:Enterprisey/script-installer.js, User:Enterprisey/short-tab-titles.js, Wikipedia:AutoEd/complete.js, User:Evad37/MoveToDraft.js, User:Writ_Keeper/Scripts/teahouseUtility.js, User:Danski454/stubsearch.js, User:Pythoncoder/userHighlighter.js, User:Pythoncoder/Scripts/voteSymbols.js, User:David_Condrey/bookmarknav.js, User:Lourdes/AfDstarted.js, User:ZLEA/Dashboard.js, User:Omni_Flames/PendingChangesLink.js, User:The_Evil_IP_address/hdedit.js, User:Theopolisme/Scripts/autocompleter.js, User:Evad37/rater.js, User:Cacycle/wikEd.js, User:Cacycle/diff.js, User:Cacycle/wikEdDiff.js
• URL: https://en.wikipedia.org/w/index.php?title=Wikipedia:Clinic_for_Wikipediholics&action=edit
• User subpages: https://en.wikipedia.org/wiki/Special:PrefixIndex/User:Berrely/
• User/skin.js: https://en.wikipedia.org/wiki/User:Berrely/vector.js
• User/common.js: https://en.wikipedia.org/wiki/User:Berrely/common.js
• Error console: None related to WikEd.js
• Problem description: The first time I turned on WikEd, I noticed that the editor overlaps the sidebar, making it hard to read what it says. The white bit disappears, but the text still combines with the text in the editor.
• Steps to reproduce: I can't really explain how to reproduce, I just clicked the WikEd button!

:: Berrely: Thanks for reporting this, even when using your script settings. But I am also not sure sure, how the problem should look like. Do you still have this problem? Which sidebar are you talking about? Maybe you could post a screenshot? Thanks, Cacycle (talk) 11:57, 2 May 2020 (UTC)

:::{{u|Cacycle}}, sorry! For some reason, it fixed itself after a few days, but now another problem has arisen, for some reason, all edit notices are duplicated and there is a text saying "WikEd: Duplicated edit warning". — Yours, Berrely • ^Talk∕_Contribs 13:10, 2 May 2020 (UTC)

Hi, yet another post asking about the compatibility between this and Fandom. I recently installed Tampermonkey with the WikEd script. I went on some other wiki sites where I did not install the script as Javascript and confirmed that it works. It even works on Gamepedia, which is a property of Fandom. However it doesn't seem to work on anything that has "fandom" in its URL (e.g., [https://psychusa.fandom.com]). Anyone know why that is? Is the software somewhat different? --Tenryuu 🐲 ( 💬 • 📝) 22:29, 3 April 2020 (UTC)

Hi everyone. I recently switched skins and was wondering if WikEd supports the Timeless skin. The gadget is still active but the toolbars don't come up. —Tenryuu 🐲 ( 💬 • 📝 ) 19:33, 10 May 2020 (UTC)

• wikEd version: latest one
• Browser id: Google Chrome 81.0.4044.138
• Operating system: Windows 10
• Wikipedia skin: Vector or Monobook, doesn't seem to matter
• User scripts that you have installed on your Special:Mypage/skin.js and Special:Mypage/common.js pages (if any): On Wikipedia I have loads of scripts installed, on this new wiki I have none. Issue happens on both.
• Gadgets that you have checked in your preferences. Optional: What happens if you disable these gadgets: Wikipedia: loads, new wiki none
• Web address (URL) of the page or wiki installation where you experience your problems: Wikipedia and https://wiki.endmyopia.org

The following doesn't happen in Firefox. I go to my sandbox page and try to save an edit, this generates an edit conflict 25-50% of the time. This happens on all articles across the wiki. It doesn't happen if wikEd is disabled. Not sure if anyone else is also having this issue. -NottNott 11:57, 23 May 2020 (UTC)

due to capitalisation, the references will be unusable. i have tested with greasemonkey version ( firefox for android 68.9.0) on [https://pt.m.wikipedia.org/wiki/Wanda_Zab%C5%82ocka wiki page] 2401:4900:33AC:9AB3:1:0:BBAC:6075 (talk) 15:28, 10 June 2020 (UTC)

if wiked is using awb RegExTypoFixto fix typos, if possible, can u please enable it on greasemonkey user script 2401:4900:33AC:9AB3:1:0:BBAC:6075 (talk) 16:07, 10 June 2020 (UTC)

As the [report on Phabricator https://phabricator.wikimedia.org/T256191]. The replace field WikEd floats up when key the characters. --Koala0090 (talk) 04:01, 24 June 2020 (UTC)

We are currently in the process of rolling out client side error tracking on all Wikimedia wikis. Due to concerns around volume we are limited about where we can roll it out, by making sure bugs get addressed and squashed.

This script appears to be widely used and is generating the following error when toggling the controlButtons. Can somebody please look into this error? Thanks in advance! Jdlrobson (talk) 18:44, 3 September 2020 (UTC)

Uncaught TypeError: buttonsWrapper is null

ButtonBarGripHandler https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:4618

TurnOn https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:3741

Setup https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:2396

Startup https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:2080

https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:19212

I am getting this bug when I open the URL https://he.wikipedia.org/w/index.php?title=%D7%99%D7%A9%D7%A2%D7%99%D7%94%D7%95_%D7%A9%D7%A4%D7%99%D7%A8%D7%90&action=edit

Browser: Firefox. Stack trace is below.

Jdlrobson (talk) 21:37, 4 September 2020 (UTC)

jQuery.Deferred exception: wikEd.frameBody is null wikEd.UpdateTextarea@https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:16407:3 getContents@https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:3840:14 $.fn.textSelection@https://he.wikipedia.org/w/load.php?lang=en&modules=ext.TemplateWizard%2Ccharinsert%2CeventLogging%2CnavigationTiming%2Cpopups%2CwikimediaEvents%7Cext.TwoColConflict.JSCheck%7Cext.centralNotice.geoIP%7Cext.centralauth.ForeignApi%7Cext.centralauth.centralautologin.clearcookie%7Cext.cx.entrypoints.contributionsmenu%7Cext.cx.eventlogging.campaigns%7Cext.cx.widgets.callout%7Cext.echo.api%2Cinit%7Cext.growthExperiments.SuggestedEditSession%7Cext.uls.common%2Ccompactlinks%2Cinit%2Cinterface%2Cpreferences%2Cwebfonts%7Cext.wikimediaEvents.loggedin%7Cjquery%2Cmoment%2Coojs%2Coojs-ui-core%2Coojs-ui-toolbars%2Coojs-ui-widgets%2Coojs-ui-windows%2Csite%7Cjquery.client%2Ccookie%2ChighlightText%2ClengthLimit%2CmakeCollapsible%2Csuggestions%2CtextSelection%2Cthrottle-debounce%2Ctipsy%2Cui%7Cjquery.makeCollapsible.styles%7Cjquery.uls.data%7Cmediawiki.ForeignApi%2CString%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2CconfirmCloseWindow%2Ccookie%2Cexperiments%2Cicon%2CjqueryMsg%2Clanguage%2Cstorage%2Ctemplate%2Cuser%2Cutil%2Cwidgets%7Cmediawiki.ForeignApi.core%7Cmediawiki.action.edit%7Cmediawiki.action.edit.collapsibleFooter%2CeditWarning%7Cmediawiki.diff.styles%7Cmediawiki.language.specialCharacters%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.page.watch.ajax%7Cmediawiki.ui.button%7Cmediawiki.widgets.DateInputWidget%2CUserInputWidget%2CvisibleLengthLimit%7Cmediawiki.widgets.DateInputWidget.styles%7Coojs-ui-toolbars.icons%7Coojs-ui-widgets.icons%7Coojs-ui-windows.icons%7Coojs-ui.styles.icons-content%2Cicons-editing-advanced%2Cicons-editing-citation%2Cicons-editing-core%2Cicons-editing-list%2Cicons-editing-styling%2Cicons-interactions%2Cicons-media%2Cicons-movement%7Cskins.vector.legacy.js%7Cuser.defaults%7Cwikibase.client.action.edit.collapsibleFooter&skin=vector&version=1jt8j:778:237 modules/ve-mw/preinit/ve.init.mw.DesktopArticleTarget.init.js/

Do you have any idea why all edit notices are duplicated with the caption {{tq|Duplicated edit warnings (wikEd):}}? Any help much appreciated — Yours, Berrely • ^Talk∕_Contribs 09:23, 5 September 2020 (UTC)

: Since you are scrolled down the page to the edit box when editing with wikEd, could easily not see the one at the top of the page. — JJMC89 (T·C) 17:24, 6 September 2020 (UTC)

• Date: 2020-09-19 03:11:43 UTC
• wikEd version: 0.9.155 (November 5, 2017)
• Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0 (Win32)
• Skin: vector (detected: vector_new)
• MediaWiki: 1.36.0-wmf.9
• Gadgets:
• MediaWiki scripts:
• Scripts: User:Markhurd/hidetopcontrib.js, User:Chris_the_speller/script/ScriptA.js, User:Ohconfucius/script/MOSNUM_dates.js, User:PleaseStand/userinfo.js, User:Cacycle/wikEd.js, User:Pathoschild/Scripts/Regex_menu_framework.js, User:Cacycle/diff.js, User:Cacycle/wikEdDiff.js, https:/api.php
• URL: https://en.wikipedia.org/wiki/User_talk:Cacycle/wikEd
• User subpages: https://en.wikipedia.org/wiki/Special:PrefixIndex/User:Chris_the_speller/
• User/skin.js: https://en.wikipedia.org/wiki/User:Chris_the_speller/vector.js
• User/common.js: https://en.wikipedia.org/wiki/User:Chris_the_speller/common.js
• Error console: ____ (Firefox: Tools → Web Developer → Browser console; push clear and reload the page. Chrome: Control button → Tools → JavaScript console. Copy and paste error messages related to wikEd.js)
• Problem description: When editing a page with wikEd, there are two boxes: a plain one and also one below it with an "X" for clearing any text in it. I don't know which box really works. It sometimes causes me to log edits that have no summary. This only appeared a day or two ago.
• Steps to reproduce: Editing a page without wikEd, only one box for edit summary appears. Turn on wikEd, and there are two boxes: a plain one and also one below it with an "X" for clearing any text in it. Chris the speller ^yack 03:20, 19 September 2020 (UTC)

::A workaround (and maybe a clue): with wikEd off, edit a page, then turn wikEd on. No double box. If wikEd is already selected when you start to edit a page, then you get two boxes. Chris the speller ^yack 04:28, 19 September 2020 (UTC)

:::{{reply to|Chris the speller}} Jon (WMF) [https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&diff=979408145&oldid=979075361 changed the script], is it better now? —Tacsipacsi (talk) 00:20, 21 September 2020 (UTC)

::::No, it still shows two boxes for edit summary, sometimes. Is there some kind of refresh I need to do? All day I have seen the problem on and off, but I have never seen it when wikEd was turned off. Chris the speller ^yack 01:00, 21 September 2020 (UTC)

:: I believe I can replicate the issue on my account, but I tried the code from before my changes and the issue is still present. Interestingly the issue is not present on my other account User:Jdlrobson. I think what has happened here is some sort of style change to the editor or another gadget, but they appear to be unrelated to my change. There have always been 2 boxes, but one has always been positioned to give the illusion of one.

Just to confirm this is what I'm seeing:

thumb

If you're seeing something different please do share!

Jon (WMF) (talk) 20:29, 21 September 2020 (UTC)

:I see the same two boxes, but the box where you have typed "asas" is about twice the height on my account, and it is clearly above the box that has the dropdown list, not overlapping it at all. If I stick to using the smaller box that has the dropdown list, I'm not posting any blank edit summaries, at least not that I have noticed. Chris the speller ^yack 16:14, 22 September 2020 (UTC)

thumb

Is this what you're seeing Chris? ~Awilley (talk) 16:35, 22 September 2020 (UTC)

:I'm seeing the same issue, as per Wikipedia:Village_pump_(technical)#Double_edit_summary%3F. Nikkimaria (talk) 16:56, 3 October 2020 (UTC)

For a few months now I've had the same problem in Wikidata and in Wikipedia with the subject line and the summary line. You always have to fill out both lines identically, otherwise you will have big problems publishing posts in forums and editing Wikipedia articles. In addition, the buttons in the German language setting are sometimes displayed in German and sometimes in English (Preview instead of Vorschau anzeigen).

Duplicate subject line.jpg|Duplicate subject line

Duplicate summary line.jpg|Duplicate summary line

• My Browser is Firefox 83.0 (64-Bit).
• I tried it with and without JavaScript enabled.

Please fix the bug. Thx. --HarryNº2 (talk) 03:05, 7 December 2020 (UTC)

:I've noticed this a few times; as there's a discussion here I'll add a brief comment. It seems (or seemed?) to happen to me now and again, but not systematically. I haven't found it to be a big problem. The dual summary boxes haven't appeared recently, with no noteworthy change to my system that I can identify, but I wouldn't be surprised if they reappear. I always use WikEd, but haven't made tests to see whether it happens with the standard editor. I'm always using the latest Firefox version, with a lot of extensions, with up-to-date Win10/64. Best wishes, Pol098 (talk) 19:43, 8 December 2020 (UTC) They did reappear! Pol098 (talk) 18:36, 21 December 2021 (UTC)

• Date: 2020-10-21 22:52:42 UTC
• wikEd version: 0.9.155 (November 5, 2017)
• Browser: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 (Linux x86_64)
• Skin: vector (detected: vector_new)
• MediaWiki: 1.36.0-wmf.13
• Gadgets:
• MediaWiki scripts: RefToolbar.js, RefToolbarMessages-en.js, RefToolbarConfig.js
• Scripts: User:Cacycle/wikEd.js, User:Cacycle/diff.js, User:Cacycle/wikEdDiff.js
• URL: https://en.wikipedia.org/w/index.php?title=Draft:Tacsipacsi/sandbox&action=edit
• User subpages: None, tested as anon
• User/skin.js: None, tested as anon
• User/common.js: None, tested as anon
• Error console: From wikEd code, only XHR requests POSTed to /w/api.php; there are some seemingly unrelated jQuery deprecation warnings and no errors
• Problem description: Fix redirects does nothing
• Steps to reproduce:
• # Open Draft:Tacsipacsi/sandbox for editing. I tried this logged out to make sure no non-default gadgets or other user preferences interfere.
• # Paste main page.
• # Click the Fix redirects icon on the toolbar.
• Expected results:
• # The link is turned into main page.
• Actual results:
• # The text is highlighted, but no change is made.

—Tacsipacsi (talk) 23:06, 21 October 2020 (UTC)

Its been three years and Im just now getting back to the question I brought up here. It seems that the font size of 13px is hard-coded into the WikEd script ... could the developer(s) change this by turning it into a variable so that people will be able to change the size of the font that loads in the edit window?

Thanks,

—Soap— 02:25, 12 January 2021 (UTC)

:I should qualify that .... I seem to have thought three years ago that it inherits the font size from some other source .... even if that is true, can it be made customizable within WikEd? It seems like it should behave the same way any CSS variable does. —Soap— 02:27, 12 January 2021 (UTC)

And I also want to add that the naive solution of adding

.wikEdFrameBodySyntax

{

font-size: 150% !important;

line-height: 150% !important;

}

does not work either. —Soap— 02:42, 12 January 2021 (UTC)

:I don't know if I'm missing something, but I adjust the font size in the edit window by using my browser's zoom function; I use Ctrl-plus and minus; there's also a View>Zoom mouse option. While I always use Firefox, I can't imagine any browser lacking this capability. I've never felt the need to change the default size in the editor itself. HTH, Pol098 (talk) 14:43, 13 January 2021 (UTC)

::Yes I know about that. My eyesight isnt that bad, but the amount of text zoom I'd want would make editing inconvenient since browser zoom applies to the entire page and not just one textarea within it. I've done it a few times for large edits, but zooming in to edit and then zooming back out to read gets annoying too. WikEd has its own built-in zoom as well, but it's buggy, and starts out by getting smaller instead of larger .... so the few extra clicks adds up for someone like me who mostly makes small edits. Also I suppose I would get used to it, but it took me quite a long time to find the zoom button even after reading the user manual. —Soap— 17:33, 13 January 2021 (UTC)

Summary: the WikEd Wiki link button removes all simple wikilinks from a selection with several links - I don't know if this is by design, or just fortunate; maybe it's only intended to deal with single links. But if the selection includes piped wikilinks, some unlinked text is deleted, I think from the first link to just before the first piped one; this is either an error, or due to my pushing WikEd beyond its specification. I didn't find information about this in the documentation - I may have missed it.

User agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0 (version is really 84.0.2)

Windows 10/64 Pro, Version 10.0.19042 Build 19042 (i.e., current Feb 21)

Wikipedia skin: Vector (default)

User:Pol098/common.js scripts:

importScript('User:Evad37/duplinks-alt.js'); // User:Evad37/duplinks-alt. Show duplicate links.

importScript('User:Markhurd/hidetopcontrib.js'); //Shows only user contributions which aren't top https://en.wikipedia.org/wiki/User:Markhurd/hidetopcontrib

userHideAllSubsequent=true; //optional for hidetopcontrib. If used, shows only first contribution by other users; otherwise shows all

importScript( 'User:Kaniivel/RefConsolidate_start.js' );

Gadgets:

Focus the cursor in the search bar on loading the Main Page

Navigation popups: article previews and editing functions pop up when hovering over links

Open search results in a new tab or window when holding down the Ctrl key

Suppress display of fundraiser banners

Reference Tooltips: hover over inline citations to see reference
information without moving away from the article text (does not work if "Navigation popups" is enabled above)

FormWizard: a wizard for creating and expanding project pages

Display watchlist notices

(This loads the base style for the watchlist. Please do not disable this option.)

Display green collapsible arrows and green bullets for changed pages in your watchlist, page history and recent changes (unavailable with the improved Watchlist user interface)

Display pages on your watchlist that have changed since your last visit in bold (see customizing watchlists for more options)

Subtle update marker: Tone down the "Changed since last visit" indicator on history pages. (By default it renders as a green-filled bar, enabling this gadget changes it to green text.)

Editing:

Citation expander: automatically expand and format citations using Citation bot

Syntax highlighter: Alternative to the default coloring of wiki syntax in the edit box (works best in Firefox and works almost all of the time in Chrome and Opera)

wikEd: alternative full-featured integrated text editor for Firefox, Safari, and Google Chrome (documentation) (of course)

CharInsert: add a toolbar under the edit window for quickly inserting wiki markup and special characters (troubles?)

Add extra buttons to the legacy (2006) editing toolbar

refToolbar: add a "cite" button to the editing toolbar for quick addition of commonly used citation templates

Appearance:

Add an [edit] link for the lead section of a page

Replace the "new section" tab text with "+"

Show radio buttons to switch between views of certain content, such as some maps

Web address (URL) of the page or wiki installation where you experience your problems: all pages. If I copy the sample text I use to illustrate the problem (below) to any page, the problem manifests.

Firefox browser console, after clicking the "Wiki links" button with text selected to cause the problem:

e is undefined h0-main.js:1

Unchecked lastError value: Error: Invalid window ID: 13405 h0-main.js:1

Unchecked lastError value: Error: Invalid window ID: 13405 background.js:47

Problem description: I'm not sure if this is a problem, or if I am trying to do more than WikEd is supposed to. I often use the "Wiki link" button to remove wikilinks from selected text. I have found that I can usually select a section of text with several wikilinks, and the button will remove all the links in the selected text. I think this always works, reliably, if there are no piped links, but if the selection includes non-piped links and a piped link, non-linked text is deleted, I think from the first link until the first piped link. I have tested this with sentences from the following gibberish:

[Text that gets corrupted by the WikEd Wiki link button if a piped link is included in the selection, but not if a pipeless selection is made (some, but not all, links are piped)):

Nowiki'd source text: The variant has become dominant in the United Kingdom and Ireland. If I highlight part of the previous sentence and click "Wiki link", the result is corrupted: "dominant in the Ireland". This is another example with several wikilinks but no pipes that will all be removed without corruption. This is another example with several wikilinks with piped links that will display corruption. (becomes "This is another piped links that will display corruption.") If there are several piped links as in this case the outcome is like this. ("If there piped links as in this case the outcome is like this.")]

Rendered text: The variant has become dominant in the United Kingdom and Ireland. If I highlight part of the previous sentence and click "Wiki link", the result is corrupted: "dominant in the Ireland". This is another example with several wikilinks but no pipes that will all be removed without corruption. This is another example with several wikilinks with piped links that will display corruption. (becomes "This is another piped links that will display corruption.") If there are several piped links as in this case the outcome is like this. ("If there piped links as in this case the outcome is like this.")]

Best wishes, Pol098 (talk) 18:09, 2 February 2021 (UTC)

:Maybe this got missed because of the large amount of extra information required; the problem remains, I summarise: when removing several wikilinks with the WikiEd link button, if some of the links are piped some linked text is simply deleted, corrupting the article if not noticed. Details in the Problem description above. Best wishes, Pol098 (talk) 14:32, 16 March 2021 (UTC)

Steps to Reproduce:

• Edit the section https://en.wikipedia.org/wiki/DDR5_SDRAM#DIMMs_versus_memory_chips (now fixed, so see video...)
• Insert 2 newlines between paragraphs
• Click "Publish changes" or "Changes"
• Note that 1 newline is missing

Video of bug: http://thuejk.dk/missing_newline.mkv

Turning off wikEd fixed the problem. Thue (talk) 11:20, 25 March 2021 (UTC)

:Firefox presumably? Search for "SOLVED" in section wikEd bug report: blank lines deleted. HTH, Pol098 (talk) 11:46, 25 March 2021 (UTC)

::Yes, probably the same issue. I don't really see how it is "solved" if the problem still occurs in the production version editors meet, but I turned wikEd off now, so I don't really care too much :P. Thue (talk) 18:46, 25 March 2021 (UTC)

:::Solved by a small change in Firefox configuration, in the section I referenced: "This issue relates to the Firefox config editor.use_div_for_default_newlines which defaults to true. Changing it to false [in about:config]... takes the problem away for me. Nthep (talk) 15:35, 24 May 2019 (UTC)" I don't remember the details, but the problem was caused by a change Firefox made to the way it handles some HTML markup, it's not really a WikEd issue. If you want to know more (though there's no reason to), read through several previous reports of this issue and links from there. Pol098 (talk) 19:21, 25 March 2021 (UTC)

::::Well, this is not how most things normally work. It is not normally the responsibility of the user of the software to find obscure fixes in obscure webpages to get basic bug-free operation. Thue (talk) 18:32, 26 March 2021 (UTC)

{{Quotebox|text=For the benefit of anyone who comes here after a problem with loss of line breaks when editing Wikipedia with WikEd using the Firefox browser: this is a known issue, an incompatibility rather than an error, and is probably not going to be changed. It happened with a change to Firefox's handling of line breaks, which doesn't affect most non-Wikipedia Web pages, over a year ago. The details are in earlier sections of this page. The fix (which has worked for me with no problems since, without affecting Firefox's operation): Change the value of parameter editor.use_div_for_default_newlines to false in Firefox's about:config. HTH, Pol098 20:45 UTC, 27 March 2021}}

{{Color|red|Sensational return of line-swallower in April 2023!!!}}

{{u|Pol098}} and {{u|Thue}} (and {{u|Cacycle}}), I changed this years ago when I had the problem and found the work-around here, but noticed it had started again recently (possibly with a recent Firefox update?). I have checked my editor.use_div_for_default_newlines and it is still set to false, but WikEd still keeps losing lines and sometimes randomly inserting between bullet points. Any ideas for what to try next? Also, could this be added to the "Known general issues" section on your user page, please, Cacyle, so it is easier to find? Laterthanyouthink (talk) 02:13, 5 May 2023 (UTC)

:p.s. And adding how to get to About:config on Firefox might also be helpful in the instructions to correct it if added to known issues. Laterthanyouthink (talk) 02:16, 5 May 2023 (UTC)

::I've noticed the recent change (reversion to losing line breaks) since April 2023. I'm not sure if it's identical to the way it was before, and indeed find that editor.use_div_for_default_newlines, changed to fix the original problem, remains false. I might change it back again to see what happens. I hadn't reported it, after spending a lot of time on it in 2021; other browsers work. To get to aboutLconfig, just type it in the address bar and accept the warning. Best wishes, Pol098 (talk) 12:22, 5 May 2023 (UTC)

:::looking online, it seems to be an issue with FF v112. Nthep (talk) 12:39, 5 May 2023 (UTC)

:::: All versions from FF v112 to (latest) v116.0.3. Pol098 (talk) 16:57, 14 August 2023 (UTC)

:::::Still happening to me, and editor.use_div_for_default_newlines still set to false... Thanks for your work and updates on this, {{u|Pol098}}. I just keep switching between Wiked and the default one afterwards to check the lines. Laterthanyouthink (talk) 08:05, 17 August 2023 (UTC)

::::::An alternative to switching editors is simply to use a different browser for Wikipedia. Best wishes, Pol098 (talk) 14:19, 17 August 2023 (UTC)

{{Clear}}

Running the RegExpTypoFixer adds duplicate endings and $3. (i.e. ruled -> ruleded$3, creator -> creatoror$3, Jennifer -> Jenniferer$3). I think it's happening for all the rules using $3, but I haven't checked carefully. I've also got a similar problem to the one mentioned above, with RegExpTypoFixer eating the last newline if I run it on selected paragraph(s) instead of the whole page.

• Version: 0.9.155
• Browser: Chrome
• OS: Linux
• Skin: Vector
• User:Rusalkii/common.js
• Problem persists across pages but you can see the examples I listed above on List of Angel's Friends characters

Rusalkii (talk) 21:49, 4 April 2021 (UTC)

"Preview page with this template" (template edit) isn't supported - if you change something in code, and you do "Preview page with this template" instead of Preview, the changes will be lost. MarMi wiki (talk) 17:06, 5 April 2021 (UTC)

:I've (blindly) added support for that button [https://pl.wikipedia.org/wiki/Wikipedysta:MarMi_wiki/wikiEd.js here]. It seems to work ok, but since editor #Doesn't work well with Preview when invoked from common.js), I have no way of confirming it (but it behaves exactly like preview). MarMi wiki (talk) 15:54, 7 April 2021 (UTC)

There's something wrong with the translation applying process - I see (in dev console - Network) that the file with my language is loading (wikEd_international_pl.js), but the interface in wikEd remains in English. MarMi wiki (talk) 19:27, 6 April 2021 (UTC)

:More info:

:Automatic language detection doesn't work (as described above).

:Setting languageDefault in user common.js doesn't do anything.

:Forced load of translation by mw.loader.load (in user common.js) works. MarMi wiki (talk) 19:52, 6 April 2021 (UTC)

• Date: 2021-04-06 19:56:16 UTC
• wikEd version: 0.9.155 (November 5, 2017)
• Browser: Mozilla/5.0 (Windows NT 6.1; rv:87.0) Gecko/20100101 Firefox/87.0 (Win32)
• Skin: vector (detected: vector_new)
• MediaWiki: 1.36.0-wmf.37
• Gadgets:
• MediaWiki scripts:
• Scripts: User:Cacycle/wikEd.js, User:Cacycle/diff.js, User:Cacycle/wikEdDiff.js
• URL: Any
• User subpages: https://en.wikipedia.org/wiki/Special:PrefixIndex/User:MarMi_wiki/
• User/skin.js: https://en.wikipedia.org/wiki/User:MarMi_wiki/vector.js
• User/common.js: https://en.wikipedia.org/wiki/User:MarMi_wiki/common.js
• Error console: -
• Problem description: See above.
• Steps to reproduce: Change language in preferences to other than English (I use global language setting), follow the steps in User:Cacycle/wikEd_international#Installation

When invoked from common.js, Preview resets any changes you enter (as a gadget it works ok). MarMi wiki (talk) 15:48, 7 April 2021 (UTC)

: I have the same issue on ArchWiki, and there is no "Gadgets" tab available in Preferences. I see the following (only with wikEd enabled) in the Console of the Firefox's Development tools:

: Uncaught Error: Another textSelection API was already registered, on load.php:744:928

jQuery 6
enqueue https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:11
jQuery 10
build https://wiki.archlinux.org/load.php?lang=pt-br&modules=ext.wikiEditor&skin=vector&version=18yyc:29
(asynchronous: setTimeout handler)
build https://wiki.archlinux.org/load.php?lang=pt-br&modules=ext.wikiEditor&skin=vector&version=18yyc:29
create https://wiki.archlinux.org/load.php?lang=pt-br&modules=ext.wikiEditor&skin=vector&version=18yyc:17
addModule https://wiki.archlinux.org/load.php?lang=pt-br&modules=ext.wikiEditor&skin=vector&version=18yyc:8
wikiEditor https://wiki.archlinux.org/load.php?lang=pt-br&modules=ext.wikiEditor&skin=vector&version=18yyc:13
js https://wiki.archlinux.org/load.php?lang=pt-br&modules=ext.wikiEditor&skin=vector&version=18yyc:5
jQuery 12
js https://wiki.archlinux.org/load.php?lang=pt-br&modules=ext.wikiEditor&skin=vector&version=18yyc:3
js https://wiki.archlinux.org/load.php?lang=pt-br&modules=ext.wikiEditor&skin=vector&version=18yyc:5
runScript https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:13
cssHandle https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:14
flushCssBuffer https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:5
flushCssBuffer self-hosted:1225
(asynchronous: FrameRequestCallback)
addEmbeddedCSS https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:6
execute https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:14
doPropagation https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:7
(asynchronous: requestIdleCallback handler)
requestIdleCallback self-hosted:1178
requestPropagation https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:7
setAndPropagate https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:8
markModuleReady https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:12
runScript https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:13
cssHandle https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:14
flushCssBuffer https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:5
flushCssBuffer self-hosted:1225
(asynchronous: FrameRequestCallback)
addEmbeddedCSS https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:6
execute https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:14
doPropagation https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:7
(asynchronous: requestIdleCallback handler)
requestIdleCallback self-hosted:1178
requestPropagation https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:7
setAndPropagate https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:8
markModuleReady https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:12
runScript https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:13
cssHandle https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:14
flushCssBuffer https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:5
flushCssBuffer self-hosted:1225
(asynchronous: FrameRequestCallback)
addEmbeddedCSS https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:6
execute https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:14
doPropagation https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:7
(asynchronous: requestIdleCallback handler)
requestIdleCallback self-hosted:1178
requestPropagation https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:7
setAndPropagate https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:8
implement https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:20
 jQuery

:followed by:

:Uncaught TypeError: element is undefined, on load.php:1126:765

jQuery 22
runScript https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:13
execute https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:14
doPropagation https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:7
(asynchronous: requestIdleCallback handler)
requestIdleCallback self-hosted:1178
requestPropagation https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:7
setAndPropagate https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:8
implement https://wiki.archlinux.org/load.php?lang=pt-br&modules=startup&only=scripts&raw=1&skin=vector:20
 jQuery

: Rafaelff (talk) 14:24, 26 June 2021 (UTC)

I have WikEd enabled, but all I can do is turn it on or off. This is probably due to me being on mobile. ― Qwerfjkl|✉   22:46, 8 May 2021 (UTC)

Just a note that that bug (reported above at #Unicode fixing bug) is still active ... and FWIW, I haven't selected any options that mention "unicode" in any of the preference pages, that I can see. I use Firefox, and any time I try to sort any of my tables or lists of plants using wikEd, it replaces any occurrence of the string "uad" with "­ ;" (without the space). FWIW. - Dank (push to talk) 19:12, 21 May 2021 (UTC)

As title, I've tested whether wikEd is usable when using these two skins, discovering that it does not work when using any of them (OS:Windows 10 Home 21H1 Browser:Mozilla Firefox for Acer 94.0.1 (64-bit) and Microsoft Edge 95.0.1020.44 (64-bit)). Yet it is usable when using Vector (both browsers work). What is the reason of this? I'm very curious.--RekishiEJ (talk) 17:53, 9 November 2021 (UTC)

After toggle uppercase first → uppercase, I usually want to toggle again to lower case, but recently wikEd loses the highlighting, so now I have to select and highlight the text again. This is time-consuming and makes me more likely to highlight something other than the exact text I had highlighted for the first toggle. Chris the speller ^yack 05:14, 11 November 2021 (UTC)

:Hi - I too have noticed this, in addition to an even worse problem, and was wondering if you had changed anything recently? Every time I cut and paste, the cursor shoots back to the top of section, which as you can imagine is very time-wasting and frustrating. (On Firefox.) I did try doing a clean and restarting my computer, but that didn't fix it. Laterthanyouthink (talk) 05:53, 17 November 2021 (UTC)

::I've been seeing that too, only in Firefox 94 on Windows. No problem in Firefox for Android or any other browser on Windows. Nthep (talk) 09:18, 17 November 2021 (UTC)

:::Ah, yes, good catch, {{u|Nthep}}. It works fine in Edge on Windows, so I'll temporarily edit there. Laterthanyouthink (talk) 10:18, 17 November 2021 (UTC)

::::It is also happening in Firefox on macOS. Sammi Brie (she/her • t • c) 05:35, 19 November 2021 (UTC)

:::::I don't think I changed anything when the problem started, and now (within the last week) it seems to be fixed, though again I changed nothing. I'm very happy. Maybe a Firefox update broke it and then another update fixed it. It's now Firefox 97.0 Chris the speller ^yack 05:12, 16 February 2022 (UTC)

::::::This looks very much like the problem described in the next section ("Cursor jumps to top of edit box"). I believe Firefox 97 is the answer. Chris the speller ^yack 05:17, 16 February 2022 (UTC)

(Inserted at top of section, 20 January 2022)

I have been alerted by email saying "this has been fixed in Firefox Nightly 98.0a1 (2022-01-19) and Firefox release will get this fix once it reaches 98". Thanks to {{user|Pol098}} for keeping us informed and following through. Laterthanyouthink (talk) 06:28, 20 January 2022 (UTC)

Glad I was able to help. FF98 is in nightly, beta due 8 Feb, release 8 March. It's been a long time... Best wishes, Pol098 (talk) 12:09, 20 January 2022 (UTC)

(Inserted at top, 7 Jan 22)

{{Color|red|This is reported fixed in Firefox, to be implemented from Firefox 97 (8 February 2022)}}. It seems to be working in released 97, no need to wait for 98. (10 Feb 22).
Links further down, for 7 Jan 22

::Hallelujah! Working for me today too. Laterthanyouthink (talk) 09:19, 12 February 2022 (UTC)

{{Quote box|title=Copied from previous section|text=Every time I cut and paste, the cursor shoots back to the top of section, which as you can imagine is very time-wasting and frustrating. (On Firefox.) I did try doing a clean and restarting my computer, but that didn't fix it. Laterthanyouthink (talk) 05:53, 17 November 2021 (UTC)}}

I have this problem; I have added this separate section and heading to make it easier to find for others with the same issue. I had seen the header Loses text highlighting after toggle uppercase first → uppercase, but ignored it for days as the text highlighting issue isn't something I'd noticed. Glad to hear it's specific to one Firefox version, which means it's likely to be fixed. I work around it by editing with a different browser. Best wishes, Pol098 (talk) 13:55, 19 November 2021 (UTC)

The jump to the top issue also happens in Troubleshooting/Safe Mode. Pol098 (talk) 15:06, 20 November 2021 (UTC)

I have reported this to Firefox support at https://webcompat.com/issues/94036 [21Dec21: this GitHub discussion has now been closed (but can still be read there) and Bug 1747008 has been opened on Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1747008 ]

What I posted (with a couple of typos fixed):

{{Quotebox|text=There is an issue with Firefox 94 & 95 when editing Wikipedia with the WikEd editor enabled. I have searched but not seen it reported.

It has been reported on the WikEd Talk page by several people, with no resolution reported: https://en.wikipedia.org/wiki/User_talk:Cacycle/wikEd#Loses_text_highlighting_after_toggle_uppercase_first_%E2%86%92_uppercase and the next section, "Cursor jumps to top of edit box, WikEd with Firefox 94"

Specifically, when editing any Wikipedia page or section with the WikEd editor enabled instead of the standard Wikipedia editor, if text is pasted into the page, the cursor jumps to the top of the page, and the page scrolls up if there is more text than fits the screen. Normal behaviour is that the cursor stays at the end of the inserted text.

Other uses report that this happens with Firefox 94-95, in normal and Troubleshooting (to disable extensions) modes, under Windows and macOS, and does not happen with other browsers, older Firefoxes, or Firefox for Android. Link to discussion is above.

To replicate: open a Wikipedia page that is not too short (to show scrolling), click "Edit Source", enable the WikEd editor by clicking a "pencil and paper" icon at bottom left of a cluster of icons above the edit window at the top right, scroll down so that the top of the text is not displayed, and paste some text anywhere. The text will be inserted, but the box will scroll to the top, and the cursor will be at the beginning of text. Normally the cursor would be positioned at the end of the new insertion. This may be an issue with WikEd or with Firefox 94-95.}} Pol098 (talk) 15:40, 20 November 2021 (UTC)

:You forgot to tell them what wikEd is and how to enable it. —TheDJ (talk • contribs) 09:18, 24 November 2021 (UTC)

::Yes, I realised that very quickly, but I can't log in to GitHub to say so [later: I can now log in, and have posted update] (a changed email address and a password deemed "weak" - when I try to login I get a password reset sent to a non-existent email address). I wrote a followup which I can't post there; I'll put it here in the hope it'll be seen by the Firefox maintainers (I haven't revised and checked it thoroughly, ready for GitHub).

{{Quotebox|text=Thanks for response [Firefox maintainers].

I omitted important information to replicate the issue (sorry):

- As I said, this only manifests with the optional WikEd editor, not the standard editor

- you have to be logged in to Wikipedia

- You have to tick Preferences > Gadgets > Editing section > "wikEd: alternative full-featured integrated text editor for Firefox, Safari, and Google Chrome."

- when editing a page, the icon to switch to the WikEd editor instead of the standard editor must be clicked.

I attach a screen dump of the edit screen with WikEd enabled. To switch to the WikEd editor instead of the standard Wikipedia one after selecting it in Preferences, click the button circled in red, at the top right of the edit area, (not left as I had said); a large array of icons should appear.

The issue manifests in Troubleshooting mode; I have clean-installed Firefox in a Win7/32 virtual machine and the issue also manifests.}}

::Best wishes, Pol098 (talk) 11:27, 24 November 2021 (UTC)

:::Update: bug persists in Firefox 95.0, 95.0.1, 95.0.2, 96.x Pol098 (talk) Various dates in November–December 2021

::::[https://github.com/webcompat/web-bugs/issues/94036 A possible cause (in Firefox) has been found and is being looked into.] [21Dec21: this GitHub discussion has now been closed (but can still be read there) and Bug 1747008 has been opened on Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1747008 ] Pol098 (talk) 13:33, 20 December 2021 (UTC)

{{Outdent|::::}}{{Color|red|This is reported fixed in Firefox, to be implemented from Firefox 97}}

See https://bugzilla.mozilla.org/show_bug.cgi?id=1747008

[https://wiki.mozilla.org/Release_Management/Calendar Firefox 97 is already in nightly release, due for beta release on 10 January 2022, final release on 8 February 2022]
Pol098 (talk) 14:17, 7 January 2022 (UTC)

=== wikEd bug report: Cursor springs to the top of the edit field ===

{{Color|red|Fixed—see above}}

• Date: 2021-11-22 22:35:51 UTC
• wikEd version: 0.9.155 (November 5, 2017)
• Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0 (Win32)
• Skin: vector (detected: vector_new)
• MediaWiki: 1.38.0-wmf.9
• Gadgets:
• MediaWiki scripts:
• Scripts: User:PerfektesChaos/wikEd_international_de.js, User:Cacycle/diff.js, User:Cacycle/wikEdDiff.js
• URL: e.g. https://de.wikipedia.org/w/index.php?title=Herbert_Obenaus&action=edit or any other = all
• User subpages: https://de.wikipedia.org/wiki/Special:PrefixIndex/Benutzer:Wi-luc-ky/
• User/skin.js: https://de.wikipedia.org/wiki/Benutzer:Wi-luc-ky/vector.js
• User/common.js: https://de.wikipedia.org/wiki/Benutzer:Wi-luc-ky/common.js
• Error console: no error messages related to wikEd.js
• Problem description: Hallo, in de:WP a bug with the cursor-function since 11/3 are discussed by several users (see first, then, recently): After every C&P in the edit field, the cursor springs to the very beginning of the edit field.
  To find the last cursor point in a long article – clicking the reverse button the cursor springs back to the previously changed word(s), which occurs in blue. I. e., the last change is only marked but preserved.
  If WikEd is deactivated the editing field works properly.
• Steps to reproduce: It happens in all articles by changing.

Thanks for debugging, --Wi-luc-ky (talk) (German Wikipedia user) 23:52, 22 November 2021 (UTC)

:You might not have seen the previous two sections. This has been reported to the Firefox people (link in previous section). Best wishes, Pol098 (talk) 21:02, 23 November 2021 (UTC)

::Yes, Firefox 97 seems to have fixed this problem. Many thanks to them and especially to the folks here who dug into the problem and reported it. Chris the speller ^yack 05:21, 16 February 2022 (UTC)

I think that this might be the same as #wikiEd running paragraphs together and inserting extraneous newlines above, in Firefox. It seems to be losing paragraph breaks and randomly inserting lines after headers. I noticed this a couple of weeks ago for the first time in a long time. Laterthanyouthink (talk) 10:35, 12 June 2022 (UTC)

:Oh, I have just re-read the solution about Firefox needing the change to editor.use_div_for_default_newlines to false, and worked out how to do it... Hopefully fixed now! Laterthanyouthink (talk) 01:37, 2 September 2022 (UTC)

• Date: 2022-06-23 13:04:41 UTC
• wikEd version: 0.9.155 (November 5, 2017)
• Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:101.0) Gecko/20100101 Firefox/101.0 (Win32)
• Skin: vector (detected: vector_new)
• MediaWiki: 1.39.0-wmf.17
• Gadgets:
• MediaWiki scripts:
• Scripts: User:Cacycle/wikEd.js, User:Cacycle/diff.js, User:Cacycle/wikEdDiff.js
• URL: https://en.wikisource.org/w/index.php?title=Translation:Shulchan_Aruch/Orach_Chaim/154&action=edit
• User subpages: https://en.wikisource.org/wiki/Special:PrefixIndex/User:Nissimnanach/
• User/skin.js: https://en.wikisource.org/wiki/User:Nissimnanach/vector.js
• User/common.js: https://en.wikisource.org/wiki/User:Nissimnanach/common.js
• Error console: ____ (Firefox: Tools → Web Developer → Browser console; push clear and reload the page. Chrome: Control button → Tools → JavaScript console. Copy and paste error messages related to wikEd.js)

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://meta.wikimedia.org/w/load.php?lang=en&modules=ext.globalCssJs.user&skin=vector&user=Nissimnanach&version=hmu01 load.php:9:800

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://www.mediawiki.org/w/index.php?title=MediaWiki:Gadget-edittop.js&action=raw&ctype=text/javascript load.php:9:800

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://commons.wikimedia.org/w/index.php?title=MediaWiki:Gadget-HotCat.js&action=raw&ctype=text/javascript load.php:9:800

This page is using the deprecated ResourceLoader module "jquery.ui". Please use OOUI instead. load.php:402:254

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-popups.js&action=raw&ctype=text/javascript load.php:9:800

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript load.php:1:303

Some cookies are misusing the recommended “SameSite“ attribute 4

Cookie “wikiEditor-0-toolbar-section” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite injectedScript" draggable="false">index.php:243:111

Cookie “wikiEditor-0-toolbar-section” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 injectedScript" draggable="false">index.php:243:111

Cookie “enwikisourcewmE-sessionTickLastTickTime” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite injectedScript" draggable="false">index.php:243:111

Cookie “enwikisourcewmE-sessionTickTickCount” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite injectedScript" draggable="false">index.php:243:111

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://en.wikipedia.org/w/index.php?title=User:Cacycle/diff.js&action=raw&ctype=text/javascript&0.9.155 index.php:17743:12

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEdDiff.js&action=raw&ctype=text/javascript&0.9.155 index.php:17743:12

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://upload.wikimedia.org/wikipedia/commons/3/3e/WikEd_error.png

[Before clearing the console, I also had this error:]

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://upload.wikimedia.org/wikipedia/commons/3/3e/WikEd_error.png index.php:6061:1

Uncaught TypeError: rect is undefined

PastePoll https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:5244

index.php:5244:7

Learn more: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/Unexpected_type

PastePoll https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript:5244

• Problem description: Paste wiki text from other wiki page, sometimes "Convert pasted text to Wiki code" dialog pops up, other times it doesn't and also the [W] button and alt-shift-b also don't work
• Steps to reproduce: Paste text from https://he.wikisource.org/wiki/%D7%A9%D7%95%D7%9C%D7%97%D7%9F_%D7%A2%D7%A8%D7%95%D7%9A_%D7%90%D7%95%D7%A8%D7%97_%D7%97%D7%99%D7%99%D7%9D_%D7%A7%D7%A0%D7%92 onto edit page at https://en.wikisource.org/w/index.php?title=Translation:Shulchan_Aruch/Orach_Chaim/154&action=edit

Sometimes if I paste just a couple lines or paste twice I get the [w] popup. Other times I get no [w] popup. Seems to happen more often when pasting longer text.

Thank you

Nissimnanach (talk) 13:17, 23 June 2022 (UTC)Nissimnanach

Please see subject line. I am trying out the Vector 2022 skin (which I mostly like). I am using Edge browser under Win 10 Pro, both up to date. —Finell 02:17, 16 September 2022 (UTC)

:Hi {{ping|Cacycle}} about Vector 2022, perhaps you might be interested in reading this FAQ of the Desktop Improvements project.--Patafisik (WMF) (talk) 10:33, 27 January 2023 (UTC)

:@Finell I had this problem. Try clicking on the drop down menu in the header toolbar and see if you can scroll down the menu. I found the wiked button there (i.e. hidden from sight at first) and I just needed to reactivate the app. Nthep (talk) 14:44, 27 January 2023 (UTC)

::Which drop down? I need that solution cuz normally this new default Vector 2022 skin doesn't work with wikEd —Loginnigol 16:43, 3 December 2023 (UTC)

:::There's only one - the one at the right hand end. But note, this doesn't fix the problem described below at #WikEd interface disappeared — Any conflicts? Nthep (talk) 16:59, 3 December 2023 (UTC)

{{Edit fully-protected|User:Cacycle/wikEd.js|answered=yes}}

Internet Explorer doesn't support unsetting styles using null ([https://github.com/mdn/browser-compat-data/issues/16828 reference]).

Therefore, I would like to replace this code:

// delete measuring styles

select.style.margin = null;

input.style.fontFamily = null;

select.style.fontFamily = null;

with:

// delete measuring styles

// (IE requires assigning an empty string, it doesn't work with null)

select.style.margin = '';

input.style.fontFamily = '';

select.style.fontFamily = '';

I'm not sure wikEd can run on IE anyway, but it's more about promoting more compatible code. We'll have to live with IE 11 for some time yet, at least on Wikipedia.

(ah, and the complete removal of IE from MDN is really annoying…)

Od1n (talk) 04:05, 20 December 2022 (UTC)

:{{not done}} (as to the immediate edit request), User:Cacycle is active and may of course update their own personal script here if they would like to. — xaosflux ^Talk 11:54, 20 December 2022 (UTC)

::User:Cacycle isn't very active currently (very few edits on 2021, extremely few edits on 2022), and although wikEd is in the User: namespace, this script is imported by a lot of wikis. However, I guess we'll just let IE 11 die, as in the near future it should become completely unsupported everywhere. Od1n (talk) 09:30, 28 December 2022 (UTC)

Is there a way to have this tool, but only with the ''reference, template, and code folding

' feature? I don't really want all the other things. Is there another gadget or script that does that too?' BhamBoi (talk) 21:28, 18 January 2023 (UTC)

Original message from frwiki, copied here by Patafisik (WMF) (talk) 10:11, 27 January 2023 (UTC)

Bonjour,

Anomalie : En synthèse lorsque je travaille avec l'éditeur Wikied comme en mode classique il y a d'emblée un problème d'affichage : deux fenêtres d'édition s'ouvrent l'une sous l'autre et en mode classique les boutons se superposent avec la fenêtre du dessous et ne sont pas actifs. Je peux éditer le texte et le sauvegarder la première fois que j'utilise l'éditeur depuis la mise en marche de l'ordinateur. Mais lors des modifications suivantes, le texte modifié n'est pas repris lorsque je le prévisualise et n'est pas conservé lorsque je sauvegarde ma modification. Je finis généralement par sauvegarder ma modification en effectuant de multiples tentatives ... mais je n'ai jamais pu déterminer une procédure précise permettant de contourner ce bug.

Configuration : Windows 11, Firefox version 109.0 et Chrome Version 109.0.5414.76 (même problème avec les deux navigateurs).

Contexte :

• Je ne suis pas un perdreau de l'année ...
• Je ne touche jamais au paramétrage de l'éditeur mais quelques jours avant le déploiement de la dernière version de Vector sur la version anglophone de Wiki (pure coincidence, je n'étais pas au courant), j'ai voulu testé les dernières fonctionnalités de l'éditeur et ai activé toutes les fonctions beta ainsi que la version la plus récente de l'éditeur. Ayant eu des problèmes en éditant les articles (pb sans rapport avec ceux que je signale ici, j'arrivais à faire des sauvegardes), j'ai choisi l'ancienne version de Vector et ai désactivé toutes les fonctions beta le jour même ou Vector était déployé. Et c'est là que tous mes ennuis ont commencé.
• Par ailleurs mon ordinateur fonctionne normalement (Photoshop, Word, Excel, navigateur internet, messagerie Thunderbird) et a priori je n'ai pas de virus. Pline (discuter) 27 janvier 2023 à 09:37 (CET)

::Hello, my text editor (wikied, classic wiki) still works badly: display problems, loss of text entered. Would my profile be...broken? I use the old version of Vector (2010) and all the beta functions are off. --Pline (talk) 12:44, 8 February 2023 (UTC)

:::{{Reply-to|Patafisik (WMF)}} My French is not that great, but is this the long-standing #wikEd bug report: two boxes for edit summary? Best wishes, Pol098 (talk) 17:08, 14 August 2023 (UTC)

::::CC {{ping|Pline}}--Patafisik (WMF) (talk) 07:26, 17 August 2023 (UTC)

Hi, User:Cacycle/wikEdDiff.js can trigger TypeError: Cannot read properties of undefined (reading 'innerHTML') in line 652 which has the content var versionMatchOld = tdOld.innerHTML.match( /\bhref="([^#"<>]+?(&(amp;)?|\?)oldid=\d+[^#"<>]*?)"/ );. Reporting it here as this shows up in some server-side logs per phab:T326833 (though it is not very common). Could that code please be improved? Thanks a lot! :) -- AKlapper (WMF) (talk) 00:03, 7 February 2023 (UTC)

:I think line 567 should be changed to compare against undefined instead of null, i.e. if ( tdOld === undefined || tdNew === undefined ) { – these variables are never null, but they may be undefined if the appropriate table cells are not found. —Tacsipacsi (talk) 23:46, 8 February 2023 (UTC)

::For the record, it is a regression from [{{fullurl:User:Cacycle/wikEdDiff.js|diff=prev&oldid=623742061}} 623742061] (line 506/519). Od1n (talk) 16:21, 20 April 2023 (UTC)

This 2021 bug, possibly now different, has reappeared. Rather than start a new section, others, and I, have been appending to the section #Bug report: editing with wikEd and Firefox deletes newlines, probably better than having lots of sections to check. Best wishes, Pol098 (talk) 12:26, 5 May 2023 (UTC)

Unchanged 6 months later, for all intermediate Firefox versions up to the current 119.0.1. Pol098 (talk) 17:34, 9 November 2023 (UTC)

{{edit interface-protected|User:Cacycle/wikEd.js|answered=yes}}

Do we know of anything that's incompatible with wikEd? I tried enabling the gadget in Preferences and nothing seemed to happen: editing a page looked just like normal and there was no wikEd button on the page, even after a hard refresh. I also tried downloading the Tampermonkey script (after disabling the gadget). It claimed to run, but again with no visible effect. As wikEd works for everyone else, it's obviously a problem with my setup rather than a bug. Are there any known conflicts? I'm using Vector 2010, Firefox and Ubuntu. Thanks, Certes (talk) 21:35, 5 November 2023 (UTC)

:There are a lot of things that are incompatible with wikEd, but as far as I know, it’s way more common that wikEd breaks other things than the other way round. JavaScript error messages may be of help. —Tacsipacsi (talk) 22:38, 5 November 2023 (UTC)

:I don't know if this is related, but a few days ago I noticed that I didn't see wikEd anymore. I haven't been actively editing lately, so I don't know when it stopped working. I was using Vector 2022, and I did all sorts of settings changes to try to find the cause, cleared my CSS and JS pages etc. Long story short, I finally got it to appear, I don't even know how, but only in Vector 2010. I have a test account logged in on another browser and I reset all the settings on that account but it's the same thing: wikEd works on Vector 2010 but not on 2022. kyykaarme (talk) 16:47, 8 November 2023 (UTC)

::@Kyykaarme Same problem here. Suddenly vanished. I use Vector 2022, works on Vector 2010. Doug Weller talk 14:53, 9 November 2023 (UTC)

:::@Kyykaarme taking this to the VP technical Doug Weller talk 14:26, 10 November 2023 (UTC)

::::Same thing to me — WikEd has VANISHED from my Source edit interface without any trace. No explanation has been provided. The timeline clearly indicates this thing started early in November.— and still ongoing —Loginnigol 20:56, 18 November 2023 (UTC)

::Is it working for you now? —Loginnigol 21:01, 18 November 2023 (UTC)

:You too? Has this problem been solved or what? It has been weeks now. —Loginnigol 21:01, 18 November 2023 (UTC)

:Still not solved. WikED has failed to work in the default Wikipedia skin (Vector 2022) for all of November and into December now. —Loginnigol 17:20, 3 December 2023 (UTC)

It seems to have been broken by phab:T347907. I think the following simple change should fix it:

@@ -1453,7 +1453,7 @@

// vector (see https://bugzilla.wikimedia.org/show_bug.cgi?id=19527)

vector_old: [ 'personal', true, true, ['content', 'bodyContent', 'contentSub', 'left-navigation', 'namespaces'] ],

- vector_new: [ 'p-personal', true, true, ['content', 'bodyContent', 'contentSub', 'left-navigation', 'p-namespaces', 'p-cactions'] ],

+ vector_new: [ 'p-personal', true, true, ['content', 'bodyContent', 'contentSub', 'left-navigation', 'p-associated-pages', 'p-cactions'] ],

// citizendium.org

pinkwich5: [ 'p-personal', true, true, ['column-content', 'content', 'bodycontent', 'sitesub', 'contentSub', 'column-one', 'p-cactions'] ],

—Tacsipacsi (talk) 09:05, 4 December 2023 (UTC)

: My WikEd is also no longer functioning in the English and French Wikipedia since beginning of November 2023 !

: Do we have to paste these code lines into our User:YourUsername/common.js page ? (Local Wikipedia language or wiki only), or,

: in our meta:User:YourUsername/global.js page (Every Wikipedia language and MediaWiki installation) ?

: Do we need to also include the first line: @@ -1453,7 +1453,7 @@ ?

: In advance, thank you very much for your answer. Shinkolobwe (talk) 21:36, 5 December 2023 (UTC)

:"the following simple change" means? Change what where? Not everybody here is an insider techie so please articulate in plain English. Some of us use wikEd via gadget checkmark in settings only (no longer manually put scripts on any "js" page). —Loginnigol 00:28, 6 December 2023 (UTC)

::The change needs to be done in the wikEd script, not in your common.js or global.js. This means on the one hand that you shouldn’t and can’t do anything, and on the other hand that the people who can do something hopefully recognize and know how to read a unidiff. —Tacsipacsi (talk) 01:39, 6 December 2023 (UTC)

:{{done}} Izno (talk) 04:29, 6 December 2023 (UTC)

::It's back!!! Well done! Hawkeye7 (discuss) 09:59, 6 December 2023 (UTC)

:::Yes! It works now. Thanks specifically to Tacsipacsi since you cared enough to provide the solution and restoring something that last time it was functional was back in October.—Loginnigol 11:18, 6 December 2023 (UTC)

:I'm still using the old version Vector (not use to the new version), and my wikied doesn't work in the English/Chinese Wikipedia now. Maybe because of this update? Can any experts fix this? Thank you so much! M1koto 00:21, 7 December 2023 (UTC)

::Same for me on enwiki and frwiki; wiked returns if I select Vector 2022... Mwarf (talk) 10:33, 7 December 2023 (UTC)

::So it looks like the vector_new (Vector 2022) rule matched Vector 2010 before the above edit request and matches Vector 2022 since then, while the vector_old (Vector 2010) rule matches neither Vector versions… The solution should be copying the previous version of the vector_new rule to vector_old:

@@ -1453,7 +1453,7 @@

// vector (see https://bugzilla.wikimedia.org/show_bug.cgi?id=19527)

- vector_old: [ 'personal', true, true, ['content', 'bodyContent', 'contentSub', 'left-navigation', 'namespaces'] ],

+ vector_old: [ 'p-personal', true, true, ['content', 'bodyContent', 'contentSub', 'left-navigation', 'p-namespaces', 'p-cactions'] ],

vector_new: [ 'p-personal', true, true, ['content', 'bodyContent', 'contentSub', 'left-navigation', 'p-associated-pages', 'p-cactions'] ],

// citizendium.org

pinkwich5: [ 'p-personal', true, true, ['column-content', 'content', 'bodycontent', 'sitesub', 'contentSub', 'column-one', 'p-cactions'] ],

—Tacsipacsi (talk) 14:49, 8 December 2023 (UTC)

:{{done}} Izno (talk) 18:28, 8 December 2023 (UTC)

::Solved the issue for me, thanks! Mwarf (talk) 22:47, 8 December 2023 (UTC)

::{{reply to|Izno}} The first element of the array should also be changed from personal to p-personal. Now the logo is slightly out of place because it’s placed directly in the <body> (fallback mode) instead of the personal menu. The fallback position happens to be near to the intended one, but it isn’t exactly there (and due to the user menu being absolutely positioned, it can cause overlaps). —Tacsipacsi (talk) 18:37, 10 December 2023 (UTC)

File:Symbol watching blue lashes high contrast.svg You are invited to join the discussion at Wikipedia:Village pump (technical) § Neither Vector 22 or Vector 10 are working for me.. –Novem Linguae (talk) 08:09, 24 December 2023 (UTC)

Description:

I am attempting to customize my MediaWiki installation to improve my workflow by adding a custom button to the toolbar. My primary goal is to have a button that allows me to easily insert the "$...$" environment into the editing area.

What I Have Done:

1. Created a "custom.js" file in my user space to define the custom button and its functionality.
2. Included the button image and tooltip text.
3. Wrote JavaScript code to insert the math tags ("$...$") at the cursor position.
4. Added the button to the toolbar using the mw.toolbar.addButton method.

The Issue:

Despite following the instructions and troubleshooting steps, I am facing difficulties in getting the custom button to appear in the toolbar. Instead, I encounter the following issues:

1. Deprecated ResourceLoader modules, such as "jquery.ui.core," "jquery.ui.widget," and others, generate warnings in the developer console. I have attempted to replace these deprecated modules with their recommended counterparts without success.
2. I also receive an error message: "A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received." This error is preventing the custom button from being displayed.

Additional Information:

• I have cleared my browser cache and refreshed the page multiple times.
• My MediaWiki version is

• I have full permissions to edit JavaScript and CSS files in my MediaWiki instance.

Request for Assistance:

I would greatly appreciate your assistance in resolving these issues. If you have any insights or suggestions on how to successfully add a custom button to the MediaWiki toolbar for inserting the "$...$" environment, please let me know.

Thank you for your time and support. MoveSmart (talk) 17:30, 19 January 2024 (UTC)

Issue Description:

Whenever I click on the Fullscreen button in the WikiEd toolbar, I am unable to make any further edits unless I remove WikiEd from my common.js. The problem seems to be that the links and buttons of the MediaWiki interface overlap the WikiEd toolbar in Google Chrome.

Steps to Reproduce:

1. Enable WikiEd by adding it to the "common.js" file.
2. Edit a page on MediaWiki using Google Chrome.
3. Click on the Fullscreen button in the WikiEd toolbar.

Expected Behavior:

Fullscreen mode should be activated, allowing for distraction-free editing, and I should still be able to access and interact with MediaWiki's interface elements.

Actual Behavior:

Upon clicking the Fullscreen button, while in fullscreen mode, the links and buttons of the MediaWiki interface overlap with the WikiEd toolbar. This makes it impossible to interact with WikiEd or edit the page effectively.

Environment:

• MediaWiki Version: 1.34.0
• Browser: Google Chrome
• Operating System: Windows 11 x64

Additional Information:

• The issue occurs specifically when using Google Chrome.
• Removing WikiEd from the "common.js" file allows me to edit the page without problems.
• The problem makes it difficult to use WikiEd's Fullscreen feature effectively in Chrome.

Note: You may want to include any relevant screenshots or additional details that can help the developers better understand the issue. MoveSmart (talk) 17:37, 19 January 2024 (UTC)

var wikEdConfig = {};

This line of code doesn't create the "wikEdConfig" variable, which is needed to configure the s:ru:MediaWiki:Gadget-wikEd.js gadget. [https://ru.wikisource.org/w/index.php?title=MediaWiki:Gadget-wikEd.js&oldid=5130405 Here is the code]. On a page (e.g. s:ru:Ветка роз (Щепкина-Куперник)) in the Chrome console (F12 button), when entering "wikEdConfig", the console responds with "undefined".

I [https://ru.wikisource.org/w/index.php?title=MediaWiki:Gadget-wikEd.js&oldid=5130404 tried to disconnect] the WikEd script, leaving in the gadget only the variable definition, thinking that the script overrides it. But this doesn't work either, the variable is not defined.

However, the variable is defined if I [https://ru.wikisource.org/w/index.php?title=User:Vladis13/common.js&oldid=5130363 install] WikEd as a personal script on "User:Vladis13/common.js" with same code.

Using: Mediawiki 1.43.0-wmf.4, Chrome Linux 123, WikEd 0.9.155 (Nov 5, 2017). Vladis13 (talk) 00:28, 13 May 2024 (UTC)

:Gadgets are not executed in the global scope. You need to use window.wikEdConfig = {}; to define a global variable in a gadget. Also, you don’t need to create <script> elements manually: the entire line 4 could be replaced by mw.loader.load( '//en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript' ); —Tacsipacsi (talk) 17:23, 14 May 2024 (UTC)

::Thank you, this works! Vladis13 (talk) 22:47, 14 May 2024 (UTC)

https://bugzilla.mozilla.org/show_bug.cgi?id=579760 was resolved as fixed because the repros do not show the bug anymore so it was assumed fixed somehow. Does this affect any other bug?  AltoStev (talk) 02:36, 23 June 2024 (UTC)

How can wikEd be uninstalled via a user's common.js? -- Jtneill - Talk 11:25, 18 August 2024 (UTC)

:User:Jtneill, you may need to open User:Jtneill/common.js and remove

mw.loader.load( '//en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript' );

:You may also want to open Special:Preferences > Gadget : search wiked and untick it. Yug (talk) 🐲 19:06, 16 September 2024 (UTC)

Maybe wikiEd doesn't plan for a darkmode, but there are some features in this editor that really stands out (image preview), so I just tried it again and one of the main downsides I found is that it is broken in darkmode.

I suggest at least using the following css snippet that can make it more compatible with dark mode.

/* this works in WP, but idk in mediawiki */

/* it uses some css variables probably only found in WP current vector layout */

.wikEdConsoleWrapper{

background: light-dark(#f0f0f0, var(--background-color-neutral));

border: 1px solid light-dark(#c0c0c0, var(--border-color-base));

}

/* or use this, as it is more sure to work everywhere: */

.wikEdConsoleWrapper{

background: light-dark(#f0f0f0, #27292d);

border: 1px solid light-dark(#c0c0c0, #72777d);

}

-- Arthurfragoso (talk) 00:18, 3 January 2025 (UTC)

:[https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/light-dark light-dark] is pretty new (hasn’t been available for a year in any major browser except for Firefox, and isn’t available in all Firefox ESR versions currently supported by Mozilla – which are 115 ESR and 128 ESR), I don’t think we should use it in a gadget with such widespread usage.

:The used CSS variables are not enwiki-specific and should work on any fairly new MediaWiki install with the Vector 2022 skin (e.g. all WMF wikis, including Commons, Wikibooks etc.). However, in order to support all skins and to be absolutely sure, use them with the fallback parameter, e.g. var(--background-color-neutral, #eaecf0) – which would also mean light-dark becomes unnecessary, as the variable itself is light/dark aware (without relying on the light-dark CSS function). So my (absolutely untested) proposal is:

.wikEdConsoleWrapper {

background: var(--background-color-neutral, #eaecf0);

border: 1px solid var(--border-color-base, #a2a9b1);

}

(I’ve used the default light mode colors of the variables as the fallback, not the colors in the above proposals, so that the same color appears in light-mode Vector 2022 and in Vector 2010/Monobook. Maybe other colors would be closer/better: feel free to use different Codex design tokens, but please keep the consistency between the light-mode color and the fallback color.) —Tacsipacsi (talk) 23:54, 3 January 2025 (UTC)

::Thanks for the full explanation. I agree with you. :) — Arthurfragoso (talk) 00:28, 4 January 2025 (UTC)

::Just a note, it still valid to use light-dark in other wikipedia templates, we can increase compatibility by:

::

background-color: white; /* fallback to get 100% browser compatibility */

background-color: light-dark(white, black); /* will be applied if the browser has support */

::As dark mode users usually don't use older browsers, this should work for most of them. Arthurfragoso (talk) 15:57, 28 January 2025 (UTC)

See Wikipedia:Help desk#Editing my Raw Watchlist ([https://en.wikipedia.org/w/index.php?title=Wikipedia:Help_desk&oldid=1276550313#Editing_my_Raw_Watchlist permanent link]). PrimeHunter (talk) 14:27, 19 February 2025 (UTC)

I have wikEd enabled in gadgets, using Monobook. The button appears at the top right and I have it enabled. But the toolbar doesn't load, except for a short period while I was editing today (it was difficult to use with dark mode though). I'm using Chrome 134.0.6998.89. – yutsi (talk) 01:35, 20 March 2025 (UTC)

:Going to Special:EditWatchlist/raw made it work somewhat. The middle section of the toolbar disappeared and the whole editing pane (in light mode) was completely white with no outline (none of the watchlist items were visible until I turned off wikEd).– yutsi (talk) 01:40, 20 March 2025 (UTC)

Within wikEd not working for me. Not sure if others are having problems? All I can get to work in the find and replace one at a time. Doc James (talk · contribs · email) 19:05, 10 May 2025 (UTC)

:Works for me (Firefox); just tested a global replace. First enter term to replace, and replacement; then select text (ctrl-A for all text), then the double red arrow at bottom left of WikEd's find panel. May depend upon browser? Best wishes, Pol098 (talk) 13:00, 11 May 2025 (UTC)

::By the way, with Firefox in particular (not other browsers), WikEd messes up line spacing, removing some breaks between just-edited paragraphs, adding blank lines between asterisked list entries. Started over a year ago, already reported here and shown at top of this WikEd User Talk page. Pol098 (talk) 13:00, 11 May 2025 (UTC)

:I couldn't reproduce this, but i think what might be happening is a confusing UI. In WikiEd, the replace all button replaces all in a selection if something is selected, and otherwise the entire document. However when you first type in the thing to find, that automatically highlights the first instance, which means when you eventually press the replace all button, its only going to replace that instance unless you deselect it. Bawolff (talk) 21:25, 20 May 2025 (UTC)