GitHub - GoogleChrome/web-vitals-extension: A Chrome extension to measure essential metrics for a healthy siteYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Manifest - Web Accessible Resources | Chrome Extensions | Chrome for Developers
Web-accessible resources are files inside an extension that can be accessed by web pages or other extensions. Extensions typically use this feature to expose images or other assets that need to be loaded in web pages, but any asset included in an extension's bundle can be made web accessible. By default no resources are web accessible, as this allows a malicious website to fingerprint extensions t
chrome.declarativeNetRequest | API | Chrome for Developers
Manifest In addition to the permissions described previously, certain types of rulesets, static rulesets specifically, require declaring the "declarative_net_request" manifest key, which should be a dictionary with a single key called "rule_resources". This key is an array containing dictionaries of type Ruleset, as shown in the following. (Note that the name 'Ruleset' does not appear in the manif
How to Continuously Deploy a Chrome Extension
Note from the publisher: You have managed to find some of our old content and it may be outdated and/or incorrect. Try searching in our docs or on the blog for current information. Google Chrome is the most-used browser on the Internet. And people are creating Chrome Extensions for all kinds of use-cases. Within 24 hours of Twitter announcing their 280 character tweets test, a new Chrome Extension
Chrome拡張の開発でwebpackを使わずにES6のimportを有効にしたい - DRYな備忘録
追記 2018/10/29 chromeモジュールが使えなくなる、という指摘は半分正しくて半分間違ってる（いくらでもやりようがある）のでもうちょっとちゃんとした記事を書きました。 medium.com 以下原文ママ。 背景 JSのプロジェクトで、特に僕はChrome拡張を作ることが多いんですが、ES6 syntaxを使いたい だいたいのES6 syntaxは、Chrome（現在 65.0.x）で使える ただし、問題は import です Background Script でimportを使う medium.com つまりHTML5準拠のブラウザでは<script type="module" src="..."></script>とすれば、これをエントリポイントとして以下importは解決されるんだけど、ということは逆にmanifest.jsonのbackground.scriptsでBa
12 Extensions and Apps that Fill the Gaps in Chrome DevTools - Telerik Blogs
Do a search online for "must have chrome extensions/applications" or "top XX chrome extensions/applications" for front-end developers and you will most certainly find several cliche articles containing a random curated list of extensions/applications. It is pretty much what you might expect to find. I am not going to write one of those articles. What follows, I hope, is more useful and insightful
Chrome Logger - Server side application debugging
About Chrome Logger is a Google Chrome extension for debugging server side applications in the Chrome console. Most languages include their own logging capabilities, but sometimes it is easier to see your logs right in the browser. Chrome Logger used to be known as ChromePHP. If you are feeling generous, you can donate to help support development. Usage Using Chrome Logger is simple: Install the C
Klepto proxy by kyo-ago
Kleptoとは？ JavaScript, CSSの開発者向けのLocal Proxyです。 何ができるの？ 現在以下の機能が実装されています。 通信内容の閲覧（network list） 通信内容の差し替え（auto responder） Chrome developer tools上で書き換えた内容のローカルファイルへの反映（auto save） ローカルファイルが更新された場合にブラウザをリロード（auto reload） （注 現在Windows環境では「通信内容の閲覧」と「通信内容の差し替え」が正しく行えません） 動作環境 MacOSX版Chrome version 25以上（2013/03/01の安定版最新） 現在Windows環境では「network list」と「auto responder」が動作しません（1ページ通信するとそれ以上通信できなくなる） 「auto save
Chrome Devpanel Extension Communicating with Background Page
I have an extension to the chrome devtools panel. I can send messages to the page using chrome.devtools.inspectedWindow.eval ... but how do I receive messages in the dev panel? Specifically, I need my devpanel to hook into events that happen on the page. I can't get it to listen to events on my content script, nor the background page. I've tried chrome.extension.sendMessage in the content script,
chrome.webRequest | API | Chrome for Developers
You must declare the "webRequest" permission in the extension manifest to use the web request API, along with the necessary host permissions. To intercept a sub-resource request, the extension must have access to both the requested URL and its initiator. For example: { "name": "My extension", ... "permissions": [ "webRequest" ], "host_permissions": [ "*://*.google.com/*" ], ... } webRequestBlockin
僕が考えたChrome拡張機能を作るときのデザインパターン
最近いくつかのChrome拡張機能を作っていて、すでに数千人のユーザを獲得できているものが出てきてたりします。 Image collector extension goo.gl URL Shortener extension mixi Check button extension Semantic inspector これだけ作ってると、何となく自分でのChrome拡張機能を作り出す際のデザインパターン・・・っていう大それたものじゃないけど、ようはテンプレが確立されてきます。全く褒められない書き方をしているかもしれませんが、ここでそのテンプレ達を晒しておこうかな、と思います。 manifest.json まずはChrome拡張機能の要であるマニフェストファイルです。これは誰が書いてもさほど変わらない記述内容となるでしょう。 { "manifest_version": 2, "name":
はじめてのChrome extension
Toru Yoshikawa highlights 10 awesome features of Chrome DevTools including the ability to pick colors from the screen in Elements, adjust animation speed in Elements, define animation timing in Elements, search by selector in Elements, take timeline screenshots in Timeline, show layers in Layout, enable network throttling in Network, display variable values inline in Sources, store variables as gl
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Evolving Chrome Extensions with Manifest V3 - Simeon Vincent - JSConf US 2019
Intent to Ship: Long Task API - Google Groups
Debug a Google Chrome Developer Tools Panel Extension
GitHub - kinjouj/chrome-extension-study
GitHub - anvaka/jsruntime: Chrome Extension to explore javascript runtime.
GitHub - GoogleChrome/chrome-extensions-samples: Chrome Extensions Samples