Change Details

The section translation unit we defined has the following problem. It behaves like a placeholder in translation column, onlick get translated. But, `mw.cx.dm.SectionTranslationUnit.static.matchTagNames = mw.cx.dm.SourcePage.static.sectionTypes;` and `mw.cx.ui.SectionTranslationUnit.static.matchTagNames = [ 'section' ];` This mismatch causes translation of tables buggy. As of now, when a table section is clicked, the table get copied to translation column, and source copy is removed(cloning issue). This is because table is also a section as per data model, but in ui, it behaves like a section with placeholder ( mw.cx.ui.SectionTranslationUnit.prototype.translate is problematic)

The section translation unit we defined has the following problem. It behaves like a placeholder in translation column, onlick get translated. If there are block level translation units inside the section, for example, Tables, the whole table get disappeared from source column

The section translation unit we defined has the following problem. It behaves like a placeholder in translation column, onlick get translated. But, `mw.cx.dm.SectionTranslationUnit.static.matchTagNames = mw.cx.dm.SourcePage.static.sectionTypes;` and `mw.cx.ui.SectionTranslationUnit.static.matchTagNames = [ 'section' ];` This mismatch causes translation of tables buggy. As of now, when a table section is clicked, the table get copied to translation column, and source copy is removed(cloning issue).If there are block level translation units inside the section, This is because table is also a section as per data modelfor example, but in uiTables, it behaves like a section with placeholder ( mw.cx.ui.SectionTranslationUnit.prototype.translate is problematic) the whole table get disappeared from source column