Ok ... when I initially replied I was getting mixed up with the thread on field name placement so what I wrote might have seemed a bit garbled :) I thought it was just another link to
But yes that #17516 is my error. I still think it's because the rules are somehow applying with reverse precedence. And actually I think that #17320 is showing the same sympton, the hyphened rule
should be applying because that does currently work, but instead the first one is taking precedence.
Basically I discovered this when I was testing the double underscore for targetting specific fields. Double underscore seems to be acting effectively as a wildcard, so those rules affect
all fields. So I tested with:
What happened here is that both fields were placed at Content:3. So I tried:
At this point both fields are placed at Content:4.
Both fields placed at their correct positions.