New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 604379 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

History is being manipulated with IMA HTML5 in INSECURE mode and VPAIDJS

Reported by lore.cin...@gmail.com, Apr 18 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36

Steps to reproduce the problem:
1. Go to http://ryanthompson591.github.io/vpaidExamples/
2. Select "video" sample.
3. When the ad start,  hold the browser back button (there should be the page itself).
4. Click the back button to see the page refreshing.

What is the expected behavior?
The video ad runs without the browser history is  being manipulated.

What went wrong?
The history is being manipulated with the current page as last element.

Did this work before? N/A 

Chrome version: 50.0.2661.75  Channel: stable
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0

Check the discussion in the Google IMA forum https://developers.google.com/interactive-media-ads/docs/sdks/flash/community?place=topic%2Fima-sdk%2FEEfCBG1SYcc%2Fdiscussion
 
Cc: gdambrauskas@google.com
Status: Untriaged (was: Unconfirmed)
Confirmed the behavior, although this doesn't seem like a Chrome bug. More like a problem with the IMA SDK.

gdambrauskas: Can you confirm?
Labels: Needs-Feedback
The problem was that we set the content of the friendly iFrame using the srcdoc attribute, and this evidently pushes an event onto the history stack. I have a change pending that switches IMA to using document.write to change the iframe content instead, which seems not to manipulate history.

If this is the intended behavior for srcdoc then there's no Chrome bug here.
Cc: davidhammer@google.com
Status: ExternalDependency (was: Untriaged)
Status: WontFix (was: ExternalDependency)
No chrome bug here.

Sign in to add a comment