[i]italic doing strange things[/I]
Hello Web-team, as I'd discovered 5 days ago the italic-coding in our message screen once placed and hitting the spacebar 'i' jumps to 'I' as with the regular text also so the code is wrong/invalid causing an annoying issue. I do not know if it is only 'Mac-related' or other systems have the same issue, can you shed a light on this issue?
Thanks.
Btw, ... pretty nice login screen, seeing the update. :):D
It's working fine for me. When I was limited to posting on my mobile, I noticed the italics feature would do what you're experiencing; I can only assume it was G-Board's autocorrect feature. Now that I'm back on a PC, it's working fine.
Out of interest, what browser are you using? Do you have any browser extensions?
22-Feb-2021 15:53:47
- Last edited on
22-Feb-2021 15:54:57
by
Trewavas
That very much sounds like an autocorrect feature on your computer is making that change, rather than something with the Jagex website being behind the change.
I know my current computer had a similar feature turned on in Windows when I last reinstalled the OS - it was one of the first things I disabled once I was up and running. Ultimately its up to you whether you want to leave it on or not, but if you wanted to turn it off, Google popped up the following steps for doing so on Mac:
Select "System Preferences" from the Applications toolbar. ...
Click "Keyboard." ...
Click "Text" in the top bar.
Deselect "Correct spelling automatically." This will turn off autocorrect.
Hello Web-team, as I'd discovered 5 days ago the italic-coding in our message screen once placed and hitting the spacebar 'i' jumps to 'I' as with the regular text also so the code is wrong/invalid causing an annoying issue. I do not know if it is only 'Mac-related' or other systems have the same issue, can you shed a light on this issue?
Thanks.
Btw, ... pretty nice login screen, seeing the update.
Thanks people for responding but I think you all do not understand what is going on.
If you look at my OP you can see that in-between the first 'brackets' (or you call them different) the code is written as a small letter as it should be and at the end you will see it written as a capital letter.
To correct this I need to write the post first and manually 'override' that single error. Rewriting doesn't help as it will make that issue continue to exist. Very persisting.
Even, as you can see, the (return) spaces after the italic-written text and after 'Thanks.' will disappear as you can see in the OP making it a wall of text.
And of course the smileys aren't displayed anymore.
In the quote you see what the results are when 'manually correcting the code error'.
I have used italic coding on many occasions but it was recent that it started to have its hick-ups.
To say "deselect 'Correct spelling automatically'" and everything is fixed is not the way to go as you haven't fixed anything, rather make it disappear so you will not notice. If the mistake lies in the spelling correction.
It has always been OK and all of a sudden something is badly wrong messing around with the basic coding and use of text.
2_Tron
said
:
Thanks people for responding but I think you all do not understand what is going on.
If you look at my OP you can see that in-between the first 'brackets' (or you call them different) the code is written as a small letter as it should be and at the end you will see it written as a capital letter.
To correct this I need to write the post first and manually 'override' that single error. Rewriting doesn't help as it will make that issue continue to exist. Very persisting.
Even, as you can see, the (return) spaces after the italic-written text and after 'Thanks.' will disappear as you can see in the OP making it a wall of text.
And of course the smileys aren't displayed anymore.
In the quote you see what the results are when 'manually correcting the code error'.
I have used italic coding on many occasions but it was recent that it started to have its hick-ups.
To say "deselect 'Correct spelling automatically'" and everything is fixed is not the way to go as you haven't fixed anything, rather make it disappear so you will not notice. If the mistake lies in the spelling correction.
It has always been OK and all of a sudden something is badly wrong messing around with the basic coding and use of text.
This 100% sounds like an autocorrect issue as mentioned above by an FMod, and if it doesn't seem to be something that's happening with your operating system, it might be due to your browser.
Community Manager for Jagex
How it sounds isn't helpful and certainly neither is a guessing game. As I said in my last post it was just very recent that the issue came to surface and prior to that it never was an issue at all.