You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a bug in the debugging module where a bidder which is "completely" mocked out (where no actual network request for it is generated) will never be considered "timely" and, if the auction times out, will always appear in the list of timed out bidders / its onTimeout handler will be invoked. It should be fixed with #12177.
However, this should not affect "real" bids. Let me know if this was a red herring hiding some other timeout issue.
Type of issue
Bug
Description
We are recording
onTimeout()
event getting called for all bidders, if any of the bidder's bid in current auction times out.Test page
https://jsfiddle.net/umerrqq/t61e2zkm/4/
Steps to reproduce
In Chrome Developer Tools enable Network Throttling to Slow 3g for timing out bidders
We are using bidders who have implemented
onBidWon
andonTimeout
events in their respective Bid AdapterCase 1:
Media.net Bidder Won (mocked Bid) - onTimeout and onBidWon event is fired for the same bidder
Case 2:
Ad Query Bidder Won(mocked Bid) - onTimeout and onBidWon event is fired for the same bidder
Prebid Events
Bid Timeout Event - The below image shows adquery bidder’s snm appears is TIMEOUT
Auction End Event - in
auctionEnd
event, underbidsReceived
array, the bidder's snm is RENDERED.Expected results
onBidWon
should've fired and NOT theonTimeout
eventActual results
Both
onBidWon
andonTimeout
events got fired.Platform details
Prebid 9.11.0
Other Information
The text was updated successfully, but these errors were encountered: