chrome-extensions | MeterSphere 录制浏览器请求的插件,记录浏览器中的网络请求并导出为 JMeter 或 JSON 格式的文件 | Performance Testing library

 by   metersphere JavaScript Version: v1.2.4 License: GPL-3.0

kandi X-RAY | chrome-extensions Summary

kandi X-RAY | chrome-extensions Summary

chrome-extensions is a JavaScript library typically used in Testing, Performance Testing, Jenkin applications. chrome-extensions has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

MeterSphere 是一站式开源持续测试平台,涵盖测试跟踪、接口测试、性能测试、团队协作等功能,兼容JMeter 等开源标准,有效助力开发和测试团队充分利用云弹性进行高度可扩展的自动化测试,加速高质量软件的交付。 该项目为 MeterSphere 配套的浏览器插件,该插件可将用户在浏览器操作时的 HTTP 请求记录下来并生成 JMX 文件(JMeter 脚本文件),用于在 MeterSphere 中进行接口测试或性能测试。.

            kandi-support Support

              chrome-extensions has a low active ecosystem.
              It has 353 star(s) with 59 fork(s). There are 19 watchers for this library.
              It had no major release in the last 12 months.
              chrome-extensions has no issues reported. On average issues are closed in 10 days. There are 2 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of chrome-extensions is v1.2.4

            kandi-Quality Quality

              chrome-extensions has 0 bugs and 0 code smells.

            kandi-Security Security

              chrome-extensions has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              chrome-extensions code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              chrome-extensions is licensed under the GPL-3.0 License. This license is Strong Copyleft.
              Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

            kandi-Reuse Reuse

              chrome-extensions releases are available to install and integrate.
              chrome-extensions saves you 4572 person hours of effort in developing the same functionality from scratch.
              It has 9664 lines of code, 0 functions and 60 files.
              It has low code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of chrome-extensions
            Get all kandi verified functions for this library.

            chrome-extensions Key Features

            No Key Features are available at this moment for chrome-extensions.

            chrome-extensions Examples and Code Snippets

            No Code Snippets are available at this moment for chrome-extensions.

            Community Discussions


            My chrome extension is not working on Edge
            Asked 2020-May-15 at 06:06

            I have a piece of code which works fine on chrome. I did the following step mentioned here. I'm able to load it properly, but the code doesn't run properly. In the background console only the url gets printed, no other consoles or alerts work. Please any help will be appreciated ! Please



            Answered 2020-May-15 at 06:06

            I tested and found that if we remove window.onload then the extension will work well in Edge Legacy. It will print all the consoles.

            You could set content.script run at document_idle. It's equal to window.onload and you do not need to listen for the window.onload event. For more detailed information, you could refer to this article.

            My manifest.json is like below:



            Chrome extension : sendResponse returning empty object
            Asked 2020-Apr-07 at 09:36

            I know there are a lot of similar questions : Chrome extension messaging: sendResponse returning empty object, etc., but I read and tried all of them before asking my question. My problem is a bit different, so I think that's why their solutions don't work for me.

            I want to detect Ctrl+C from the user, so when he clicks on extension icon, the content of the clipboard is displayed inside the popup.

            Here's what I've done : a part of manifest.json :



            Answered 2020-Apr-07 at 09:36

            The actual cause of the problem is that extension.onMessage is a deprecated alias for runtime.onMessage so you have two listeners for the same event but only the first registered listener's sendResponse is transferred to the caller and that is {}.

            That said, the entire workflow can be extremely simplified: there's no need for the background script or the content script so you can remove "background" and "content_scripts" from manifest.json. No need for messaging either.

            You need a browser_action popup and simply read the clipboard in the popup script.




            Error: User credentials required in Google Cloud Print API
            Asked 2019-Nov-06 at 14:52

            I'm trying to use Google Cloud Print(GCP) API, but I can't make it works. Maybe I've understood bad the workflow because is the first time I'm using the google api, please help me to understand how to make it works.

            Initial considerations:

            • I'm trying to implement it in reactJS, but It is indifferent because the logic to make GCP works is independent of the technology. Then you also can help me understand the workflow.

            What exactly I want:

            To make my first test, I am looking to get all information about my printer.

            What I did:

            1. I created a project in:
            2. Inside the project created, I created a credential:
              • create credentials -> OAuth client ID

            And I chose Application type: Web, and also configure the restrictions to source and redirection to my localhost.

            1. Manually in, I added my printer, I made a test printing a PDF and was OK.

            2. I created a project in reactJS to get the information of my printer I've added.



            • I'm using a component react-google-login to obtain easily the user accessToken:

            • This component only obtains the access token and save it in localStorage, in a variable called googleToken and it draws a button to call a function to obtain the information about the printer.




            Answered 2017-Dec-02 at 22:54

            I've resolved my problem, my main problem about User Credential required were because I was using the incorrect access token and It was because I was getting the access token incorrectly.

            I'm going to explain my whole solution because there are few examples of codes with this API.


            1. The steps described were Ok until the fourth step where I used the external component react-google-login to trying to get the access token, instead I used googleapis module: Link Github googleapis

            2. Also to avoid CORS problem(and not use CORS chrome plugin) I wrote the requests to Google API in server side.(NODEJS)

            3. I had also a problem in the frontend when I tried to generate a popup to give permission for printer(problems about CORS), my solution was to use this very simple module for authentication: Link Github oauth-open

            General scheme:


            Knowing I have all data described in my question post(until the third step).


            • The next step in getting a URL and use it to the user can authenticate. As I said before I used the module oauth-open in the frontend to generate the popup and only this module need the URL. To get the URL in the backend I used the endpoint /googleurl, where here I used the method generateAuthUrl of the module googleapis to generate the URL.

            • After that In the frontend, I got the authentication_code(that returned the module oauth-open), I send It to my endpoint /googletoken and here I process the authentication_code to generate access token, refresh token and expiration date with the method getToken of the module googleapis. Finally, these data are stored in the database.


            • For print, since the frontend, I send what data I need send to the printer. I used my endpoint /print

            • In the backend endpoint, my logic was the next:

            Recover tokens and expiration date from database, with the expiration date check if the token has expired, and if It has already expired then gets another token and replace the old access token with the new one, replacing also with the new expiration date, to obtain this new data only is necessary call to method refreshAccessToken of module googleapis.Note: the refresh token never expires.

            After having the access token updated, use it to send data to the printer with Google route(.../submit)


            • All the next codes are in only 1 file
            • Some data as validation, static variables, error handler, etc, has been removed to better understanding.

            Route get URL authentication.



            Standard way to build a Chrome extension into Chromium
            Asked 2019-May-01 at 18:30

            I have built a Chrome extension that I have been installing into Chrome using Selenium.

            Now I would like to build my own Chromium from source so that my extension is pre-bundled into the built distributed package so that I don't have to worry about needing Selenium to install the CRX file for my use case.

            I have found several forums where people suggested they were going to try this, but none of them ended up seeming like they were successful.

            I found some tips on how a system administrator can force install extensions into chromium for users in their network: But that is for chrome enterprise, probably not going to be useful for me.

            Here is another post which talks about how to offline install chrome extensions. I might be able to use some of this to make what I want happen.

            Has anyone had success actually building into chromium a CRX so that the CRX is just installed automatically?

            Quick update:

            I just want to note: I'm installing my custom version of chrome with an InnoSetup installer. So I do have the chance to, after my chromium fork is installed, do some custom execution steps post install. And my extensions are hosted on the chrome web store and approved.

            So if there is some way to programmatically install chrome extensions into a Chromium installation from the web store, I would could easily use that.



            Answered 2018-Jun-18 at 09:07

            This has been tested in our Chromium fork version 66.0.3359.139 on Windows 10. The extension bundling process might be different for Linux and OS X. I have also tried to make it as easy as possible to accomplish this task. There are a couple of things you will have to do to accomplish this:

            1. Add your Chromium extension (.crx) file to a list of default extensions to bundle with mini installer
            2. Find out the ID of that extension
            3. Automate plugin installation process
            4. By pass Chrome Web Store check
            5. Build mini installer to install your Chromium fork

            1: To bundle your extension with the installer, you will have to modify: src\chrome\browser\extensions\default_extensions\ file. Suppose tab_capture.crx is your extension then it's contents should look something like this:



            How to Inject jQuery with Chrome in Developer Console?
            Asked 2019-Apr-27 at 23:48
            THE ISSUE

            I used to be able to (locally) use either of the following two Chrome extensions to easily inject jQuery into pages that didn't already have jQuery, and that I didn't own (client-side) to experiment with design changes, development modifications, and real-time troubleshooting:

            Unfortunately, now because of what appears to be the newest craze in preventing "XSS" (cross-site scripting), those plugins no longer work. There may be a noble purpose behind these changes, and I'm just trying to understand WHAT changed. I think it has something to do with "content security policy", which I've only recently heard of and have very little knowledge of.

            I first learned about XSS as a browser issue in 2011, however, XSS prevention measures had never prevented me from doing local development before. I've been searching for a modern (late 2017) solution, to no avail.

            I'm not sure where to go from here.


            Here are plugins I tried (which used to work until about 6 months ago) that no longer work for me:

            1. jQuery in Console (Plugin)
            2. jQuery Inject (Plugin)
            3. jQuery Injector (Plugin)
            4. GitHub - bluerabbit/jquery-inject: jQuery-inject(Chrome extension)

            Here are some of the many links I encountered that offer solutions which no longer work:

            This last one also looks promising, but I haven't tried it yet:

            MY QUESTIONS
            1. How can I inject jQuery (using Chrome Developer Console) into a webpage that doesn't use jQuery?

            2. Did something change in the browser/JavaScript/programming world significantly enough in 2017 that if a person knew about this particular change or phenomena it would easily explain why the above plugins no longer work?

            3. Why don't the above plugins work? Did ALL the browser companies universally roll out some major change this year?



            Answered 2017-Dec-27 at 21:39

            You can make a very basic chrome extension which just injects JQuery on every page. Getting started with chrome extensions. You can specify that in the manifest itself using this piece of code.



            Edge extension: Validation failed for extension manifest
            Asked 2019-Apr-01 at 07:00

            After the review of my Edge extension I got the approval to submit it into the store. However the submission failed with this error.

            File specified by '' does not exist: Extension\PopupApplication\app\index.html?background=1

            Validation failed for extension manifest: Extension\manifest.json

            The relevant part in the manifest.json looks like:



            Answered 2019-Apr-01 at 07:00

            The fix was to change our code to successful submit the edge extension. The submission does not allow query parameters in the property. This was confirmed by the Microsoft support.



            Centralized configuration of settings for a Google Chrome Extension?
            Asked 2018-Nov-14 at 15:40

            We'd like to develop a Google Chrome extension that is managed centrally, e.g. by MS Active Directory Group Policies.

            How do we centrally distribute domain/customer specific configuration for such an extension?

            Our users are mostly Windows users in the same domain, but we can not assume that they're logged in to any particular G-Suite organisation.

            It does seem possible to create Active Directory Group Policies to install a particular extension for all users. That same article does however say:

            Unfortunately I was not able to come up with a solution concerning the centralized management of Chrome extension settings. Some extensions, for example The Great Suspender, come with additional options for the user to configure. As said, I was not able to find a way how to manage or configure these centrally.

            So now that the extension is installed, how do we configure it?

            Since it is our own extension, there is more freedom. I'm thinking with a Group Policy, one could install C:\some\extension-file.json and then run



            Answered 2018-Nov-14 at 15:40

            How do we centrally distribute domain/customer specific configuration for such an extension?

   is the specific answer for that need. Quoting the docs:

            Enterprise policies configured by the administrator for the extension can be read (using storage.managed with a schema).

            With that in mind, you have to do the following:

            1. Provide a schema for the storage via the storage.managed_schema key in the manifest. An example is given in the documentation.

            2. Present values expected by the schema via GPO / registry as described in admin docs.

            You can verify that the policy-mandated values are loaded by observing chrome://policy.

            You can then use as you would any other (though it is read-only), including watching for changes with onChanged.



            How to share a unique tab ID between content and background scripts without an asynchronous delay?
            Asked 2018-Nov-06 at 14:21

            I have built a chrome extension and I'm getting hit by a race condition that I need help with.

            If you see the answer chrome extension: sharing an object between content scripts and background script it tells us that you cannot share a variable between content and background scripts.

            My goal is to generate a unique ID per-browser tab and then share it in between the content.js and the background.js. Then I need to use this value in a content injected javascript as explained in this answer: In Chrome extensions, can you force some javascript to be injected before everything?

            The only way I have been able to figure out how to do this is by doing the following async code then I just use the tab ID as the unique ID:




            Answered 2018-Nov-06 at 14:21

            This question was already answered previously, although it is hard to tell that this is the same issue at first glance.


            The answer is pretty descriptive so give it a read.

            Here is the script changes that make it work:



            Add event, through extension, to an element with event handler function in original page
            Asked 2018-Oct-24 at 14:32

            In my Content Script, I have an element (an a tag, to be more specific) and I need to add an event to it. The event handler, however, is defined in the page JS, and I dont know how to attach it to the event of my element in the extension. What I want to achieve is:



            Answered 2018-Oct-24 at 14:32

            According to the MDN reference there is a way for page and content scripts to communicate with each other.

            In Firefox*, DOM objects in content scripts get an extra property wrappedJSObject. This is an "unwrapped" version of the object, which includes any changes made to that object by any page scripts.

            Now, in your code, you're immediately calling the function rather than passing the listener a reference. To solve this you should wrap your function call in an arrow function to prevent this:



            Protection of private key for signing Chrome WebExtension
            Asked 2018-Sep-17 at 15:05

            I am the developer of a WebExtension for Chrome. The WebExtension is not listed in the Chrome Web Store because it is only used for internal purposes.

            When packaging the first version of the WebExtension I got a pem file which contains a private key. Currently, I am using chrome.exe to create/sign new releases of my WebExtension using my private key.

            I have noticed that the file is not protected by a passphrase and contains the private key in plaintext. I think it is handled that way to simplify the packaging process for developers. However, I am concerned about the security of my private key. Therefore, I want to protect my private key with a passphrase.

            I guess that chrome.exe will expect a pem file containing a plaintext private key so I have searched for alternatives to sign my WebExtension and found the following:

            Both of them using openssl. Hence, handling of an encrypted private key can be added but I am not very experienced using openssl.

            Do common/best practice openssl commands exists for encrypting and decrypting a pem file?

            Any help will be appreciated, thanks!



            Answered 2018-Sep-17 at 15:05

            Encrypt a key with a passphrase:


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install chrome-extensions

            You can download it from GitHub.


            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone metersphere/chrome-extensions

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link