API-Killer-Storage
大小:0.06MiB版本:v 1.0.4.1更新时间:2019-07-23
☞︎ Storage Headshot!
API-Killer-Storage 的使用方法详解,最全面的教程
API-Killer-Storage 描述:
用户数:2
分类:生产工具插件
扩展大小:0.06M
最后更新时间:2019-07-23
版本:v 1.0.4.1
API-Killer-Storage 插件简介:
这是来自Chrome商店的 API-Killer-Storage 浏览器插件,您可以在当前页面下载它的最新版本安装文件,并安装在Chrome、Edge等浏览器上。
API-Killer-Storage插件下载方法/流程:
点击下载按钮,关注“扩展迷Extfans”公众号并获取验证码,在网页弹窗中输入验证码,即可下载最新安装文件。
API-Killer-Storage插件安装教程/方法:
(1)将扩展迷上下载的安装包文件(.zip)解压为文件夹,其中类型为“crx”的文件就是接下来需要用到的安装文件
(2) 从设置->更多工具->扩展程序 打开扩展程序页面,或者地址栏输入 Chrome://extensions/ 按下回车打开扩展程序页面
(3) 打开扩展程序页面的“开发者模式”
(4) 将crx文件拖拽到扩展程序页面,
完成安装如有其它安装问题,
请扫描网站底部二维码与客服联系如有疑问请参考:
https://www.extfans.com/installation/This web-extension kills the HTML5' Storage-API,
https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage
https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage
https://developer.mozilla.org/en-US/docs/Web/API/Storage
https://developer.mozilla.org/en-US/docs/Web/API/StorageEvent
https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API
How does it works?
The web-extension first decimates the methods from the <code>Storage</code>-object prototype (<code>getItem</code>, <code>setItem</code>, <code>removeItem</code>,...),
this is done in-order to purge all of the custom objects that were (or will) derived from it,
particularly <code>localStorage</code>-like objects which were initiated without a <strong>set</strong>-method in their <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/defineProperty#Parameters">descriptor</a> (a.k.a "readonly"),
when that's gone, there are various storage-related objects (<code>sessionStorage</code>, <code>localStorage</code>,...)
and browser-specific ones (<code>webkitStorageInfo</code>, <code>webkitPersistentStorage</code>,..).
Beware,
This <strong>will really mess $h!t-up</strong>,
the <code>Storage</code>-API was "here" long-enough so some web-apps/websites might not bother to fallback to using <code>document.cookie</code> (or even indexedDB),
plus - I havn't really researched what would happen to the core-pages (for example accounts.firefox.com) which tend to send-messages to the core of the browser, for example for sync. of the profile.
it will surely break something...
I'm ~~~pretty~~~ sure that the browser-shell (used to be called "CִHְROַME") and extensions are isolated,
This web-extension will work better on Google-Chrome that Firefox.
Why?
Chrome will allow extension-JavaScript to run on a page that has its JavaScript disabled
(by either browser-setting or a very strict strict <code>Content-Cecurity-Policy</code> header),
Firefox will not allow JavaScript-from extensions to run if for some reason the JavaScript is disabled for the page.
This means that this web-extension won't work on websites such as https://addons.mozilla.org/ .
<strong>Just so you'll be aware.</strong>