dojo.replaceClass arguments are un-intuitive replace(new, old) vs replace(old, new)
|Reported by:||ktiedt||Owned by:||elazutkin|
Since there was 0 response on the contrib list, opening a formal ticket
Since we are finally updating internally to 1.6 based code we came across dojo.replaceClass and were a bit confused by the argument orders that were chosen...
Typical replace functions *always* replace(old, new)... I am curious why suddenly this method diverged from that...
Change History (5)
comment:3 Changed 4 years ago by elazutkin
- Priority changed from high to undecided
- Type changed from defect to enhancement