[wp-trac] [WordPress Trac] #40238: WP REST API post content often relies on inaccessible enqueued JS and CSS
WordPress Trac
noreply at wordpress.org
Wed Mar 22 19:40:48 UTC 2017
#40238: WP REST API post content often relies on inaccessible enqueued JS and CSS
--------------------------+------------------------------
Reporter: mnelson4 | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone: Awaiting Review
Component: REST API | Version: trunk
Severity: normal | Resolution: maybelater
Keywords: dev-feedback | Focuses:
--------------------------+------------------------------
Changes (by jnylen0):
* type: defect (bug) => enhancement
* resolution: invalid => maybelater
Comment:
IMO this is neither invalid nor a support issue. Rather, this is a feature
of the design of shortcodes (or a deficiency, depending on how you look at
it). I hope we can do a better job of addressing this in the
[https://github.com/WordPress/gutenberg block-based editor project] by
ensuring that blocks are "serialized" to semantically meaningful HTML
during rendering.
In the meantime I would suggest providing enough information in your
rendered shortcodes to reconstruct the intended functionality, perhaps
along with a `register_rest_field` or two for extra information.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/40238#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list