Hello. Thank you for contacting the Toolset support.
As you can see with the errata page - this issue is resolved with Toolset Views 2.6 but I need to test this again with current views version.
Can you please share access details and problem URL so I can see how exactly you setup your view with content template and then I will try to reproduce this issue on clean install and if reproduced successfully, I will escalate it to our Devs.
I have set the next reply to private which means only you and I have access to it.
When I logged in to wp-admin and checked the plugin page I found that you are using "NAF Page Builder" - which builder is this? Then I found you are using NAF theme, is Beaver Builder is bind to this theme? If yes, it will be theme compatibility.
I checked with normal Beaver Builder Pro plugin version 2.2.5 and I do not see that issue. Please check the following image.
=> hidden link
It looks like the issue is from your theme how it loads the Beaver Builder assets.
The 'NAF Page Builder' is the Beaver Builder plugin that is white-labeled. It's the core plugin, just with a label of 'NAF Page Builder' rather than 'Beaver Builder Page Builder'. Similarly, the 'NAF Theme' is the Beaver Theme Child Theme.
However, I figured out the solution here. When I try to insert the View via the WP Widget (screenshot: hidden link), the styles don't carry over, but when I use the Views shortcode (screenshot: hidden link), the styles carry over. Perhaps a bug?
Yes - I confirm that when view is added using widget its not loading the style. I will escalate this issue to next level support. Please hold on for further updates.
I've got the news from the next level support that the issue you are experiencing is not a bug, it is a conflict between 2 template builder and content renderers.