tree 65b52066292ada9b1d9e828620f28d5b1267fc21
parent 9bfab77835b8582a56abe0a4d241de82707042cb
author Jonah Williams <jonahwilliams@google.com> 1600912685 -0700
committer GitHub <noreply@github.com> 1600912685 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfa/0uCRBK7hj4Ov3rIwAAdHIIABzfySRWf9OTazUcvS8YQSND
 XDfiyq0nEj8RQb3ju0ULs68sV3FSBtevLv+OLS8Kt63x/dMDWKi1c58g61N/fWl2
 FKeLDtqyWkDGwqiuf/8JFJi5s9mHeaI5/nhcyPCAHETe2Xlvc3KEkw/UUFDUIKIF
 RLR0diC00BT1kpA1bgsa7TCKZW60JExN8gq6vuzACtYfu08m3FKaRcMSEQb62LEC
 schjYQGLRHt49xdRWQOQK866l62s793hA2p4NClHbWtnRvxZctIuJzneVOVFFkOQ
 0JGbwSt2ZZdn0dMdHF/PtuS/fDzv7GoGZYXnKRdBLM9cYwV62F/FY8Oj6E5x4tQ=
 =yIA4
 -----END PGP SIGNATURE-----
 

[flutter_tools] register service worker after first frame event (#66082)

Registering the service worker immediately after the documented has loaded may cause SW initialization to compete with framework initialization. It was recommended to us that we defer the service worker setup until after the framework is done with setup, which should be sometime after the first frame.

To implement this, I augmented the binding setup to dispatch an event on the document after the binding has initialized. I don't see any obvious risks with this setup.

Fixes #66066