html文件不放在resources下,html – 什么是“resource：//”URL方案？

资源：URI方案是Firefox独有的,并在Firefox v3中注册.

它在内部使用,与chrome.manifest相关.

在Firefox中,在地址栏中输入此内容并导航到它.

resource:///

您应该找到本地Firefox用户配置文件的目录结构.

背景

Mozilla注册了多个URI方案.其中包括资源：和铬:(后者,更常见)

Chrome目录是任何Firefox安装的重要组成部分. Chrome目录中包含数据文件,文档,脚本,图像等.所有这些文件都包含用户界面元素和本地用户数据.

但是chrome：// URI实际上只是鲜为人知的资源的一个特例：// URI指向平台安装区域的顶部. chrome目录中的所有路径必须以resource：或jar开头：

具体用例.. Emberjs

问题

We allowed accessibility for resource:/// which pointed at the

installed on-disk resources that came with Firefox. I don’t know if we

supported alternate resource aliases at the time, but I’m sure add-ons

weren’t using them and that we didn’t support resource aliasing in

chrome.manifest (which didn’t exist).

When we introduced resource into chrome.manifest we should have added

the option contentaccessible=yes mechanism at the same time: let

add-ons opt-in to fingerprintability just as we do with chrome

content. Unfortunately anything we do may have compatibility problems:

searching addon source I find 810 chrome.manifest files that define

custom resource:// locations. One reason for so many is because it’s

used by JetPack addons so I’m somewhat hopeful that most of those

don’t need to reference these from content.

Quoted from Reference 2 below.

The only reason extensions would need to use resource: is to make things available to web content.

Quoted from Reference 2 below.

直接来自Mozilla

在Mozilla,IANA或W3C的任何文档中,我都很难找到资源：//.这是唯一的,只能直接提到资源的定义：我可以找到直接从Mozilla发布的.它是如此模糊,我拍了一个截图:)

进一步阅读：