Amarande al'Kalin
Gaidin
- Joined
- May 5, 2006
- Messages
- 1,947
- Age
- 44
- Location
- Illinois, USA
- Pronouns
-
- She - Her
- Discord
- ladyvivian
I'm not sure if this one is a browser-specific issue or a vB issue in general, but at least on Chrome, I run into it quite often.
For some reason, whilst using the WYSIWYG post editor, if you use certain modifications to text (bold, italic, etc.) in the natural-seeming manner (that is, the way you'd usually do it in say a word processor, turning on bold/italic/etc. before you type in the text to be emphasised and then turning it off afterwards, rather than just typing everything out as normal and then going back to bold/italic stuff afterwards), it causes strange effects on cursor position:
* If you continue simply typing, the cursor continues to move with your typing as normal, no evidence of any glitches at all, but -
* If you press certain keys, most notably Enter or Backspace, instead of taking effect at the present cursor position as you'd expect, the action takes place at the place where you last activated or deactivated bold/italic/&c. and moves the cursor there. However, it only seems to do this once per incident, if you cursor/click back to where you were before the jump, further backspaces/Enters/etc. function like they should.
E.g., you type "This is a test sentence", hitting Ctrl-I to activate italics before the word "test" and then again to deactivate it afterwards.
As you're typing "sentence" the cursor moves normally.
But, if you try backspacing, for instance because you mistyped "sentence" and need to correct it, instead of going back one space as expected, the cursor will jump back to the end of the word "test" and instead delete the last T ...
Or if you hit Enter after "this is a test sentence", the cursor snaps back to the end of "test" then too and inserts the newline in between "test" and "sentence" rather than placing it at the end of the sentence like you'd think it would.
Any idea why this happens? Can we fix it on the vB end or is this is a defect in Chrome, time to revert to Firefox or IE?
For some reason, whilst using the WYSIWYG post editor, if you use certain modifications to text (bold, italic, etc.) in the natural-seeming manner (that is, the way you'd usually do it in say a word processor, turning on bold/italic/etc. before you type in the text to be emphasised and then turning it off afterwards, rather than just typing everything out as normal and then going back to bold/italic stuff afterwards), it causes strange effects on cursor position:
* If you continue simply typing, the cursor continues to move with your typing as normal, no evidence of any glitches at all, but -
* If you press certain keys, most notably Enter or Backspace, instead of taking effect at the present cursor position as you'd expect, the action takes place at the place where you last activated or deactivated bold/italic/&c. and moves the cursor there. However, it only seems to do this once per incident, if you cursor/click back to where you were before the jump, further backspaces/Enters/etc. function like they should.
E.g., you type "This is a test sentence", hitting Ctrl-I to activate italics before the word "test" and then again to deactivate it afterwards.
As you're typing "sentence" the cursor moves normally.
But, if you try backspacing, for instance because you mistyped "sentence" and need to correct it, instead of going back one space as expected, the cursor will jump back to the end of the word "test" and instead delete the last T ...
Or if you hit Enter after "this is a test sentence", the cursor snaps back to the end of "test" then too and inserts the newline in between "test" and "sentence" rather than placing it at the end of the sentence like you'd think it would.
Any idea why this happens? Can we fix it on the vB end or is this is a defect in Chrome, time to revert to Firefox or IE?
That is why I just usually change such things after I have written the whole post 
