Steps to reproduce
I’m serving adverts into Google Doubleclick for Publishers SafeFrames which should fill the window when clicked, using
$sf.ext.expand($sf.ext.geom().exp); - i.e. "signal the SafeFrame script in the host window to expand this iframe as far as possible in every direction".
The base ad-unit renders without issue, but the attempt to expand fails every time.
This was working in Edge version 40 - but not the latest version (41.16299.15.0). No other browser, desktop or mobile, exhibits a similar issue.
The issue seems to be specific to Google’s SafeFrame implementation.
Steps to reproduce:
Visit http://safeframes.net/examples/creative_test.html using Microsoft Edge 41.16299.15.0.
Select "Push Expansion (300x250)" from the Samples dropdown.
Click the “Expand” button in the yellow box which appears.
Expected behaviour: box expands to 720px x 570px.
Observed behaviour: box expands to 720px x 570px.
Select “sf.ext.expand by push and sf.ext.collapse” from “Some example safeframe creatives:” dropdown. Click the Render Creative button.
Click any arrow button, or "Expand All", in the green box which appears.
Expected behaviour: box expands (dependent on arrow clicked).
Observed behaviour: No change in element size. No log output.
It’s been suggested by a user experiencing a similar issue that this is a result of heightened security: https://productforums.google.com/forum/#!topic/dfp/sRX_HDIwu3k notes the following error message in the Edge console when a Google / Doubleclick SafeFrame advert fails to render:
SEC7131: Security of a sandboxed iframe is potentially compromised by allowing script and same origin access.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “James M.”
Changed Steps to Reproduce
Changed Assigned To to “Scott L.”
Changed Status to “Needs root cause”
Changed Assigned To to “Venkat K.”
Changed Assigned To from “Venkat K.” to “Frank L.”
UPDATE: As of 2018-02-22, GPT SafeFrames expand correctly in Edge 41, as everywhere else. This was tested on a version of Edge which hasn’t been updated since this issue was reported - Google have presumably silently fixed the issue on their end.