On 5/8/25 9:56 AM, Xiaochen Zhou wrote:
The functionality of canLoadOpaqueURL() was replaced with
navigator.canLoadAdAuctionFencedFrame()
<https://wicg.github.io/turtledove/#canloadadauctionfencedframe> in
2023. Calling the canLoadOpaqueURL() API has resulted in a deprecation
console warning
<https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/fenced_frame/html_fenced_frame_element.cc?q=%22HTMLFencedFrameElement.canLoadOpaqueURL()%20is%20deprecated%22&ss=chromium%2Fchromium%2Fsrc>
ever since pointing developers to the new API.
The behavior of canLoadOpaqueURL() is not spec’d so this does not
involve spec changes (only the explainer needs an update). The
chromestatus metrics
<https://chromestatus.com/metrics/feature/timeline/popularity/5072>
shows there has been no usage of it for the last 6 months.
How did we end up shipping an API that is not specified?
The removal of canLoadOpaqueURL() will start from M138. We would be
happy to send out a formal Intent to Remove if anyone deems it worthwhile.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/203e9d51-b81f-42f6-8363-994111ba00f2n%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/203e9d51-b81f-42f6-8363-994111ba00f2n%40chromium.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/92f35e73-b4d3-428f-a090-86b6703d8990%40chromium.org.
