After switching the field to output as raw, you need to resave the post where you are using this field. If this is a problem, because you have multiple posts, I suggest you use the Basic text element in Bricks to output this field.
It does not make sense to use a basic text field, change its tag to a paragraph and insert content from a WYSIWYG custom field (which itself contains paragraphs). This would result in nested paragraph tags.
So imho it’s perfectly fine to have a div wrapper (either a basic or a rich text element) which then contains the content of the WYSIWYG custom field. And in both cases it works as expected (see Meta Box WYSIWYG – Bricks).
If you really want to output the “raw value” you can use a code block and check “Render without wrapper” (see screenshot attached).
Thats a fair comment and specific to the above usecase and when you have a few paragraphs or different content. I do need to change the fields about a bit.
Just checked a few other fields and this is also happening for textarea with both single/multiple paragraphs. Here it does not make sense to add a div wrapper as you can only add text which should output multiple paragraphs.
3 elements, first 2 are basic text, 3rd is rich text all querying the mb custom field of type textarea as above and the field only has 1 paragraph - but has option for more as its a textarea field.
1 - this is fine as the basic-text tag has not been changed so remains as a div hence the div wrapper.
2 - basic-text is set as paragraph, as there is 1 paragraph in the field this produces another p tag wrapper.
3 - rich text gives a div wrapper
I noticed this says solved but I have recently run into the same problem. While adding it in a text field does work, the text field has a div element surrounding it, which means each heading will have a div around it. Is there a workaround for this?