Menu
What are the differences between chrome.runtime.getURL and chrome.extension.getURL?
The documentation implies that chrome.runtime.getURL works in both apps and extensions, and this 2012 announcement indicates that some APIs (though not getURL) have moved from chrome.extension to chrome.runtime.
What's the point of chrome.extension.getURL then, and why isn't it deprecated in favor of chrome.runtime.getURL?
336
Description. Use the chrome. runtime API to retrieve the background page, return details about the manifest, and listen for and respond to events in the app or extension lifecycle. You can also use this API to convert the relative path of URLs to fully-qualified URLs.
The chrome. extension API has utilities that can be used by any extension page. It includes support for exchanging messages between an extension and its content scripts or between extensions, as described in detail in Message Passing.
A chrome extension is a way of adding functionality to the chrome browser. You can add interface elements, open and close tabs, interact with the address bar, as well as modify the contents of any page the browser is currently on.
The chrome.extension.getURL is now deprecated, you should use chrome.runtime.getURL.
From the chrome.extension.getURL's docs:
Deprecated since Chrome 58. Please use runtime.getURL.
196
There isn't any, really.
There are some similar functions there with differences, like .getBackgroundPage, but in this case there's no effective difference.
And as you said yourself, it's not deprecated either. Why? Maybe just overlooked. extension API is older than runtime.
45
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
