I have a bookmarklet and i want to develop chrome/firefox/safari extensions, extensions that should communicate with the bookmarklet;
Is this possible, and if so, does anyone have any docs?
Related
I'm trying to develop a server-side tracker for a video game that runs against an API to update the player's performance, but I only want to track the player's activity when he is playing the game. Since there's no way to know that just from the API, nor any other service, I'm looking at other ways to tell the tracker to update when the user is running the game's process.
I'm trying to rule out desktop applications and a Chrome extension seems like a good compromise. However, I'm aware of the security implications that this has and I know Chrome has some concerns on browser-OS communications. Is there a way to safely achieve this in the scope of a Chrome extension?
Thanks.
Chrome extensions API does not provide any methods to get the process info other than that of the browser process. You can try using the native client as a part of the chrome extension.
I would like to define different actions for different pages
I would like to do like this, when I entry :
wwww.test.com/page1.html : alert Hello!
wwww.test.com/page2.html : alert Good morning!
wwww.test.com/page3.html : alert Hi!
How do I implement this idea
Any tutorial links? thinks so much!
There are three general types of Firefox add-ons: Overlay, Restartles (Bootstraped), and using the Add-on SDK (Software Development Kit). There is a good article comparing the three types on MDN (Mozilla Developer Network).
In general, the most flexible are Overlay extensions. Bootstrapped (Restartless) extensions sacrifice some of the capabilities available to overlay extensions for the ability to install and uninstall without requiring the user to restart Firefox. Add-on SDK extensions sacrifice a considerable amount of the capabilities available to the other two types of extensions for having an abstraction layer between the extension writer and the guts of Firefox. The Add-on SDK is intended to make writing extensions easier and reduce the amount of work needed by the person writing the extension to maintain compatibility with future versions of Firefox. It mostly succeeds at this, but it does fail in some ways.
There are tutorials available on MDN:
Getting Started with Firefox Extensions
XUL School Tutorial
Building an extension
Add-on SDK Tutorials (many)
Many more
MDN is a good resource for information about extensions. When working on Firefox extensions I typically have at least one tab open to a Google search for "MDN " and then whatever I am looking for. It is my go-to method of finding documentation for developing Firefox extensions.
There are a couple of forums which have good information:
Mozilla Add-on Forum (Official)
mozillaZine
Welcome to developing extensions for Firefox.
As to the specific question you asked, the exact code depends on if you are using the Add-on SDK, or not. For the SDK, you should read Working with Events and Listen for Page Load among others. For the other types: Intercepting Page Loads, Listening to events in Firefox extensions, and On page load (Code snippet); also among others.
How can I monitor browsers and capture URLs when they want to download files without using extensions and plugins? For example Internet Download Manager (the version I have) captures URLs from Chrome and Firefox without using extensions, or Free Download Manager does the same thing with Chrome (no extension is installed) but for Firefox it uses an extension and they also provide this service for almost all browsers out there.
Can this be done without extensions and plugins?
Can this be done for other operating systems like OSX and Linux ?
Thank you so much
One option would be to simply intercept all traffic by browsers, and offer the option to download when uncommon filetypes (those that browsers would typically download rather than open) are navigated to. There is probably a more elegant solution, but I might have it act as an odd sort of firewall--one that blocks certain types and instead downloads them on its own.
I found the answer. IDM Uses Layered Service Provider (LSP), which Windows provides it.
Is it possible to prevent certain Keypresses (as mentioned int he title) from reaching the browser? Basically I want to strip down user's ability to close a browser window. Is it possible through NPAPI plugin, particularly in google-chrome web browser. The plugin will be developed using firebreath.
If your actual question is if the browsers give plugins a way to do this, the answer is absolutely not.
That said, there may be system APIs that you can use to do that, but you'd definitely be more likely to get help if you ask a question about how to do that using system APIs. The challenge will be finding a way to only do it when you're in the browser or on a specific tab, etc; there is no way through the browser to do this. If there is a way it'll be hackish and involve system calls, not plugin calls.
Also remember that plugins don't automatically instantiate; it would only work on a page with your object tag. http://npapi.com/extensions for more info
Can the details about installed plugins or extensions found by inspecting UserAgent string? I tried installing many plugins but I could not seen any of its reflection in the user agent string.
The UserAgent string won't contain any information about the plugins or extensions installed on the client's browser. It is simply a depiction of the version of the browser the user has. If you are looking for the capabilities of the browser, try looking into Modernizr and checking out what capabilities it can test for.
I found this site.
It has many user agents. I went through many Useragents and finally I could see that in older browser versions of IE and Opera the name of the plugins/extensions were present.
In Chrome and Firefox I could not find any such imprints.
Some of the extensions in Chrome or Firefox are JavaScript based. If an extension is interacting with the page, it will most likely be using JavaScript. So depending on what extensions you're trying to detect, you might be able to detect them with JavaScript on the page. A lot of them, though, will have code encased in a separate context, so that may be difficult.
Here's a link from Google's plugin guide about content scripts.