Changes between Initial Version and Version 1 of Ticket #53801, comment 21
- Timestamp:
- 08/27/2021 01:23:19 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #53801, comment 21
initial v1 1 Using wp_head and wp_footer in the preview may indeed add some unexpected content there. At the same time, not having the preview seems like a broken experience. So there is not a single solution that could make things justright.1 Using wp_head and wp_footer in the preview may indeed add some unexpected content there. At the same time, not having the preview seems like a broken experience. Either of these seems imperfect and I don't think there is a solution that could make things 100% right. 2 2 3 3 My two cents are that we probably can't solve all the cases here, but we likely can solve most of them. To get more practical: We want to hide any extra content a) rendered by PHP and b) added in the runtime by javascript. Assuming iframed preview, I wonder if this rule would already account for most cases: `body > *:not(.allowlisted_preview_div) { display: none !important; pointer-events: none !important; opacity: 0 !important; } `.