- From: Patrick Meenan <notifications@github.com>
- Date: Mon, 14 Feb 2022 21:46:56 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/704/1039882992@github.com>
Assuming the ad content is triggered by script, main content high will come before ad content high in the vast majority of cases because of discovery order. The page also controls the timing/priority of the initial ad script which is the main lever for controlling ad code execution. Browsers also have control over same-origin vs cross-origin that they can layer on top of the importance signals if necessary and already consider frame vs main document when scheduling fetches. I think there's a fair amount of control already in place where non-hostile ad scripts will still prioritize appropriately and a good case for why the hints aren't hard-wired to explicit priorities. An extreme case where an ad script agressively rewrites other page content would be a problem but that's the case generally and not specific to priority hints. On Mon, Feb 14, 2022 at 10:50 PM cynthia ***@***.***> wrote: > It may actually be beneficial even within an ad context to prioritize > images and scripts relative to each other. > > This would make sense, but at the same time it feels like it should be > tiered (main content high > ad content high) and controllable by the top > level document. I'd imagine ad banners would ask for high priority once > they know this feature exists. (And the last thing the user would want is > ad banners to be served before actual content...) > > — > Reply to this email directly, view it on GitHub > <https://github.com/w3ctag/design-reviews/issues/704#issuecomment-1039825142>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AADMOBNPOXXXIOFJJSLJN43U3HEO5ANCNFSM5K2XIMAQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/704#issuecomment-1039882992 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/704/1039882992@github.com>
Received on Tuesday, 15 February 2022 05:47:08 UTC