in Safari I am getting this error:
Error: Quick Edit could not associate the rendered entity field markup (with [data-quickedit-field-id="profile/2/field_profile_address/und/default"]) with the corresponding rendered entity markup: no parent DOM node found with [data-quickedit-entity-id="profile/2"]. This is typically caused by the theme's template for this entity type forgetting to print the attributes.
but it works for other fields.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | quickedit-address-test-2968213-9.patch | 6.7 KB | sickness29 |
| #3 | 2968213-quickedit-does-not-work-with-address.patch | 454 bytes | socialnicheguru |
Comments
Comment #2
socialnicheguru commentedI do not see the error on initial page load.
In this case the page is a profile with an address field.
I click edit then save.
Then the error comes up
Comment #3
socialnicheguru commentedComment #4
socialnicheguru commentedComment #5
dwwCan't we put the attributes on the existing
<p>tag instead of introducing Yet Another Div?Comment #6
dwwAlso, does this work with the default formatter, but not plain?
Finally, it'd be great to have some tests related to this.
Comment #7
sickness29 commentedAdded test to check quickedit with address field using both plain and default formatters.
I have not included original fix from #3 because tests do not fail and I was not able to reproduce issue in safari for both article_test content type and for test profile type I created.
Let me know if we still need to add attributes to p element to make sure those attributes are not lost.
Comment #8
sickness29 commentedFixed small code standards issue
Comment #9
sickness29 commentedLooks like it won't pass because quickedit is deprecated and we need to mark it as legacy group test. hopefully passes this time
Comment #10
bojanz commentedBig thank you for writing a test and confirming quickedit now works, sickness29!
However, I don't think it's wise to commit this test, because it can't pass on D10 (where quickedit doesn't exist anymore), and 8.x-1.x wants to keep working on D10 since people won't move to 2.0.x immediately.
So, perhaps it's best to just mark this as fixed?