Barry Pollard

> That could work. Mostly i don't want to lose them in slack. Cool. Can I leave you to consolidate them all in one issue and close out the others?

Closing due to lack of feedback

@dainemawer could you give more info on point 1? I just tried opening https://speculative-rules.glitch.me/ in two tabs and both speculated correctly. Background tabs do drop speculations after 3 mins to...

Actually I've just been made away of some circumstances where tabs are duplicated that can prevent prerendering. I've raised this bug to track this: https://issues.chromium.org/issues/356852180 Is this what you were...

> @bmeurer does Firefox match Chrome in this case? (I couldn't find where Firefox puts timeStamp() marks on its performance timeline). If it does match Chrome, we can just land...

Hi @markusBurda this is a known limitation with PerformanceEventTiming when the target element is removed from the DOM as part of the interaction, or for any other reason before the...

Interesting. This looks like a bug in Chrome. I've opened this to track: https://bugs.chromium.org/p/chromium/issues/detail?id=1428899

This issue is when an element is is disconnected from the DOM tree the Performance Observer entry returns `null`. So it's not that we can't look up the element, it's...

When I block https://mweb-cdn.karousell.com/build/0eb384e38adc64a5.min.js on that page I consistently get an element. So I would guess the JavaScript is somehow deleting and re-adding the element to the DOM. I'm not...

Yes because effectively that is a new element and if the metric is reported on the previous element, then it's no longer in existence to reference. See the [Spec discussion](https://github.com/w3c/event-timing/issues/126)....