[wp-trac] [WordPress Trac] #28602: Transparently route frontend browsing through Customizer for logged-in editors
WordPress Trac
noreply at wordpress.org
Sat Jun 21 00:27:36 UTC 2014
#28602: Transparently route frontend browsing through Customizer for logged-in
editors
-------------------------------------+------------------------------
Reporter: westonruter | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Customize | Version: 3.4
Severity: normal | Resolution:
Keywords: needs-patch ux-feedback | Focuses: ui, javascript
-------------------------------------+------------------------------
Comment (by azaozz):
Not sure this is a good idea.
1. Why would we want the logged-in admins to browse the front-end in a
"constant" preview? It has a substantial overhead and quite a few quirks
(compared to a no-iframe, no extra JS browser tab), not even talking about
multisite, domain mapping, ssl/no ssl, etc. It would also break or cause
problems for many plugins and themes that "do more" on the front. Things
like P2, front-end editors, infinite scroll, etc.
2. Even if we spend the time/effort on making this work and not have back-
compat problems, what are the benefits? A bit faster loading of the
customizer if an admin clicks an "Edit" link (not for post or comment) on
the front-end? How often does that happen and is the faster loading worth
it, considering the increased complexity and potential incompatibilities?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/28602#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list