the template for one row * 2. Fill bindings placeholder * 3. Embed slots … (shell plus content) * 4. Expand components (from the component library) * * The benefit: one rendering implementation, written in JS, inherently portable — and none of Gutenberg's * problem of a JS editor and a PHP front end drifting apart. */ class Renderer { /** * Trusted content: emitted verbatim, without kses. * * `post.content` is the output of the `the_content` filter — which WordPress core prints verbatim in every * theme (`the_content()` never runs kses). Who may write raw HTML into post content is already governed by * the `unfiltered_html` capability; running kses again at the output stage is **governing the wrong * layer**, at the cost of forms, embeds and iframes in post content being silently stripped. * * A case in point: Woo's `[woocommerce_my_account]` renders a login form, and kses removed the `
` * and all five ``s, leaving a few `