Browser resource loading should respect the load path #197
Comments
@zcbenz does this seem possible to you? Can we adjust the browsers load path to match our requires load path? |
The Content API do allow users to custom resource loader, but I don't know whether it is possible to go so far, neither do I know whether CEF has exposed related API. I will have a see on this. |
I researched on this and here is the result: First it's not possible to write But the same effect can be achieved by using custom protocols, we could write |
Great. I say we make it happen via the custom protocol. On Thu, Apr 4, 2013 at 2:57 AM, Cheng Zhao notifications@github.com wrote:
|
Maybe it's better to do this after we move out of CEF? Otherwise we have to do the same work twice. |
Agreed. We should talk about moving off of CEF soon I think. On Thu, Apr 4, 2013 at 9:33 AM, Cheng Zhao notifications@github.com wrote:
|
Hey @zcbenz, now that we're off of CEF, is this doable? |
@benogle Of course! I created an issue in atom-shell on this feature: electron/electron#64. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks! |
Currently, we have a load path that
require
uses to resolve paths to script files, and we also use this load path inrequireStylesheet
. But resource references in the HTML such as images or fonts don't respect this load path... they are just loading relative to the page's static path on disk. I'd like the browser component to respect the same load path that require does, so that we can resolve relative resource paths to a variety of locations. This will allow themes and packages to easily pull resources that they package for themselves.The text was updated successfully, but these errors were encountered: