Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Core: support for expandable / flex slots #12379

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

dgirardi
Copy link
Collaborator

Type of change

  • Feature

Description of change

This adds better support for banner slots with flexible sizes:

  • publishers can now specify an ortb format array instead of sizes for an ad unit's mediaTypes.banner; expdir can also be supplied there for convenience (alias of ortb2Imp.banner.expdir);
  • bid adapters can reply with wratio/hratio instead of width and height;
  • because many adapters expect specific sizes, format elements that only specify wratio/hratio are translated to "placeholder" sizes (e.g. {wratio: 2, hratio: 1} becomes [2, 1]);
  • creatives now attempt to expand to all the available width/height when rendering a bid that has no definite size.

Other information

#9361

logWarn(`Ad unit banner.format specifies both w/h and wratio/hratio`, adUnit);
return false;
}
return (w ?? h ?? wratio ?? hratio) != null;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't we check that w AND h aren't null or wratio AND hratio aren't null ? Instead of having just one non null value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants