[MGNLUI-6555] richtextfield expand button makes it only wider not higher Created: 12/Feb/21  Updated: 04/Aug/22  Resolved: 04/Nov/21

Status: Closed
Project: Magnolia UI
Component/s: dialogs
Affects Version/s: 6.2.9
Fix Version/s: 6.2.13

Type: Bug Priority: Neutral
Reporter: Tomáš Gregovský Assignee: Jakub Petras
Resolution: Fixed Votes: 0
Labels: VN-Testing
Remaining Estimate: Not Specified
Time Spent: 1h
Original Estimate: Not Specified

Attachments: JPEG File 1.jpg     JPEG File 2.jpg    
Issue Links:
Relates
relates to MGNLUI-6096 Rich text field: move expand button t... Closed
relates to MGNLUI-7414 Huge space in dependency tab Closed
relation
is related to MGNLUI-6420 M6 sub-apps do not have an expand option Closed
is related to MGNLUI-6444 Chooser dialogs: expand vertically to... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: UI bugs
Story Points: 3

 Description   

Problem:

  • using expand button in richtext field opens new dialog with new richtext which is only wider, but not higher. see screenshots.
  • in case the original dialog has wide:true then then is almost no different between expanded and original area.

 

Goal:
The goal of this improvement is to expand the rich text field vertically when using the expand option.
At the same time, for any dialog, we will introduce a max. width.

Acceptance criteria:

  • Upon click on the expand button in RichTextFields (MGNLUI-5218)
    • Width: if <1500px full width ((30px spacing between browser border and dialog), max width=1500px
    • Height: full height (30px spacing between browser border and dialog)


 Comments   
Comment by Annick Boehler [ 19/Aug/21 ]

Hi,

may I ask about the status of this ticket? 

Thanks 

Comment by Roman Kovařík [ 04/Nov/21 ]

Reopening and changing to Resolved as this was probably closed by mistake (still needs the final QA)

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