This page used theStructured Discussions extension to give structured discussions. It has since been converted to wikitext, so the content and history here are only an approximation of what was actually displayed at the time these comments were made.
If you have never provided feedback before,you can learn how to do it effectively.If you are reporting a problem directly on this page, please include yourweb browser, computer operating system, and wiki skin (usually Vector, sometimes Monobook). The feedback tool within the visual editor will include your user agent details instead.
You can use this page to tell the Wikimedia developers your ideas and issues about using the visual editor: this is the only feedback page actively monitored by WMF staff. TheContributors team welcomes your feedback and ideas, especially on user interface decisions and the priorities for adding new features.All comments are read, in any language, but personal replies are not guaranteed: the team will try and go through reports here at least once a week. Need more attention?Report directly in Phabricator.Please note that the Wikimedia Foundation does not provide support for installing VisualEditor on third-party wikis. Please report bugs involving Parsoid atTalk:Parsoid instead.
The following discussion is closed.Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Whenever I remove a field while editing a template, the box scrolls all the way to the top, meaning if I want to delete multiple fields, I have to repeatedly scroll down, press delete, then scroll back down again because it decided to scroll up automatically, click in the next field, delete, scroll down again, etc. It's been a bug for several months, I'm currently using Chrome 66 on macOS 10.13 but it has happened for several versions of Chrome prior to 66. It wastes a lot of time and makes editing very difficult when I'm trying to remove blank parameters left in templates that don't need to be (or can't be) filled, especially in reference templates.Numbermaniac (talk)08:39, 10 May 2018 (UTC)Reply
The following discussion is closed.Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
There is a problem, very frequent at least in the french Wikipedia, where the first paragraph of the intro"fuses" with the infobox if you use the Visual Editor.
Confirmed, it's bugged when I try it. In the link above, in VisualEdit mode, it does not appear possible to directly edit the lead sentence. Trying to click on that sentence is treated as a click on the infobox. As a bizarre workaround, if you edit the infobox you can scroll down to see&edit the lead sentence in the infobox's "Content" field.Alsee (talk)06:17, 18 May 2018 (UTC)Reply
That suggests that the problem is with the infobox templates. Do those particular templates use HTML tags to set absolute positioning (such as<span>)? That was a problem once, at a different wiki, and it produced the same symptoms.Whatamidoing (WMF) (talk)17:53, 25 May 2018 (UTC)Reply
Latest comment:7 years ago3 comments3 people in discussion
Hi all
I've been working on an easy way for contributors to Wiki Loves competitions to create photo essays, the prototype ishere. Unfortunatley I have a technical issue, I'm finding that some namespaces on Commons don't allow Visual Editor (which the process relies on), I'm also finding that for some reason in my userspace for some reason signatures are dissabled in VE. Is there a page somewhere on Commons that documents where VE can be used and why it is a dissabled in some spaces, also bonus points for explaining why I can't add a signature to pages using VE (greyed out).
Extra bonus points for telling me if a new user with a fresh account will be able to use VE if a page they open has a stipulation to open in VE editing window, or if it has to be enabled by the user first.
I don't have a handy list of namespaces on Commons; @Deskana (WMF) might be able to get one for you. Generally, it is disabled in namespaces where it is likely to cause difficulties with editing, namely any namespace that contains large (think WP:ANI-size) discussion pages and technical pages (e.g., the Template: namespace).
Signatures are usually enabled only for talk pages (so that new contributors don't think that they're supposed to sign their contributions to a Wikipedia article). It might (or might not) be relatively easy to change that for userspace at Commons.
I'm guessing this thread is related toT195588, which was filed a day after this thread was made. I think that task effectively resolves the questions here. If one wishes to be specific, there will be a list of namespaces that the visual editor is enabled in on Commons in the site configuration, but I don't have the time right this minute to go digging through the configuration code to find it out. Please ping me in a few days if it's still needed, and I can probably find it.Dan Garry, Wikimedia Foundation (talk)14:41, 5 June 2018 (UTC)Reply
Latest comment:7 years ago2 comments2 people in discussion
RESOLVED
Off-topic. Simple problem solved at WP-fr.
The following discussion is closed.Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Agent utilisateur : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
Bonjour, il y a une erreur dans le nom de la page, il manque les tirets entre "Saint" "Martin" "la" "Pallu", ainsi le nom doit ressembler désormais à "Saint-Martin-la-Pallu".
Notez cependant que vous n'avez pas posté votre demande au bon endroit. Vous auriez mieux fait de le signaler sur la page de discussion de l'article concerné, par exemple, ou de procéder aurenommage par vous-même.Braaark (talk)17:47, 31 May 2018 (UTC)Reply
The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.
As it says at the top of that page, it is not officially supported any longer, although I sometimes check in if I have a few minutes (I don't think that anyone else does). Thank you for bringing your concerns here.Whatamidoing (WMF) (talk)02:32, 5 June 2018 (UTC)Reply
@Whatamidoing (WMF) I'm aware of the notice at the top of the page, but I had usually got replies on my posts there. Either way, some of these are serious bugs and should be addressed. Would it be better if I reposted each bug as a separate issue here?· • SUM1 • ·(talk)19:27, 9 June 2018 (UTC)Reply
Yes, bringing them here increases the speed at which they'll be seen, compared to posting them at WP:VEF on the English Wikipedia. But your bug reports seem to be pretty well-explained, so maybe you'd like to post them directly to the bug tracking system? It's not very different from describing them on wiki, and some of the devs watch the incoming formal bug reports closely. If you're interested, let me know, and I'll explain the process.Whatamidoing (WMF) (talk)21:42, 15 June 2018 (UTC)Reply
Templates won't work, but you can write the relevant parts free-form.How to report a bug has some advice. I often follow this pattern:
Steps to reproduce (the most important part)
Results
Expected results
followed by anything that seems relevant, such as your web browser and OS (a detail that the devs always appreciate, even if it turns out not to be important for that bug), a diff showing the problem or a page where you encountered it, and whether you have tried to reproduce it.Whatamidoing (WMF) (talk)18:31, 18 June 2018 (UTC)Reply
Also, it's really easy to add screenshots to Phabricator. Make a screenshot (however your computer does that) and drag it into the middle of whatever you're typing. It does everything automagically from there.Whatamidoing (WMF) (talk)19:15, 18 June 2018 (UTC)Reply
