This CL moves the base::Feature from content_features.h to
a generated feature from runtime_enabled_features.json5.
This means that the base::Feature can be default-enabled
while the web API is co...
No, they didn’t mean to render it all as an image, but that everything comes from the content server you’re getting the content you want from and thus the ads should be indistinguishable from content. I don’t understand how you could misunderstand it to such a degree as to think they meant to render it all as an image.
Because even if you host the ad content on the same server, it’s still possible to distinguish it, such as by URL or element xpath. To assemble the page to avoid this, you’d need to completely render the page.
No, they didn’t mean to render it all as an image, but that everything comes from the content server you’re getting the content you want from and thus the ads should be indistinguishable from content. I don’t understand how you could misunderstand it to such a degree as to think they meant to render it all as an image.
so… PDF then?
/s
Thanks, BTW. It never occurred to me that someone could interpret my comment as “render-as-an-image”.
You explicitly state “render to image”.
Because even if you host the ad content on the same server, it’s still possible to distinguish it, such as by URL or element xpath. To assemble the page to avoid this, you’d need to completely render the page.
Yes, render the page with SSR, but the person I replied to explicitly wrote “render to image”.