Ticket #1222 (closed enhancement: fixed)

Opened 22 months ago

Last modified 22 months ago

backstage.init should clear existing backstage

Reported by: FND Owned by: JeremyRuston
Priority: major Milestone: 2.6.1
Component: core Version:
Severity: low Keywords:
Cc:

Description

Some plugins might want to change the default set of backstage tasks, modifying config.backstageTasks and then calling backstage.init.

Currently this will lead to multiple instances of the backstage label and toggle button. Therefore backstage.init should clear the respective containers before (re)populating them.

Change History

Changed 22 months ago by FND

  • status changed from new to closed
  • resolution set to fixed

fixed in changeset:12023

Changed 22 months ago by FND

Note that plugins are evaluated before the backstage is first initialized. However, asynchronous or manual operations (e.g. bookmarklets) might still want to re-initialize the backstage at a later time.

Also, it seems good practice for an initialization method to ensure a blank slate.

Note: See TracTickets for help on using tickets.