Hi Nick,
You're right that this group is officially about ORMMA, but since MRAID follows much of the standards started here, there is discussion about both.
One of the differences between the two specifications is that MRAID ads must identify themselves to be MRAID. (ORMMA ads can always assume they are in an ORMMA container and do not need to identify themselves.) The identification method decided on by the IAB working group is to use a script tag with a relative path to mraid.js.
The idea is that if the ad is served to a non-mraid container, then the mraid.js file request would fail silently and not impact that ad display.
If the ad is served into an mraid container, then the container (usually an SDK) is responsible for injecting the mraid JavaScript libraries and returning a valid response to the mraid.js request.
If you are creating an ad, then you don't need the mraid.js file. You can safely ignore the file request error since that won't happen in an MRAID SDK.
If you are developing an MRAID SDK, then you may want to look at the ORMMA source code as a starting point. The ORMMA source separates an interface file "ormma.js" from an implementation file "ormma-bridge.js".
Thanks,
-Nathan
On Wed, Jun 27, 2012 at 5:07 AM, Nick
<flag...@gmail.com> wrote:
hi,
I have been googling about mraid and found very little information about it,
and in this group i have read some post, and found my self abit confused. now i want to ask a few question.
In MRAID i have to add a line <script src=mraid.js> to be Mraid compliant, where did i get the mraid.js because when i tried on my localhost its state that mraid.js not found.
thanks in advance for the response