1 | | I would have to setup a test case to check this out but having run through changes with the template pack a while back and given the nature of our JS & Ajax making this sort of change is tricky and always likely to break, I think it's less likely we have a bug here as much as just have some fairly precise requirements in markup structure and tokens, however I may have missed some detail in the opening comment and I haven't looked at r-a-y's patch which suggests there was something to fix. I'll try and setup a testcase when I have a minute to see what's occurring. |
| 1 | Revised my comments after actually reading r-a-y's comments and patch. |
| 2 | |
| 3 | Think the proposed change makes sense, as always this will affect anyone that has overloaded templates so we'll need to be clear in announcing those template changes. |
| 4 | |
| 5 | Would like to test patch and see things in action. |