[LRA-255] The application is not displaying the “Automatic Translation” button properly arranged after some “web content translation” languages are added. Created: 26/Jul/17  Updated: 09/Oct/17  Resolved: 09/Oct/17

Status: Closed
Project: Liferay Apps
Component/s: Content Translator
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Juan Camacho [X] (Inactive) Assignee: Emmanuel Abarca [X] (Inactive)
Resolution: Won't Fix Votes: 0
Labels: Content_Translator
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Device: MacBook Pro
Google Chrome Version 54.0.2840.98 (64-bit)

Attachments: PNG File Automatic Translation button bug.png    

 Description   
The application is not displaying the “Automatic Translation” button properly arranged after some “web content translation” languages are added.

REPRODUCIBILITY LEVEL:
====================
Always

STEPS:
====================
Steps
1.Open the Liferay APP with the configurations to use the Content Translator .
2. Click on the + icon.
3. Add a “Web Content Display”
4. In the “Web Content Display” click on the (+) icon and select Basic Web Content.
5. Fill out all the fields
6. Click on the “Publish” button.
7. Click on the Edit Web Content button.
8. Click on the Automatic Translation Button.
9. Select 2 languages and click on the continue button.
10. Review the Automatic Translation Button.

CURRENT RESULT:
====================
The application is not displaying the “Automatic Translation” button properly arranged after some “web content translation” languages are added.

EXPECTED RESULT:
====================
The application should display the “Automatic Translation” button properly arranged after some “web content translation” languages are added.


 Comments   
Comment by Emmanuel Abarca [X] (Inactive) [ 09/Oct/17 ]
Cosmetic fix.

Making the proper adjustments involves modifying aui:translation-manager taglib which would greatly increase the component's scope.
Comment by Juan Camacho [X] (Inactive) [ 09/Oct/17 ]
Bug closed as Won't Fix, the fix requires a lot of effort, and produces not a big benefit.
Generated at Sat Feb 10 05:49:45 GMT 2024 using Jira 8.1.3#801003-sha1:6b6f07cffadda9a0d6efe24639daed8ce94dcdd6.