xkema / missofis-request-interceptor Goto Github PK

Opening http://example.com/my-script.js file directly on a browser tab, prevents intercepting because resource type for that page is "document" not "script".

• observed at Chrome

Unsafe call to aboutDetails.insertAdjacentHTML for argument 1

Warning: Due to both security and performance concerns, this may not be set using dynamic values which have not been adequately sanitized. This can lead to security issues or fairly serious performance degradation.
core/modules/fill-about-page-details.js line 11 column 3

https://github.com/sindresorhus/escape-string-regexp

Ask the user if something wrong if the user reloads it manually from extension page of the brower

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/onInstalled

Hi, so, any thoughts/inputs on why/why not to include the link to this extension in various webstores?

For example, the link for this extension for chrome webstore:

• https://chrome.google.com/webstore/detail/missofis-request-intercep/npjcklbcofihajkojjldmebgfaljackc/

sync storage has a quota limit of 200KB.

The background script is persistent, it is possible to remove popup switch status data redirectionsOn and matchesOn from storage area.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src

bowser.webRequest.onHeadersReceived.addListener((details) => {
    const cspHeader = details.responseHeaders.filter((header) => header.name !== 'content-security-policy');
    logger('###', 'details', 'details.responseHeaders', cspHeader);
    return { responseHeaders: cspHeader };
    }, {
      urls: [
        'http://*/*',
        'https://*/*',
      ],
      types: [],
    }, [
      'blocking',
      'responseHeaders',
    ]);

• Force users to run it on development branch (!)
• Use node scripts for all to simplify package.json scripts fields

"Use Image Placeholders" text is invalid.

https://github.com/xkema/missofis-chrome-interceptor/blob/master/src/js/options.js#L86-L87

https://medium.com/web-developers-path/how-to-run-jest-programmatically-in-node-js-jest-javascript-api-492a8bc250de

const jest = require('jest');

(async () => {
  const aggregatedResults = await jest.runCLI({
    silent: true,
    noStackTrace: true,
    verbose: false,
  }, [`dist/chrome`]);
  console.log('+++', aggregatedResults.results.numFailedTests, aggregatedResults.results.numPassedTests, aggregatedResults.results.numTotalTests);
  console.log('+++', aggregatedResults);
})();

storage.sync has no support for Opera and Safari.

They're not stuck into the viewport. If the page is scrolled by the user notifications won't be visible.

It shows developer homepage on about:addons browser page of fırefox, it must be the repo URL