On 5/9/25 6:21 PM, Shivani Sharma wrote:
On Fri, May 9, 2025 at 4:25 PM Mike Taylor <miketa...@chromium.org> wrote:
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?
Looking back into the code history: the replaced method
navigator.canLoadAdAuctionFencedFrame()
<https://wicg.github.io/turtledove/#canloadadauctionfencedframe> was
introduced via this CL
<https://chromium-review.googlesource.com/c/chromium/src/+/4324522> in
Mar 2023, which also deprecated canLoadOpaqueURL(). The new method was
launched via the overall fenced frames I2S
<https://groups.google.com/a/chromium.org/g/blink-dev/c/tpw8wW0VenQ/m/mePLTiHlDQAJ?e=48417069> in
June 2023. It looks like canLoadOpaqueURL wasn't spec'd as it was
deprecated even before launch, but was never removed from the code.
Hope that clarifies and apologies for the confusion.
Thanks for the history - much appreciated. Given that usage is zero,
good luck. :)
(IMHO, we should spec web-exposed methods that we ship, even if they're
internally considered as deprecated.)
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>.
--
Shivani
--
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/227ea412-6800-4a51-8f1f-858bd7632f1b%40chromium.org.
