[MGNLUI-6188] Asset upload field in legacy apps: showing encoded html Created: 07/Sep/20  Updated: 07/Mar/22  Resolved: 31/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: dialogs
Affects Version/s: 6.2.6
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Frank Sommer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File collapsed-upload.png     PNG File large-preview.png     PNG File unsupported.png     PNG File wrong-encoding.png    
Issue Links:
duplicate
duplicates MGNLUI-6642 Labels with HTML Closed
duplicates MGNLUI-6140 Visual issue with image preview of up... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: M6 UI & UX Improvements

 Description   

The asset upload field in legacy apps has a visual bug:

Confirmation message show encoded html
HTML characters showing

HTML characters and special encoded characters showing

The issues is reproducable on demoauthor in the contacts app.

Notes
There is actually two issues here.

  • First is the html characters showing. The picture shows the line break <br />. It can also be seen when uploading "an unsupported type", screenshot added.
  • Secondly, in the wrong-encoding screenshot there is also special characters in the filename. So that is possibly another issue. Maybe they have the same fix but both should be tested.


 Comments   
Comment by Simon Lutz [ 21/Sep/20 ]

Initial point 1 and 2 are fixed by MGNLUI-6140 in 6.2.3. Re-wrote the ticket.

Comment by Richard Gange [ 31/Mar/21 ]

We will widen the scope (point 3) with MGNLUI-6642. HTML characters should be allowed but only ones that cannot exploit the system.

Generated at Mon Feb 12 09:34:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.