font is not
Feedback and discussion page for the Two Column Edit Conflict View.
New (Feb 2018): Based on feedback and further research we have developed an alternative prototype for the Two Column Edit Conflict view that can now be tested on a test wiki: Testing and feedback is much appreciated!
font is not
Hi @Mosa Daniel Mooki Bw, thanks for the feedback! The too big font should be fixed by tomorrow.
Ok Sir.But who will do the job?
Hello. I use your tool a lot of time and like it very much, but this time something is wrong. The right column has font size of about 1000%. Thank you.
Thank you. It's much bigger for me, but seems it depends on browser.
Hi @Evad37, Thanks for reporting this incident. This is nothing we intended to show up. We guess it might be related to gadgets you might use. Could you give us some insights on that? To reproduce this issue or try out the current beta-version you can go to the edit conflict simulation page. We are looking forward to hear some more details. Thank you!
Hi Hanna. I have the following gadgets enabled:
Other beta features I have enabled are:
I also have several user scripts (w:User:Evad37/common.js), but I don't think any of them interact with the editing area. I also have a bunch of css for overriding the Vector typography refresh (m:User:Evad37/global.css) and various other changes (w:User:Evad37/common.css).
And I'm using Google Chrome (version 63) on Windows 7.
I haven't been able to reproduce using the edit conflict simulation. Though I've noticed the simulation doesn't have the proper CharInsert toolbar (shows up in "copy and paste" mode instead of click to insert like in my screenshot above), and it also doesn't have the Wikitext syntax highlighting active.
The two column edit conflict handling is currently in beta and regarding your post: Clearly, in comparison to the 'old' edit conflict handling it uses more elements, colors and dialogue boxes. To help new users there we show a small walk-through tutorial on first sight.
With all that we try to solve the problem, that users in the past a) had no idea what happened or whether something has happened at all and b) found it annoyingly complicated to resolve conflicts with the 'old' interface. We gathered feedback around that from many editors and as a result came up with the current version.
However, this is a beta feature test with the goal to find out, if the workflow of the new interface works well under live conditions. For this, any feedback is welcome and valuable to improve the current version of the feature. So far the reception was quite good, but also some users pointed out that the interface could be more intuitive. So we are open for suggestions and ideas.
p.s.: As edit conflicts do not appear quite often we are currently working on a simple way to simulate them with the new interface so users can test it more easy without having to wait for a conflict to appear. If you're interested I will get back to that in this thread as soon as it's deployed.
After once having selected the version, that should be shown in the editor (right column) I can't change to the other version any more. I would regard it as helpful if a button would be added that makes such a change possible. The button should create a message that informs the user that if the version is changed now any changes made in the right column will be overwritten by the version to which is changed, followed by the buttons "change to ...version" and "cancel".
The feature is very helpful and improves the solving of edit conflict a lot.
@JoKalliauer, thank you so much for the nice feedback! :-) In case you want to test the new interface more: We've just implemented a test page where you can get simulated edit conflicts. For more informations please see for the German or for the English version.
Everytime I have an edit conflict, the system asks me which version I want to edit - the current one, or the one that I've been editing. And everytime I make one and the same choice (which is I choose to edit the current version and just copy and paste my own text). So my suggestion is to make it remember my choice to save my (and other experienced editors') time, but leave some descreet option to switch it on the go, if it's technically possible, of course. If it's not, I would like to have such an option in the preferences - thus only really experienced users, who really know what they prefer, would be able to use it.
Thanks for you description of the problem! I know that my college Hanna is currently thinking about improving the dialog, I mention her here so she gets to know about this issue – @Hanna Petruschat (WMDE)
on wikisource, in Page edition mode (page image with text box on the side), this gadget totally breaks edition, with the total disparition of the image...
Not good at all !
I second Hsarrazin feedback. It also breaks the Index namespace interface.
Thanks for the feedback you two, I created a ticket on Phabricator and we will look at the issue. If you stumble over an edit conflict again, it would be great if you could provide us some screenshots.
Little follow up here: This is actually a duplicate of https://phabricator.wikimedia.org/T176393 - so there is already work being done to fix that.
You may want to look at this feedback: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Edit_conflict_options_spoiling_my_edit
Hi, I'm using this feature on English Wiktionary. It works great, except the dialog is way too wide. I mean the dialog that says "What should initially be in the editor and serve as a basis for combining the conflict versions?", and is over the right text box. It extends way to the right of the page content, so I have to scroll to the right in order to find and press the "OK" button. Could you make the dialog be the same width as the right text box?
Well, I have a medium-sized laptop, perhaps 15 inches diagonally. Another factor is that I typically have my zoom size set to 150% while viewing English Wiktionary. Anyway, I reopened this because the problem still exists: see File:Two column edit conflict bug.png.
the issue should be fixed by now. I tested it with zoom and narrow screens. You should now always be able to reach the OK, button. It would be great if you could confirm though.
Thanks and best,
Sorry for the slow response. I had to wait for an edit conflict before I could respond. I just had an edit conflict and the dialog box looks fine now. Thank you so much!