Bugzilla

Create `featureCallout.js` and export a render function that takes a message configuration with a `parent_selector` attribute for each screen and `position` set to `callout`. 

The message configuration should follow the multistage spotlight schema. When called by the JS of the parent page, the render function should create a callout element the includes the `aboutwelcome.js` bundle and related links. Then, it should append it to the body of the parent document, and position the element based on the position of its parent element (as defined by the `parent_selector` for the current screen).

`featureCallout.js` should define the AW window functions as seen in `render_multistage` in  `spotlight.js`. This includes capturing or defining an event when the screens change in `aboutwelcome` so that the callout can be re-positioned.

Updates should be made for the `callout` positioned screens in `aboutwelcome.scss` to match new designs.

Create `featureCallout.js` with a render function that takes a message configuration with a `parent_selector` attribute for each screen and `position` set to `callout`. 

The message configuration should follow the multistage spotlight schema. A script tag with `featureCallout.js` can be included in the html of the parent page. On load, it should call the render function and create a callout element the includes the `aboutwelcome.js` bundle and related links. Then, it should append it to the body of the parent document, and position the element based on the position of its parent element (as defined by the `parent_selector` for the current screen).

`featureCallout.js` should define the AW window functions as seen in `render_multistage` in  `spotlight.js`. This includes capturing or defining an event when the screens change in `aboutwelcome` so that the callout can be re-positioned.

Updates to `AboutWelcomeChild.jsm`'s `getAWContent` function can be made to return the appropriate message for the callout based on the page url (in this case, "about:firefoxview").

Updates should be made for the `callout` positioned screens in `aboutwelcome.scss` to match new designs.

Create `featureCallout.js` with a render function that takes a message configuration with a `parent_selector` attribute for each screen and `position` set to `callout`. 

The message configuration should follow the multistage spotlight schema. A script tag with `featureCallout.js` can be included in the html of the parent page, or the render function can be imported and called by the parent page's JS. The render function should create a callout element and append it to the body of the parent document. The `aboutwelcome.js` bundle and related links can be dynamically added to the parent document's head. `featureCallout.js` can position the element based on the position of its parent element (as defined by the `parent_selector` for the current screen).

`featureCallout.js` should define the AW window functions as seen in `render_multistage` in  `spotlight.js`. This includes capturing or defining an event when the screens change in `aboutwelcome` so that the callout can be re-positioned.

Updates to `AboutWelcomeChild.jsm`'s `getAWContent` function can be made to return the appropriate message for the callout based on the page url (in this case, "about:firefoxview").

Updates should be made for the `callout` positioned screens in `aboutwelcome.scss` to match new designs.

Create `featureCallout.js` with a render function that takes a message configuration with a `parent_selector` attribute for each screen and `position` set to `callout`. 

The message configuration should follow the multistage spotlight schema. A script tag with `featureCallout.js` can be included in the html of the parent page, or the render function can be imported and called by the parent page's JS. The render function should create a callout element and append it to the body of the parent document. The `aboutwelcome.js` bundle and related links can be dynamically added to the parent document's head. `featureCallout.js` can position the element based on the position of its parent element (as defined by the `parent_selector` for the current screen).

`featureCallout.js` should define the AW window functions as seen in `render_multistage` in  `spotlight.js`. This includes capturing or defining an event when the screens change in `aboutwelcome` so that the callout can be re-positioned.

Updates should be made for the `callout` positioned screens in `aboutwelcome.scss` to match new designs.

Create `featureCallout.js` with a render function that takes a message configuration with a `parent_selector` attribute for each screen and `position` set to `callout`. Eventually, this component may fetch messages for itself, but for this iteration it can accept the message as an argument.

The message configuration should follow the multistage spotlight schema. A script tag with `featureCallout.js` can be included in the html of the parent page, or the render function can be imported and called by the parent page's JS. The render function should create a callout element and append it to the body of the parent document. The `aboutwelcome.js` bundle and related links can be dynamically added to the parent document's head. `featureCallout.js` can position the element based on the position of its parent element (as defined by the `parent_selector` for the current screen).

`featureCallout.js` should define the AW window functions as seen in `render_multistage` in  `spotlight.js`. This includes capturing or defining an event when the screens change in `aboutwelcome` so that the callout can be re-positioned.

Updates should be made for the `callout` positioned screens in `aboutwelcome.scss` to match new designs.