This is a really clever use of CAPortalLayer. Feels like you're essentially bypassing the “one WKWebView per hierarchy” constraint by turning the problem into a rendering problem instead of a state problem.
Curious how you handle input events across mirrored views — does only the “real” view receive interaction and others proxy it, or is there some trick there too?
