gecko-dev/docshell
Tom Ritter c816dcfce3 Bug 1882422: Use a local testing page to return complex data and make use of it in C++-land r=peterv
- Create a local page we will access via an about: URL
- In that page, demonstrate how to do some stuff, then fire a custom event
  indicating its stuff is done _and_ return complex data in that event.
  console.log() didn't seem to be visible in the HiddenWindow, so I also
  piped out debug strings for development purposes, so they can be
  console.logged in the Service, where we can see them.
- Instead of listening for DOMContentLoaded/pageshow, instead listen for
  the new CustomEvent.
- In UserCharacteristicsPageService, receive the data from the page and
  populate the appropriate Glean metrics
- Refactor the calling of nsUserCharacteristics::PopulateData() and
  SubmitPing().  Now we call PopulateDataAndEventuallySubmit() which will
  eventually call SubmitPing after our promise is resolved.
- To make it a little cleaner (so ContentPageStuff() isn't calling
  SubmitPing()) we return the promise out of ContentPageStuff() that
  PopulateDataAndEventuallySubmit() will await and then call SubmitPing()
  when that promise resolves

Differential Revision: https://phabricator.services.mozilla.com/D203055
2024-04-03 23:43:17 +00:00
..
base Bug 1882422: Use a local testing page to return complex data and make use of it in C++-land r=peterv 2024-04-03 23:43:17 +00:00
build Bug 1882422: Use a local testing page to return complex data and make use of it in C++-land r=peterv 2024-04-03 23:43:17 +00:00
shistory Bug 1883279 - Check browser.navigation.requireUserInteraction before skipping entries based on user interaction. r=farre 2024-03-13 10:56:33 +00:00
test Bug 1689705 - Remove marquee events. r=smaug 2024-04-03 17:40:44 +00:00
moz.build Bug 1859890 - batch 14 convert xpcshell.ini -> .toml. r=aryx,dom-storage-reviewers,jesup 2023-11-28 01:02:01 +00:00