When we implement the optimization, we'll probably have multiple levels. The default level will only make changes that we know to be safe. This will involve some selector re-ordering, but only to the extent that we can prove that the re-ordering won't change the semantics (this will not take imported files into account). The higher level will assume that selector order doesn't matter for your stylesheet and re-order more aggressively.
On Mon, Feb 1, 2010 at 9:37 AM, Divya Manian <[email protected]> wrote: > Hi all > > On 2/1/10 9:20 AM, "Chris Eppstein" <[email protected]> wrote: > > > It's also worth noting that the merged file like this can yield different > > results in the corner case where selector order changes for selectors > having > > the same weight and both match the same element and modify the same > property. > > But, as a start is it not possible to combine selectors which have the same > specificity & are in different Sass files? Possibly, the declarations that > are "imported" earlier come first before the declarations in other imported > files. > > I think that will be sufficient for now, I am also worried about repeating > the same selectors (with same specificity) just because I use _fonts.sass > and _colors.sass ("body" selector gets repeated thrice, in fonts, colors, > and my screen.sass). > > Regards, > Divya > > > -- > You received this message because you are subscribed to the Google Groups > "Haml" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected] <haml%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/haml?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/haml?hl=en.
