Ticket #486 (closed defect: wontfix)

Opened 11 months ago

Last modified 11 months ago

Multiple companions do not display correctly

Reported by: paul Owned by: paul
Priority: blocker Milestone: OVA for AS3 (v1.0.1)
Component: OVA for AS3 Version: OVA for AS3 (trunk)
Keywords: Cc:
Forum thread:

Description

Please see notes from my developer below regarding a companion fix.


I'm seeing some strange behavior when trying to load an ad tag with
two companions, one a 300x250 and the other a 728x90. My console log
is attached.

The ads have a resourceType of HTML and end up calling JavaScript
which does a document.write(). I'm not sure if the values seen in the
VAST response in the console log conform to VAST standards. I have the
OVA html5 configuration setting to true (does this really have to be
hard-coded in advance, or is there no way to dynamically switch to
html5-based ad-loading based on the VAST response?).

What is odd is that:

  1. If I configure OVA to use one companion or the other, it does so

successfully. So it's not a simple issue of the naming of the divs,
etc.

  1. If I configure OVA to use both companions, it puts the HTML for

both companion ads in the 720x90 div. It doesn't matter if I change
the order in which I specify the companions in the OVA config, it
always ends up putting both ads in the 720x90 div, and the other ends
up empty.

  1. This is really odd, but I discovered that adding an empty

window.alert(""); to the last line of the "jQuery.fn.writeElement"
function definition at the end of ova-jquery.js fixes the problem
somehow. I see two alerts, one as each companion is populated. After
clearing the alerts both companions are shown properly, in their
correct divs. However the 720x90 companion acts as if I had the
companion "restore" config boolean set to true (it isn't removed at
the end of the video ad). The smaller companion disappears following
the ad play, as it should.

All of this behavior occurs in Chrome 19 and Firefox 13.

Raised by Patrick

Change History

comment:1 Changed 11 months ago by paul

  • Status changed from new to closed
  • Resolution set to wontfix

Requires the "millisecondDelayOnInjection": 1000 option to be used.

Note: See TracTickets for help on using tickets.