Merge multiple CSS transforms / sync styles across behaviors about scrollmeister

[Prinzhorn]

What if one behavior just sets the background to red, but another behavior animates the color? The first behavior would only need to apply the style in attach and remove it in detach. The other needs to do it for every scroll.

Let me fall back. What is it that I'm actually trying to solve?

• Merging multiple transforms from different behaviors (layout + transform)
• I'm also trying to sync render and scroll calls bc right now render doesn't have access to the layout engine
• Possibly add prefixes transparently

[Prinzhorn]

I'm also trying to sync render and scroll calls bc right now render doesn't have access to the layout engine

that's fixed by now

[Prinzhorn]

Instead of making it a behavior itself I've put it in the core of Behaviors themselves. Using this.css.translate = 'foo' inside a behavior gives you all the things mentioned above. It will transparently store styles from multiple behaviors and merges them. You also don't need to clean up just like this.listen. The behavior will remove your styles for you. Why can't everything be so simple?

There is just one little thing we need to take care of: ordering. Especially in the case of CSS transforms we need to have a consistent order, because the order of transform operations matters. This is tricky because two behaviors that don't have a common dependency do not have a guaranteed order in which they are attached.

[Prinzhorn]

There is just one little thing we need to take care of: ordering. Especially in the case of CSS transforms we need to have a consistent order, because the order of transform operations matters. This is tricky because two behaviors that don't have a common dependency do not have a guaranteed order in which they are attached.

The actual order in this case is not important (there simply is no intrinsic order) but we need to make the order consistent. For the most important case (layout -> transform behavior) the order is given by the dependencies. However, we currently don't have a linearized list of behaviors. We will create and update this list every time defineBehavior is called (divide-and-conquery the problem down to a single behavior and its position within the list). This list can then be used by both the attachBehaviors call and the applyBehaviorStyle method.

[Prinzhorn]

The order is now consistent with the order the behaviors are defined.