Last modified: 2014-07-30 21:23:30 UTC
Created attachment 16035 [details] screenshot Test Environment-test2 and betalabs Steps- 1> open a blank page in VE. 2>type some text and at the end of the last character (could be a space after the text or the last character in the text itself) insert a comment. 3>Now click to move the cursor after the comment, this closes the comment dialog too. 4> Insert a whitespace.I cannot see the cursor at this point. 5> click on the page again and the cursor appears before the start of the line. 6>Hit the spacebar and then press backspace key. A pawn appears next to the comment. Please see screenshot_chrome. In Safari- Try the same steps and at step#6 I get the WebKit2WebProcess.exe dialog saying “WebKit2WebProcess.exe has encountered a problem and needs to close.”. After I click to send the error report and I get logged out of my account. In FF 31- no issues were found when whitespace was inserted after a comment.
did a fresh install of Safari, still getting WebKit2WebProcess.exe message.
Confirmed
I can't reproduce this now, Roan couldn't either. Ritu, does this still happen for you?
(In reply to Alex Monk from comment #3) > I can't reproduce this now, Roan couldn't either. Ritu, does this still > happen for you? I can reproduce it in test2 , but not in beta.
Sounds like it was fixed in wmf15 then.
(In reply to James Forrester from comment #5) > Sounds like it was fixed in wmf15 then. a bit confused, i can reproduce it in test2 with the release version 1.24wmf15 (148011a).
Sorry, yes, I meant wmf16. My apologies!
thank you. just for future.. this is not the right forum .. but how can i find the release version of beta? if a bug is not reproducible in beta , but it is in test2 , then can it be called fixed?
(In reply to Ritu Swain from comment #8) > thank you. just for future.. this is not the right forum .. No problem. :-) > but how can i find the release version of beta? Unhelpfully, it's not present of beta (because it doesn't exist yet), but the specific version of VisualEditor can be found inside VE itself: If you go to a page and enter VisualEditor, click on the help menu – "(?)" in the toolbar on the right (left if RTL). The version hash will be at the bottom of the menu. mediawiki.org is currently running "Version ce427f4 18:49, 29 July 2014". en.wikipedia.beta.wmflabs.org is currently running "Version 3dd63f7 20:00, 30 July 2014". > if a bug is not reproducible in beta , but it is in test2 , then can it be > called fixed? Normally, as long as we think it's actually fixed. Sometimes other changes can have ripple effects, but sometimes it's caused by the local wiki's configuration (or something else), so it's not a perfect call each time, sadly.
(In reply to James Forrester from comment #9) > (In reply to Ritu Swain from comment #8) > > thank you. just for future.. this is not the right forum .. > > No problem. :-) > > > but how can i find the release version of beta? > > Unhelpfully, it's not present of beta (because it doesn't exist yet), but > the specific version of VisualEditor can be found inside VE itself: > > If you go to a page and enter VisualEditor, click on the help menu – "(?)" > in the toolbar on the right (left if RTL). The version hash will be at the > bottom of the menu. > > mediawiki.org is currently running "Version ce427f4 18:49, 29 July 2014". > > en.wikipedia.beta.wmflabs.org is currently running "Version 3dd63f7 20:00, > 30 July 2014". > > > if a bug is not reproducible in beta , but it is in test2 , then can it be > > called fixed? > > Normally, as long as we think it's actually fixed. Sometimes other changes > can have ripple effects, but sometimes it's caused by the local wiki's > configuration (or something else), so it's not a perfect call each time, > sadly. thank you :)
