Open Ambertvu opened 2 years ago
Hi there @Ambertvu!
Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.
We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.
Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:
@Ambertvu thanks for reporting, and apologies for the belated response.
I can reproduce this on both V10 and V11 (two different versions of the rich text editor). This is indeed a bug. I have marked it as "up for grabs" if you or anyone else would like to attempt a fix.
Anyone looking into this might want check out how Nested Content handles this exact issue. However, please don't resort to direct querying into the DOM as the Nested Content handling does it.
Could not reproduce in
So I reckon this has been fixed somewhere along the route already
Second attempt, I think I have failed to rebuild my frontend in my previous test
Could not reproduce in
So I reckon this has been fixed somewhere along the route already
Could reproduce in
Which exact Umbraco version are you using? For example: 9.0.1 - don't just write v9
10.1.0
Bug summary
When having a BLE with multiple elements with the "inline" option active, and sorting them, disables the textarea's
Specifics
No response
Steps to reproduce
Create a BLE with a component that contains an textarea Enable the inline property on the BLE.
Add the BLE to a content item. Go to the content item. Add two elements. Fill in a value in the textarea Open them both: Drag the one above the other Results:
Expected result / actual result
The contents of the textarea remain visible.