hitting return on the first CSS declaration

[syrupcore]

Starting with this code:

Code: Select all

.products{
    float: left;
    list-style-type: none;
    margin:10px 0;
}

If you put your cursor right before the "f" in float and hit return it ignores it's current tab position. you get this:

Code: Select all

.products{

float: left;
    list-style-type: none;
    margin:10px 0;
}

If you put your cursor right before the l in list-style-type it respects the current declaration's tab position. you get this:

Code: Select all

.products{
    float: left;

    list-style-type: none;
    margin:10px 0;
}

Is this happening to anyone else? I'm on 9.0.0.97.

Thanks,
Will

[MikeyB]

Hi Will,

Yes, can replicate the same here, also version 9.0.0.97

Mike

[chrisjlocke]

Kinda makes sense, as you're adding a new line based on the tab positions on the previous line (sort of...)
Its also a bug, as I guess it should be adding a line based on the current line tab positions.

A workaround (or the way I normally do it) is if I want a new line above float: left;, then put your cursor at the end of .products { and then hit Enter.

A similar thing happens in Word. Hit Enter at the start of a sentence with tabs, and its put on its own line (ie, disregarding the tabs) so this may be 'by design' in the editor engine.

[Karlis]

It makes sense, but it is not a bug. There is simply no special support or analysis. I'll think about improving this maybe.

[syrupcore]

Moving to feature requests.

It would be nice. Not really a new feature as much as a refinement of a good feature.

[Gatis]

Yes, it seems syrupcore is right about how this should work.