[Arguable Bug] CSS indent doesn't occur on first line

[Ryan Williams]

One thing that's irked me but I've never reported for some reason is the CSS auto-indentation.

Although it indents nicely for the most part (barring the "if you wrap onto two lines it doesn't indent properly" throughout WeBuilder bug I reported a while ago), the first line of the CSS never seems to indent.

Although it puts an indent in when it automatically creates the braces, if you go back later to add a first line to the CSS it doesn't indent and you have to indent it manually. It'd be nice if WeBuilder could look at the lines after it and if they're indented it indents the first one too.

[Karlis]

So you are referring to the indentation of the first line? Actually there is no special feature for this.

It simply takes the same indent as the previous line. Why? Because all other CSS and code editors we tested do the same, so I felt like it is ok.

Does this bother you a lot? What do others say?

[syrupcore]

it doesn't bother me much except that when I hit tab to indent the line and the code hints box opens up, I can't hit tab to indent. First you have to hit escape to close the box and then tab but then once you tab, the code hints box doesn't come up. cross my eyes a little on this one.

A related problem comes up more for me. I use a snippet for "{}" on occasion when I only want a certain declaration to take a single line instead of three (usually when there is only one thing to declare, like .error{color:red}.

so, I type .error and then hit my shortcut to fire the snippet. my cursor lands between the braces but no code hints appear. If I hit tab, still no code hints but if I instead hit space, code hints comes up.