[wp-trac] [WordPress Trac] #39612: (Resolve) Error due to Backbone.History being started again
WordPress Trac
noreply at wordpress.org
Fri Jan 20 23:59:25 UTC 2017
#39612: (Resolve) Error due to Backbone.History being started again
----------------------------+------------------------------
Reporter: tfrommen | Owner: adamsilverstein
Type: enhancement | Status: assigned
Priority: normal | Milestone: 4.8
Component: Administration | Version:
Severity: normal | Resolution:
Keywords: needs-patch | Focuses: javascript
----------------------------+------------------------------
Comment (by adamsilverstein):
> What version do '''you''' prefer? I think stopping and (re)starting
exactly like core it needs is better than only starting if not yet
started.
I'm not sure.
Can you provide some sample code or do you know of a plugin that does
this? I'd like to test how history behaves in the 2 scenarios. my first
instinct is the first version: only start in not started already -
assuming history still works as expected.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/39612#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list