Thank you so very much!!! :smiley: yeah also in my PR comment I wasn't totally sure if this was a breaking change but yeah since those can be referenced in js code it does really seem like a breaking change!
I also totally agree, that identifying the problem can be quite difficult especially in complex projects, whilst the workaround is straightforward.
Another thing that I don't like is that this kind of breaks angular's view encapsulation contract by actually leaking some css unbeknown of the user (opposite to what happens to the native shadow dom).
About the scope name being a suffix, I think you are right, I didn't really put much thought on where to put the scope name to be honest (by prefix felt natural as it is sort of what happens with classes, the scope gets put before the actual element), I will amend it :slightly_smiling_face: