demo · v135

Fenced-frame auto-beacons, cross-origin

Chrome 135 lets a fenced frame's automatic reporting beacon ride along cross-origin data after a top-nav, without manual plumbing. The simulator below builds the request you'd otherwise have to handcraft and shows where the destination data ends up.

Origin trial / flag Fenced frames need chrome://flags/#enable-fenced-frames and an origin trial token. This page simulates the beacon shape client-side so you can see the schema regardless.
window.fence: ?

before chrome 135 (no cross-origin data)


      

      

        
chrome 135+ (cross-origin data attached)

        

      

    

  


  

    
the code


// inside the fenced frame
window.fence.setReportEventDataForAutomaticBeacons({
  eventType: "reserved.top_navigation_commit",
  eventData: JSON.stringify({ product: "abc-123" }),
  destination: ["seller", "buyer"],
  crossOriginExposed: true,   // NEW in Chrome 135
});

  


  

    
see also