For the refactoring, one approach is from about:welcome trailhead react component, we add a hook on first mount to dispatch an action to the main process, e.g., FXA_ENDPOINT_REQUEST, so we only load the FxA module and call API (can be async) for about:welcome and not about:home/newtab.
Bug 1556276 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For the refactoring, one approach is from about:welcome trailhead react component, we add a hook on first mount to dispatch an action to the main process, e.g., FXA_ENDPOINT_REQUEST, so we only load the FxA module and call API (can be async) for about:welcome and not about:home/newtab. This is in contrast to the current approach to read a pref once at startup (thus very slightly impacting first run but also not responding to url changes).
For the refactoring, one approach is from about:welcome trailhead react component, we add a hook on first mount to dispatch an action to the main process, e.g., FXA_ENDPOINT_REQUEST, so we only load the FxA module and call API (can be async) for about:welcome and not about:home/newtab. This is in contrast to the current approach to read a pref once at startup (thus very slightly impacting all startup even those without about:welcome, but also not responding to url changes).
For the refactoring, one approach is from about:welcome trailhead react component, we add a hook on first mount to dispatch an action to the main process, e.g., FXA_ENDPOINT_REQUEST, so we only load the FxA module and call API (can be async) for about:welcome and not about:home/newtab. This is in contrast to the current approach to read a special activity-stream pref once at startup (thus very slightly impacting all startup even those without about:welcome, but also not responding to url changes).
For the refactoring, one approach is from about:welcome trailhead react component, we add a hook on first mount to dispatch an action to the main process, e.g., FXA_ENDPOINT_REQUEST, so we only load the FxA module and call API (can be async) for about:welcome and not about:home/newtab. This is in contrast to the current approach to read a special activity-stream pref once at startup (thus very slightly impacting all startup even those without about:welcome, but also not responding to url changes nor handling trailing slashes consistently bug 1554102).