- 🇳🇿New Zealand luke.stewart
Just noting here to help future me (and others) that looks like the following awesomeness can occur - that sent me deep into the weeds.
If you are displaying a content type using a display mode that uses a trimmed text field it can truncate html in a way that there is an open tag. In my case this was a
<b>because the closing tag was after the full stop.This then caused a host of drupalSettings. to be undefined, and while drupalSettings existed - it was empty. so for example drupalSettings.user was undefined causing various errors in contextual links. (adding to help search indexing).
https://drupal.stackexchange.com/questions/270863/drupalsettings-object-...
Which when I inspected source to see if I was experiencing the same - identified that there was some invalid html.While I manually corrected the broken HTML I figured it wasn't great you could break the site by accidentally highlighting the space after the fullstop to close your bold text... Which lead me here.
I applied the patch and it applied cleanly on 10.3.6 with some offsets.
In my use case I had a View outputting nodes using a summary display mode. Before and After applying the patch I still see the broken html. I'm not clear from the above if this is supposed to fix this case or not. However updating text modes to select fix faulty and broken html resolved the above.