Page content element

What do you mean?

Tailor produces HTML for elements that are not dynamic (e.g., the Posts element which by definition shouldn’t be static HTML). The content element, like most others, should leave HTML in the post content whether the plugin is active or not.

I mean that the plguin leaves elements like div span etc, other plugin leaves a clean content when the plugin is deactivated or removed. Suppose that i make a website with your plugin, if i choose to change page builder or delete tailor builder, my posts content will be full of code residues that i must remove manually for each posts and page.

I understand.

You’re right that that’s different to the way that Tailor works. Saving “clean” content to the post would require that additional processing of the content is performed during each front end page load so that the “builder” content is displayed properly. Tailor saves HTML content to the post itself, which means that it’s not necessary to modify the content during front end page loads.

While Tailor markup is kept to a minimum, I will consider adding this as an admin option for those that consider the tradeoff worthwhile. Thanks for the feedback!

Oh yes it is just a feedback, i think that add this as an option is the better solution!