Hi Mark! Thanks for getting back to me. 

I’m on version 11.2.11. The skuid page is deployed via visualforce but the chatter component is being included via iframe in order to make it possible for people to “use” it even though it’s janky. 

Not sure why it’s loading the classic version of chatter even though I’m in lightning experience. 

Our users still toggle between classic and lightning. What’s the best way to deploy so it works for everyone regardless of whether they are in lightning or classic?

It seems like I can’t allow for both lightning and classic overrides if I have two different pages to display based on record type. 

Mark - thanks for pointing me in the right direction. I will work on skuid page lightning component overrides for all my objects.

While it is looking a lot better and the rich text + chatter components are rendering properly I’m still running into a strange error when trying to interact with some parts of the chatter feed: https://cl.ly/6cf4b7a85665

Have you seen this before?

Here’s the error text

rCannot read property ‘tagName’ of null]

Proxy.c()@https://columnfive.lightning.force.com/resource/1541020678000/skuid__SkuidReqsJS:1:73262

Proxy.dispatch()@https://columnfive.lightning.force.com/resource/1537232010000/skuid__VendorJS:2:19404

Proxy.q.handle()@https://columnfive.lightning.force.com/resource/1537232010000/skuid__VendorJS:2:17419

Kaede, I haven’t seen an error like that before, but it sounds like something on the backend is having trouble trying to find an HTML element.  I’m glad this is looking a lot better. Would you be able to share a simple page’s XML that’s demonstrating this issue (and which actions are causing the error)? I see you’re on Skuid 11.2.11, which is just about to up-to-date. 

Also, have you by any chance tried the out-of-the-box Chatter Lightning component alongside your Skuid page, to see if the behavior persists? One of the nice things about Lightning is that you can put components alongside your Skuid pages pretty easily, so if there’s nothing about your use-case that requires the Chatter feed to be inside the Skuid page, putting it beside or below the Skuid page in the Lightning App Builder Page might be an option too.