Bugzilla

The current management of CFRs (and other 'views') is handled in multiple places in the code which makes it difficult to keep track of the various views being displayed to the user and is susceptible to conflicting views - especially when we factor in Nimbus experiments. We should look at refactoring the current CFR implementation to use a single central source of management which could include queing and prioritization. This should also be scalable to include more 'view' types in the future such as Dialogs, Snackbars, Toasts etc. Suggestions so far have included the use of a Store.

This spike should aso include an inventory of all the current CFRs used in the app, including any triggered in experiemtnal settings or with experiements. 

Use the [Spike investigation report doc](https://docs.google.com/document/d/1O6YGS5bN-V15XXMS6nn9rifzjG23wEdfkfloc8JNCZY/edit#heading=h.87elzc2fggd1) to capture the findings of the investigation.

Improtant
* Do NOT change any of the current CFR ordering/triggers
* Take inventory of the current CFRs

The current management of CFRs (and other 'views') is handled in multiple places in the code which makes it difficult to keep track of the various views being displayed to the user and is susceptible to conflicting views - especially when we factor in Nimbus experiments. We should look at refactoring the current CFR implementation to use a single central source of management which could include queing and prioritization. This should also be scalable to include more 'view' types in the future such as Dialogs, Snackbars, Toasts etc. Suggestions so far have included the use of a Store.

This spike should aso include an inventory of all the current CFRs used in the app, including any triggered in experiemtnal settings or with experiements. 

Use the [Spike investigation report doc](https://docs.google.com/document/d/1O6YGS5bN-V15XXMS6nn9rifzjG23wEdfkfloc8JNCZY/edit#heading=h.87elzc2fggd1) to capture the findings of the investigation.

Important
* Do NOT change any of the current CFR ordering/triggers
* Take inventory of the current CFRs

The current management of CFRs (and other 'views') is handled in multiple places in the code which makes it difficult to keep track of the various views being displayed to the user and is susceptible to conflicting views - especially when we factor in Nimbus experiments. We should look at refactoring the current CFR implementation to use a single central source of management which could include queing and prioritization. This should also be scalable to include more 'view' types in the future such as Dialogs, Snackbars, Toasts etc. Suggestions so far have included the use of a Store.

This spike should aso include an inventory of all the current CFRs used in the app, including any triggered in experimental settings or with experiements. 

Use the [Spike investigation report doc](https://docs.google.com/document/d/1O6YGS5bN-V15XXMS6nn9rifzjG23wEdfkfloc8JNCZY/edit#heading=h.87elzc2fggd1) to capture the findings of the investigation.

Important
* Do NOT change any of the current CFR ordering/triggers
* Take inventory of the current CFRs

The current management of CFRs (and other 'views') is handled in multiple places in the code which makes it difficult to keep track of the various views being displayed to the user and is susceptible to conflicting views - especially when we factor in Nimbus experiments. We should look at refactoring the current CFR implementation to use a single central source of management which could include queuing and prioritization. This should also be scalable to include more 'view' types in the future such as Dialogs, Snackbars, Toasts etc. Suggestions so far have included the use of a Store.

This spike should aso include an inventory of all the current CFRs used in the app, including any triggered in experimental settings or with experiements. 

Use the [Spike investigation report doc](https://docs.google.com/document/d/1O6YGS5bN-V15XXMS6nn9rifzjG23wEdfkfloc8JNCZY/edit#heading=h.87elzc2fggd1) to capture the findings of the investigation.

Important
* Do NOT change any of the current CFR ordering/triggers
* Take inventory of the current CFRs

The current management of CFRs (and other 'views') is handled in multiple places in the code which makes it difficult to keep track of the various views being displayed to the user and is susceptible to conflicting views - especially when we factor in Nimbus experiments. We should look at refactoring the current CFR implementation to use a single central source of management which could include queuing and prioritization. This should also be scalable to include more 'view' types in the future such as Dialogs, Snackbars, Toasts etc. Suggestions so far have included the use of a Store.

This spike should aso include an inventory of all the current CFRs used in the app, including any triggered in experimental settings or with experiments. 

Use the [Spike investigation report doc](https://docs.google.com/document/d/1O6YGS5bN-V15XXMS6nn9rifzjG23wEdfkfloc8JNCZY/edit#heading=h.87elzc2fggd1) to capture the findings of the investigation.

Important
* Do NOT change any of the current CFR ordering/triggers
* Take inventory of the current CFRs

The current management of CFRs (and other 'views') is handled in multiple places in the code which makes it difficult to keep track of the various views being displayed to the user and is susceptible to conflicting views - especially when we factor in Nimbus experiments. We should look at refactoring the current CFR implementation to use a single central source of management which could include queuing and prioritization. This should also be scalable to include more 'view' types in the future such as Dialogs, Snackbars, Toasts etc. Suggestions so far have included the use of a Store.

* This spike should aso include an inventory of all the current CFRs used in the app, including any triggered in experimental settings or with experiments. 
* Identify potential solutions

Use the [Spike investigation report doc](https://docs.google.com/document/d/1O6YGS5bN-V15XXMS6nn9rifzjG23wEdfkfloc8JNCZY/edit#heading=h.87elzc2fggd1) to capture the findings of the investigation.

Important
* Do NOT change any of the current CFR ordering/triggers
* Take inventory of the current CFRs

The current management of CFRs (and other 'views') is handled in multiple places in the code which makes it difficult to keep track of the various views being displayed to the user and is susceptible to conflicting views - especially when we factor in Nimbus experiments. We should look at refactoring the current CFR implementation to use a single central source of management which could include queuing and prioritization. This should also be scalable to include more 'view' types in the future such as Dialogs, Snackbars, Toasts etc. Suggestions so far have included the use of a Store.

This Spike should include:
* inventory of all the current CFRs used in the app, including any triggered in experimental settings or with experiments. 
* identify potential solutions

Use the [Spike investigation report doc](https://docs.google.com/document/d/1O6YGS5bN-V15XXMS6nn9rifzjG23wEdfkfloc8JNCZY/edit#heading=h.87elzc2fggd1) to capture the findings of the investigation.

Important
* Do NOT change any of the current CFR ordering/triggers
* Take inventory of the current CFRs