Closed Bug 1823779 Opened 2 years ago Closed 2 years ago

Refactor to evaluate screen targeting and update screens state on index change

Categories

(Firefox :: Messaging System, enhancement, P2)

enhancement

Tracking

()

VERIFIED FIXED
114 Branch
Iteration:
114.2 - Apr 24 - May 5
Tracking Status
firefox114 --- verified

People

(Reporter: pdahiya, Assigned: pdahiya)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

https://phabricator.services.mozilla.com/D172593 fix adds dynamic screen targeting by using isDynamic property inside handleAction. This adds an overload of maintaining isDynamic property for actions we want to evaluate targeting dynamically.

Scope of this bug is to refactor code to evaluate screen targeting on unvisited screens (screens coming after the current screen) when index changes and screen loads

useEffect(() => {
    (async () => {
      let screensVisted = screens.slice(0, index);
    setScreens(
      screensVisted.concat(
        await window.AWEvaluateScreenTargeting(screens.slice(index))
      )
    );
    })();
  }, [index]); 

Depends on: 1820566
Assignee: nobody → pdahiya
Iteration: --- → 113.1 - Mar 13 - Mar 24
Priority: -- → P1
Priority: P1 → P2
Iteration: 113.1 - Mar 13 - Mar 24 → 113.2 - Mar 27 - Apr 7
Iteration: 113.2 - Mar 27 - Apr 7 → 114.1 - Apr 10 - Apr 21
See Also: → 1829448, 1829210, 1820865
Depends on: 1827572
Iteration: 114.1 - Apr 10 - Apr 21 → 114.2 - Apr 24 - May 5
See Also: → 1827573
Pushed by pdahiya@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/aa398d16e528 Evaluate screen targeting and update screen state on index change r=Mardak,omc-reviewers,negin
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
Blocks: 1830213
Blocks: 1829210
See Also: 1829210

I‘ve verified this enhancement using the latest Firefox Nightly 114.0a1 (Build ID: 20230507095340) on Windows 10 x64, macOS 11.7.1, and Ubuntu 22.04 x64.

  • After following the testing steps from this Test Plan, I confirm that the “about:welcome” screens (both with language mismatch and without) show up in the correct order and have their impression pings are correctly registered in the Browser Console.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: