There are still duplicated code and inconsistent behavior in Special:Translate PHP and JS side. Should be migrated to all JS.
|Open||Soda||T128137 Stop using onclick attributes and global functions in Translate js|
|Resolved||Nikerabbit||T132546 Remove code for the old non-TUX UI|
|Resolved||Nikerabbit||T50207 Remove TUX PHP code from Special:Translate in favor of JS code|
|Open||None||T72282 [TUX] Create easily reusable message editor component|
|Open||None||T110687 TUX message list assumes all messages are translated into same language|
(In reply to Niklas Laxström from comment #0)
There are still duplicated code and inconsistent behavior in
Special:Translate PHP and JS side. Should be migrated to all JS.
Niklas: Could you please elaborate / paste some function or file names, so a contributor could theoretically have enough information to start working on this?
(Generally, such short descriptions might work well and are clear enough for "insiders" in the team or as a quick private to-do list, but are less helpful to enable somebody else to pick up such a task.)
Much of SpecialTranslate.php and some of ext.translate.special.translate.js are starting points.
I'm not really expecting outsiders to do this without discussing with me first. This involves some non-technical issues like whether it is okay to remove the non-JS fallback and that some features are even still not present in TUX.