[CONTEDIT-98] Fix rows for title and leadText in editor config once bugs in plugin have been resolved Created: 07/Apr/17  Updated: 04/Apr/23  Resolved: 04/Apr/23

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: blocked
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to CONTEDIT-68 Dynamic input fields that grow in hei... Closed
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:
Story Points: 5
Team: AuthorX

 Description   

The plugin (https://vaadin.com/directory#!addon/expandingtextarea) used for expanding the text fields for title and leadText used in CONTEDIT-68 has two small bugs:

  1. Initial rows is at least 2 (and cannot be set to 1 – as required for the title)
  2. Initial rows cannot be overwritten at all (and therefore rows of leadText cannot be set to 3)
  3. What happens if you set rows > maxRows?

Once those bugs are resolved, we should update the config again / make sure it work / update to the latest plugin.



 Comments   
Comment by Michael Mühlebach [ 01/Jun/17 ]

Blocked because of:
Limitation of the expanding text area plugin.

Comment by Michael Mühlebach [ 01/Jun/17 ]

avongunten Could you tell us how important this is? The reason is because the external plugin we use for that seems not under active development any more. So we would have to fork that codebase and "make it our own".

Comment by Anja von Gunten [ 02/Jun/17 ]

I don't see it as crucial in relation to the effort it seems to be to 'make it our own'. It would be a nice to have fix. So i suggest not to prioritize it right now. I will move it out of the fine-tuning epic.

Comment by Laura Delnevo [ 04/Apr/23 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 00:17:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.