Hiya,

I "think" that this isn't supposed to do this, but correct me if I'm wrong and tell me what I'm doing wrong if it's working like it's supposed to.

When I go to the Tags tab and change it to CSS I've tried a few different tags to enter them in and it's done this same thing for all of them.
I first find the tag I want to use such as Text-Align and I double click it to insert it into the spot of my CSS I want it to go.
Then I double click the sub setting that goes with it so that it will go right after that line such as:

• Double Click 'Text-Align' so it shows
  Text-Align [curser is here blinking];
• Double Click 'Center' with the cursor blinking as stated above right before the semi-colon ';' so it should show:
  Text-Align: center;
  
  But what it instead does is it puts the sub setting 'after' the semicolon like this:
  text-align: ; center
  
  It seems as if it's not realizing that it needs to go right where I have the cursor, either that or I'm just misunderstanding how it's supposed to work lol.

I can't replicate your issue but perhaps you can try to replicate mine;

Create a new entry in a style sheet, something like the one below.

.test {
text-align: center;
}

If I put two spaces in front of the text-align bit to indent it, all is well when using auto-complete, but if I type the letter t as the first character on that line and use auto-complete, I end up with the following:

.test {
ttext-align
}

Not only does autocomplete add text-align to the letter t instead of replacing it, autocomplete won't pop up to give me any options because it doesn't recognise the tag.

Strange goings-on indeed!

Dave.

the autocomplete does the same thing to me too if I hit enter and try doing it as you show above, but... it doesn't do that "tt" thing if you type it in the same line, then it seems to work fine.
so if you type:

.test{ text-align..... (this way works good doesn't do the double t and the autocomplete works correctly also)

instead of

.test{
text....

But it should work correctly both ways I would think.

And my problem seems to be gone also, not sure what that was about, but apparently it was just a glitch? I'll post a reply here again if it does it again.