[MGNLUI-4130] TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding Created: 01/Feb/17 Updated: 20/Mar/17 Resolved: 17/Mar/17 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.5.1 |
| Fix Version/s: | 5.5.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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: | Initial Article editor | ||||||||
| Sprint: | Basel 87 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
It was noticed that if the text area stretcher is attached to a field which belongs to a layout which is not our FormView - the extension fails on the client-side and causes the whole layout to break. The cause for that is the usage of the form field which is initialised in TextAreaStretcherConnector#initFormView - the field may end up being null, but then in the rest of the class it is used as if it non-null. The right way of doing it would probably be that the extension does nothing and doesn't show itself if it is not in a Magnolia dialog (all the calculations would anyway be wrong). |
| Comments |
| Comment by Andreas Weder [ 02/Mar/17 ] |
|
Raised this to major as this is a bug the article editor depends upon. |