Closed

Need Chrome Browser Extension API to communicate with website

This project received 4 bids from talented freelancers with an average bid price of $633 USD.

Get free quotes for a project like this
Employer working
Skills Required
Project Budget
$250 - $750 USD
Total Bids
4
Project Description

I have developed a Chrome Browser Extension that performs form-based single sign on and logs the user into and out of multiple popular web pages simultaneously. I am developing an [url removed, login to view] website on WIndows Server 2008 R2 with MYSQL Server. The challenge now is connecting the browser extension to my website so that I can invoke it when the user clicks a button on my UI. I would like to do this using an API. All I am requesting is for an experience programmer to write an API, explained further below, and demonstrate the Browser Extension is fully operating and invoking the Single Sign On.

I have obtained some information as to how this should be accomplished from a message board. I encourage you to follow along and use the described method unless you have a better idea:

From a high level, what you want to do is inject a content script into every web page, which adds an API, accessible to the web page. When the site calls the API, the API triggers the content script to do something, like sending messages to the background page and/or send a result back to the content script, via ansychronous callback.
The main difficulty here is that content scripts which are "injected" into a web page cannot directly alter the JavaScript execution environment of a page. They share the DOM, so events and changes to DOM structure are shared between the content script and the web page, but functions and variables are not shared. Examples:
• DOM manipulation: If a content script adds a element to a page, that will work as expected. Both content script and page will see the new .
• Events: If a content script sets up an event listener, e.g., for clicks on an element, the listener will successfully fire when the event occurs. If the page sets up a listener for custom events fired from the content script, they will be successfully received when the content script fires those events.
• Functions: If the content script defines a new global function foo() (as you might try when setting up a new API). The page cannot see or execute foo, because foo exists only in the content script's execution environment, not in the page's environment.

Additional detail about exactly how this can be accomplished is located here:

[url removed, login to view]

Looking to make some money?

  • Set your budget and the timeframe
  • Outline your proposal
  • Get paid for your work

Hire Freelancers who also bid on this project

    • Forbes
    • The New York Times
    • Time
    • Wall Street Journal
    • Times Online