System for controlling browser extensions

A system includes a processor configured to execute a web browser in a first browser execution process initiated by an operating system of the system. The system includes a browser extension installed in the web browser, the browser extension including a markup language file and a file specifying at least one type of action related to a page element on which the browser extension seeks to act. The web browser may be configured to receive a set of rules from a web publisher associated with a first web page prior to rendering the first web page, determine based on the file, without loading the browser extension, that the browser extension is configured to implement a first action prohibited by the set of rules, and restrict the browser extension from implementing the first action on the first web page.

TECHNICAL FIELD

This application generally relates to web technology, and more particularly, to web browser extensions.

BACKGROUND

Web browsers implemented on a web-enabled computing device allow users to access all kinds of content. Web browsers are configured to read programmatic code and render that code as web pages, which may include rendering both audio and visual content contained in various media files (e.g., image, video, and audio files), as well as performing other functions defined in the programmatic code. Web pages are generally implemented using programming languages such as HTML (including HTMLS), CSS, and JavaScript, among a number of other available programming languages.

Some browsers allow users to install add-ons (or extensions) to the browser, where such extensions add functionality to the browser and operate as an integrated part of the browser. Browser extensions may be implemented using programmatic code that is written using the same programming languages that are used for implementing web pages, such as JavaScript. From a browser's perspective, extensions effectively function as web pages that are an integrated part of the browser once they are installed. By installing extensions that are of interest to him or her, a user can effectively create a custom browser that includes the functionality of the extensions they choose to install.

In current Internet systems, there is no way to ensure the reliability, security, and integrity of intended content delivery. Publisher websites have established a level of accountability, predictability, and trusted content delivery. However, third party browser extensions have the ability to infiltrate this trusted relationship in ways that can be unclear to the users and potentially damaging to all parties involved. Today, many browsers allow the creation and installation of extensions which can modify or interact with the browser, computer system, or content, in some cases modifying the content is ways that are not allowed or desired by certain parties, such as advertising blockers, advertising injectors, or various malware.

These third party extensions change the direct relationships between the web publisher and the user which, if offered with the right controls, can have positive implications for both parties. However, if no controls are in place, many publishers and content providers may retreat from the open Internet behind closed applications or paywalls, making it more difficult for users to find and enjoy useful content. It is difficult for users to know who and which extensions to trust in this environment.

SUMMARY

According to one aspect, a system includes a processor configured to execute a web browser in a first browser execution process initiated by an operating system of the system. The system includes a browser extension installed in the web browser, the browser extension including a markup language file and a file specifying at least one type of action related to a page element on which the browser extension seeks to act. The web browser may be configured to receive a set of rules from a web publisher associated with a first web page prior to rendering the first web page, determine based on the file, without loading the browser extension, that the browser extension is configured to implement a first action prohibited by the set of rules, and restrict the browser extension from implementing the first action on the first web page.

Other implementations of this aspect include corresponding methods, apparatus, and computer programs, configured to perform the actions of the methods, encoded on computer storage devices.

According to another aspect, a method includes generating a set of rules using a microprocessor of computing device associated with a web publisher, the web publisher being a publisher of a first web page, the set of rules governing management of web browser extension behavior associated with the first web page. The method includes applying the set of rules to control which browser extensions may implement actions on the first web page. A first rule in the set of rules may permit at least one browser extension to reformat the first web page. A second rule in the set of rules may control which types of browser extensions are allowed to operate on the first web page. A third rule may specify a certain type of browser extension to make select changes or substitutions to elements of the first web page. The web publisher may provide the set of rules to a remote server. The remote server may provide access to a web browser to obtain the set of rules. Using the microprocessor of the computing device associated with the web publisher, the web publisher may obtain a record of extension-based interactions with the first web page. Upon detecting that a first browser extension is attempting to implement a first action the first web page, the web publisher may withhold a permission to the first browser extension to implement the first action the first web page, using the set of rules.

DETAILED DESCRIPTION

In various examples, a web browser may include or be configured to interact with one or more browser extensions. In this context, a “browser extension” may include one or more web pages packaged or grouped together as a definable whole, and configured to extend the functionality to the web browser. As described herein, “browser extensions” are small software programs that can modify and enhance the functionality of a web browser. They may be written using web technologies such as HTML, JavaScript, and CSS. Extensions may have little or no user interface. In some implementations, extensions may provide a small user interface icon or other user interface that may modify a browser's “chrome”, which is defined herein to include an area outside of a webpage displayed in the browser (such as the borders of a web browser window, which include the window frames, menus, toolbars and scroll bars). Selecting the icon or the other user interface may activate the functionality of the extension within the browser.

Extensions may modify web pages, for example to block advertisements, or in some cases, malicious extensions may inject content, illegal activity, or advertisements to web pages against user intent and potentially harming the web publisher's brand. A web publisher as referred to here means a content provider associated with a web page, such as an online newspaper or online store, as examples.

Therefore in some cases, users visiting websites may have content (articles, text, images, videos, links, ads, etc.) that appears to be coming from a trusted web publisher's system, but in reality, the content has been replaced by third party content without the user or the web publisher knowing. In some cases, advertisers can also lose revenue when charged for ads that are not actually seen. For example, extensions may remove or replaces ads, or may modify an order of elements on the web page. Extensions that are injecting ads might shuffle elements on the page to make sure their ads appear on prime locations at the expense of the web publisher's content.

Systems and methods described here provide a way for web publishers to enable the management of extension behaviors on web pages provided by the web publisher.

FIG. 1is a block diagram illustrating an example system that implements browser extensions. In the example ofFIG. 1, a local computing device102is illustrated as communicating with a remote web publisher104in order to provide, using a display106, a browser window108which contains a page110that is stored at the remote web publisher104. The web publisher104may be a computing device such as a server, for example.

The local computing device102may generally represent virtually any computing device which may be configured to execute a browser application112, and to communicate with the web publisher104. For example, the local computing device102may include any standard desktop or personal computing device, any laptop, notebook, or netbook computer, any tablet computer, or any Smartphone, television with at least one or more processor, or other mobile computing device. Such computing devices, and other computing devices, may be configured to access the web publisher104over one or more computer networks, in various manners, such as the public Internet, private intranet, or other network, to thereby access the web publisher104. Consequently, the display106may be understood to represent virtually any type of display, e.g., monitor, touch-screen, or any other type of visual or auditory display.

In the examples that follow, it is generally assumed that the local computing device102and the browser application112communicate with the web publisher104over the Internet, typically using protocols for identifying, accessing, and rendering the page110, e.g., from a web server represented by the web publisher104. However, it will be appreciated that such examples are provided merely for the sake of clarity and conciseness, and, as just referenced above, are not intended to be limiting of the various manners in which the local computing device102may obtain, process, or provide content in association with the browser application112and the browser window108.

Thus, in the types of examples just referenced, it may generally be assumed that the page110represents any of the many types of webpages which are available over the public Internet. For example, in a simple scenario, the page110may represent a substantially static page which includes text, sound, images, advertisements, or other content which may be desired by a user of the local computing device102and which may be displayed within the browser window108. In other examples, the page110may include many types of dynamic or interactive content, which often may be manipulated by the user within the context of the browser window108. In many scenarios, the page110and/or associated executable code may be understood to represent an application which may execute partially or completely at the web publisher104(e.g., may utilize the processor, memory, and other hardware/software resources of the web publisher104), while providing associated functionality and features to the user via the browser window108(and perhaps executing at least partially locally at the local computing device102). As just referenced, such webpages and associated functionalities and applications are implementable using various, conventional programming languages and techniques, such as, for example, hypertext markup language (HTML), Asynchronous JavaScript™ (AJAX), eXtensible Markup Language (XML), JavaScript™, JavaScript object notation (JSON), and many other types of code which may be executed.

In the example ofFIG. 1, the page110at the web publisher104is illustrated as including, or being associated with, a page model114. Generally speaking, the page model114provides a data structure which defines the structure, content, and appearance of the page110with respect to a programming language in which the page110is written.

In specific examples described herein, the page model114may represent a document object model (DOM) data structure. Such a DOM, as just referenced, represents a data structure (typically, a tree-like data structure) that itself represents source code (e.g., HTML) of the page110.

The web publisher104may also include a content manager98, which may be used to define rules111which the web publisher104can exchange with a browser or application environment. Using the content manager98and the rules111, the web publisher104may apply, control, monitor, audit, give, or withhold permissions or rights in real time to extensions or other applications. As one example, an online newspaper may withhold or modify which content it provides based upon which extensions may have control over the content before it is presented to the user. In some implementations, as discussed in more detail below, the web publisher may have access to an auditable record of certain extension-based modifications or interactions with a web page, which can be used for accounting or other purposes. The rules111may be stored in a database or other data store. In some cases, the rules111may be stored remotely from the web publisher104and the web publisher may access the rules111on an as-needed basis.

The rules111may regulate how content can be moved around on a homepage, or if the content can be pulled from other pages. For instance, Anne may want a customized online newspaper homepage. Anne's homepage might include fashion, travel, and news from my home state. The online newspaper may allow some replacement of the online newspaper's traditional homepage, but may also insist that breaking world news always stay in the same place, as an example. The online newspaper may also allow for personalized targeted ads in some slots, but might keep the banner always the same. Certain rules111may set criteria for syndication on other trusted sites, such as timing, formatting, or requiring links to the original content. Certain rules111may allow for removal or replacement of ads if another set of criteria is met. For instance, Ben be a paid subscriber to an online newspaper or have a ‘pay-per-view’ model of news consumption which would allow Ben to skip the ads. The rules111may enable crowdsource funding of a favorite story to encourage the author to continue digging into more in-depth research. As an example, a rule may enable contributing money or other value based on an article to offset future costs of the continued story.

As other examples, the rules111may include rules to enable the management of extension behavior. An example rule might allow any browser extensions to reformat the page, withhold different kinds of information, or serve information in a different order. Another example rule might control which third party partners are allowed to operate on the page. Another example rule might allow an extension to make select changes or substitutions to elements of the page. The changes or substitutions may be defined per page, per article, or in other ways. As yet another example, a rule may give multiple web publishers a way to define which content could be co-delivered with other publishers. For instance, one online newspaper and another online magazine could enable the news section from the online newspaper to be delivered with the Hollywood section of the online magazine.

As described herein, browser extensions may be utilized in the system100to provide additional features or functionalities in association with the browser application112, and thus with respect to the browser window108. The functionality of extensions may include but are not limited to observing and modifying network traffic and modifying the page model114of the page110. Other functionality may include interacting with the user, and adding buttons and other user interface elements to the browser and handling their interaction with the user.

As may be understood from the above description, extensions defined by extension files122may generally refer to browser extensions, add-ons, plug-ins, web applications (web apps), or any other program code which is designed to augment an appearance or functionality of the browser application112in providing the browser window108or the page110. Extension files122may in particular perform modifications to network requests related to web page110, such as canceling requests for individual resources, redirecting the request for web page110or referenced resources, modifying request and response headers of web requests related to web page110, or contributing authentication information to retrieve web page110. For example, extensions may in some cases, replace ad content121in the page110with other ad content, or may block the appearance or display of the ad content121.

In the simplified example of the system100ofFIG. 1, the extension files122are illustrated as being stored locally to the local computing device102. For example, a user of the local computing device102may program and store the extension files122for use by the browser application112. In additional or alternative examples, however, it may be appreciated that some or all of the extension files122may be accessed remotely. For example, in many cases, a particular extension may be packaged within a single folder or archive which may then be accessed by the browser application112. For example, a provider and/or distributor of the extension files122(not specifically illustrated in the example ofFIG. 1) may construct and package the extension files122, and a user of the system100may thereby download and install a desired extension, including accessing, downloading, and installing the extension files122at the local computing device102, as shown.

The browser application112may include a rendering engine126that is used to convert the page model114of a page110into information that can be displayed to the user in browser window108. The rendering engine126may include a verification engine140that is used to parses meta tags defined by the framework144. The verification engine140may grant appropriate extensions certain rights to interface or modify the page110in accordance with the publisher defined meta tags. The verification engine140may perform these actions in real-time. The verification engine140may revoke certain extensions the privilege to interface or modify the page110in accordance with the publisher defined meta tags. In some implementations, the verification engine140may present contractual terms associated with the web publisher104to the extension owner, and upon the extension owner's acceptance of the proposed contractual terms, the verification engine140may grant that extension the privilege to interface or modify the page110in accordance with the terms of the ratified contract. In some implementations, the verification engine140may programmatically log the transaction at a server such as the server170, bill the extension owner, and compensate the publishers at appropriate intervals, as examples.

The browser application112may include an extension manager128that may be responsible for installing, loading, and executing extensions. It may be responsible for handling communication between the extensions122and the rendering engine126. As such it may dispatch events to certain extensions122, collect their desired modifications to web requests, send them to the verification engine140, and send the results back to a network stack. Parts or all of this functionality may be executed by other components or the browser application112.

The extension manager128may also include a notifier142that may expose to a web publisher104certain browser elements, such as DOM elements. As discussed in more detail below with respect toFIG. 3, the DOM elements may include, for example, a name of certain or of each browser extension installed on the local computing device102or the browser application112, a classification enumeration for each extension, or a list of operations or actions that each browser extension may perform on a given web page (for example, create, read, update, delete).

In some cases, the extension manager128may also include a framework144(which may be programmed for example in JavaScript™) that allows publishers to programmatically iterate over a list of browser extension DOM elements. The framework144facilitates insertion of publisher-defined web page meta tags that may regulate how specific extensions may interoperate with the page110. The framework144may specify classifications of extensions may interoperate with the page110. The framework144may specify how operations or actions in general may be applied to the page110, such as update, read, delete, write, etc. In some implementations, the framework144may facilitate the definition of contractual terms by which a web publisher104may request payment from an extension owner for the right to perform various operations or actions on the page110.

Of course, it may be appreciated that the browser application112may include, or be associated with, various features, functions, operational modules, or other elements which are not specifically illustrated in the context ofFIG. 1. Similarly, it may be appreciated that the terminology used in association with the rendering engine126and the extension manager128is merely for the sake of example, and that the various types of browser applications112which exist, or which may exist in the future, may use different terminology when referring to the various concepts described herein.

The system100may also include a remote server170. The server170may include a central storage component180, a certification engine172, and an auditor engine182. In some cases, the central storage component180may store an audit trail or log corresponding to acts of various extensions on web pages. The certification engine172may be used to certify that browser extensions perform only the acts they are defined to perform. For example, the server170may automatically certify certain browser extensions, and assign those certified browser extensions classifications or sign the browser extensions with digital certificates based on auditing or test results of actions performed by the browser extensions (i.e., to verify that the browser extensions perform only the actions they allege to perform). The auditor engine182may be used to track and log certain actions of various browser extensions, e.g., in conjunction with the central storage component180and to evaluate the actions based on permissions and definitions associated with the extensions, which may also be stored in the central storage component180.

In some cases, the browser application112may access the central storage component180in real time to determine that an extension installed in the browser application has certain permissions. The browser application112may share that information with a web publisher104associated with a page110. For example, as discussed in more detail below with respect toFIG. 3, the browser which is requesting a page or a type of content may notify a web publisher104that the browser application112has extensions A, B, and C installed, and these extensions may do actions X, Y, and Z. The web publisher104may then, based on this information, choose to perform certain actions such as withhold content, serve a different form of the content, redirect a user of the browser application112to a different type of content (e.g. PDF or image), etc. When a user receives the content, the user may see how a browser extension has changed content from an original page provided by the web publisher104.

As also shown in the example ofFIG. 1, the browser application112may include an extension manager128which may be configured to implement some or all of the functionality of a particular extension, such as an extension associated with the extension files122. For example, the extension manager128may be configured to cause the rendering engine126to execute or otherwise render particular files or pages associated with the extension of the extension files122. The extension manager128may also be configured to execute background pages and content scripts, as discussed in more detail below with respect toFIG. 2. For example, a content script may be written to examine any page loaded in the browser application112for rendering within the browser window108in order to detect a presence of a specific type of content (e.g., a non-linked webpage, or an RSS feed). That is, the content script may execute such techniques on content of any webpage loaded and rendered within the browser window108. In the event that the content script detects the specified type of content, the content script may pass a message to the extension so as to notify the extension of the detected presence of the specified type of content. In some cases, the extension may perform an actual modification of the browser window108, (e.g., to execute a page action with respect to browser window108, such as displaying the extension icon120).

In the example ofFIG. 1, the browser application112is illustrated including discrete functional modules. However, it may be appreciated that such illustration is merely for the sake of example, and that other implementations are possible. For example, a single element of the browser application112may be implemented by two or more elements. Conversely, two or more components of the browser application illustrated inFIG. 1may be executed using a single component. Further, in the example ofFIG. 1, the local computing device102is illustrated as including at least one processor102a, as well as computer readable storage medium102b. That is, for example, the local computing device102may rely on two or more processors executing in parallel to achieve a desired result. Meanwhile, the compute readable storage medium102bmay represent any conventional type of computer memory which may be used, for example, to store instructions which, when executed by the at least one processor102a, cause the browser application112to perform various functions, and other relevant functions described herein. Additional or alternative example implementations of the system100ofFIG. 1are possible.

FIG. 2is a block diagram of an example of a browser extension in a web browser. As referenced above, extension files may include various different types of files. For example, an extension204as shown inFIG. 2may include a manifest file230which gives information about the extension204, such as, for example, the most important files and the capabilities that the extension might provide and the permissions the extension may have to interact with web pages and with a browser application. For example, the manifest230may include a name of the extension and at least one content type232that the extension204seeks to act on. For example, a content type may be an image, text, hyperlink, etc. The manifest230may also indicate one or more actions234or operations that may be performed by the extension204, such as read, write, update, delete, etc., as described in more detail below with respect toFIG. 3. It may be appreciated that, as referenced above, extensions may include various other types of files. For example, the extension204may include at least one HTML page220, such as, for example, an HTML page associated with a browser action providing a pop-up window in association with the browser window208or a content script file212that is capable of modifying the content of a page model of a webpage201to be displayed within the browser window208.

With respect to the execution of the extension204, other than the content script212as described below, execution thereof may proceed similarly to, but in a separate process than that of, the rendering engine of the browser application shown inFIG. 1. The content script212may represent, or include, a script which enables an associated extension to interact with webpages, e.g., the web page201. For example, the content script212may be implemented as JavaScript™ that executes in the context of the web page201as loaded into the browser.

Content scripts can find unlinked URLs in web pages and convert them into hyperlinks, increase font size to make text more legible, and add or block advertisements or other content. Content scripts can indirectly use browser APIs, get access to extension data, and request extension actions by exchanging messages with their parent extension. Content scripts can also communicate with web pages using the page model (e.g., DOM) shown inFIG. 1.

The content script212code may always attempt to be injected in a webpage, or may only sometimes be injected depending upon how the content script is written. Further, an extension204can insert multiple content scripts into a page, and each of these content scripts may have multiple files such as JavaScript™ and CSS files.

Content scripts, generally speaking, may be configured to, for example, read details of webpages visited by a browser application, and may be further configured to make changes to such pages. For example, the content script may be configured to read and/or modify the page model (e.g., DOM) of the page201. In example implementations, however, the content script may be restricted from accessing or modifying the page model (e.g., DOM) of the web page201by the rendering engine of the browser application based on rules provided by a web publisher associated with the web page201, as discussed above with respect toFIG. 1. In this way, the web publishers may manage or track extension behavior on certain web sites.

FIG. 3is a block diagram of example classifications and operations of browser extensions. The system300shown inFIG. 3includes two computing devices, a device310and a device320. Each of the devices may include a browser application such as the browser application described above with respect toFIG. 1. The browser application may include browser DOM elements that expose to a web publisher, such as the web publisher shown inFIG. 1, various browser extension elements, with user consent. For example, the browser extension elements may include a name of each browser extension installed on the device, a classification enumeration for each extension, and a list of operations each browser extension may perform on a given web page (for example, create, read, update, delete).

For example, as shown inFIG. 3, various browser elements312may be exposed to a web publisher by the browser application of the device310. The browser elements312include the names, classifications, and operations of three browser extensions installed on the browser application operating on device310. The first browser extension has a name “Adserver”, a classification “A”, and operations “Read, write.” The second browser extension has a name “Converter” a classification “B” and operations “Read.” The third browser extension has a name “Emailer” a classification “C” and operations “Update, delete”.

As another example, the browser elements322are associated with the browser application operating at device320. The browser elements322include the names, classifications, and operations of two browser extensions installed on the browser application operating on device320. The first browser extension has a name “Adserver”, a classification “A”, and operations “Read, write.” The second browser extension has a name “SocialStatus” a classification “B” and operations “Read, write, update.”

A client-side framework (for example in JavaScript) such as the framework144ofFIG. 1may allow web publishers to programmatically iterate over the list(s) of browser extension DOM elements. This framework facilitates insertion of publisher-defined web page meta tags that regulate how specific extensions may interoperate with a web page served by the web publisher. The classifications of extensions may interoperate with the page. Operations in general may be applied to the web page. The framework may facilitate the definition of contractual terms, for example by which a web publisher may require payment from an extension owner for the right to perform various operations on a page.

FIG. 4is a diagram of an example user interface of a web browser. The user interface may be implemented in a tab402or window of a web browser such as the browser application discussed above with respect toFIG. 1. The tab402may display a web page404including content410as well as ad420and ad422. In some cases, an extension operating in the browser application may seek to modify or block one of the ads, such as the ad420. In some cases, an extension may seek to replace the content410with other content not provided by a web publisher. In some cases, an extension may seek to replace the ad422with another ad or with other content.

For web publishers to maintain trusted brand integrity and authority, they need better control over the content they provide. Control over the extensions is twofold. In the current business model a web publisher, such as a newspaper, is organized to serve ads in order to continue to deliver free or low cost content to the end user. Furthermore, the newspaper has legal obligations to its advertising partners to ensure brand integrity is maintained by appropriately serving ads against the right stories. For instance, a chocolate supplier might not want its advertisements placed next to a story related to increased diabetes and obesity rates. Today's ad-blocker extensions, at best, remove revenue sources that publishers use to ensure continued high-quality low cost content delivery to its users. Today users agree to the implied terms of service from service providers to receive content in combination with advertising, or have the opportunity to opt-out by purchasing into models that give them limited advertising or add-free content. But, the extension mentioned above, merely blocks ads from being served. In another scenario, the ad-extension replaces the newspaper ads for its own, creating liability for the newspaper when the chocolate ad gets served against the wrong article.

Extensions can also provide service to publishers that they might not otherwise be able to self-support. For instance, Mamie's Lodge, a local B&B has finally established a web-presence. As a trusted brand, they have also started serving local ads on their reservations site. Mamie's Lodge would like to enable a trusted extension to provide currency conversion on their site, but Mamie's Lodge does not currently have the ability to control whether its users are getting accurate conversion rates.

Extensions also affect users. For example, Susie reads the fashion, weather, and wedding section of the online newspaper everyday. She also likes to read the topline news, but this is usually at the bottom of her list. She would love to have a personalized online newspaper homepage that puts her favorite articles first. She could actively choose her favorite articles, but would prefer not to spend the time doing so. If she could install an extension that would track how much time and how often she reads sections of the newspaper and update the article layout of personalized homepage accordingly, then she would read the online newspaper even more. The online newspaper would like to support this effort but doesn't yet have the capabilities. If they could control who the provider of this service was, then they would be able to ensure brand integrity and offer a better user experience.

As yet another example, extensions can provide services to users of mobile devices. For example, Tom just bought the latest smart watch. He is trying to stay away from his devices as much as possible, but there are a few headlines he is always on the lookout for. If he could have certain online newspapers push specific topics to his watch, which would be integral to his fast-paced workday. These publishers might co-mingle their content if they could guarantee the right delivery.

FIG. 5is a flowchart illustrating a process for enabling trusted browser extensions, in accordance with an example implementation. The process shown inFIG. 5may be performed at least in part by a computer system such as the system100shown inFIG. 1, for example using the browser application112of the local computing device102shown inFIG. 1. The system may receive a set of rules form a web publisher associated with a first web page prior to rendering the first web page (510). For example, the browser application112shown inFIG. 1may receive a subset of rules from the rules111from the web publisher104, prior to rendering the page110using the rendering engine126.

The system may determine, without loading any browser extensions, that a browser extension installed in the web browser is configured to implement a first action prohibited by the set of rules (520). For example, the system may use the framework144to determine that a browser extension is configured to delete content on a web page, and that the rules prohibit deleting content on that web page. Thus, the system may restrict that browser extension from implementing the first action on the first web page (530). Of course, it will be understood the system may restrict the browser extension from implementing multiple actions at a time. Alternatively, if the system determines that the browser extension installed in the web browser is not configured to implement the first action prohibited by the set of rules, the system may allow the browser extension to implement the first on the first web page (540). The system may generate a record of the first action on the first web page (550). For example, the system may log a name of a browser extension that updated advertising content on the first web page. In some cases, the system may send the record to a central storage component180of a remote server170, as shown inFIG. 1, which may in turn be accessed by a web publisher with appropriate permissions.

The process shown inFIG. 5may operate on multiple (e.g., all) extensions installed in a web browser at the same time, and in some cases, the system may restrict multiple extensions (or in some cases, all installed extensions) from implementing one or more given actions on a given web page at the same time, in real-time, without any delay from a user's perspective.

The memory604stores information within the computing device600. In one implementation, the memory604is a volatile memory unit or units. In another implementation, the memory604is a non-volatile memory unit or units. The memory604may also be another form of computer-readable medium, such as a magnetic or optical disk.

The processor652can execute instructions within the computing device650, including instructions stored in the memory664. The processor may be implemented as a chipset of chips that include separate and multiple analog and digital processors. The processor may provide, for example, for coordination of the other components of the device650, such as control of user interfaces, applications run by device650, and wireless communication by device650.

Processor652may communicate with a user through control interface658and display interface656coupled to a display654. The display654may be, for example, a TFT LCD (Thin-Film-Transistor Liquid Crystal Display) or an OLED (Organic Light Emitting Diode) display, or other appropriate display technology. The display interface656may comprise appropriate circuitry for driving the display654to present graphical and other information to a user. The control interface658may receive commands from a user and convert them for submission to the processor652. In addition, an external interface662may be provided in communication with processor652, so as to enable near area communication of device650with other devices. External interface662may provide, for example, for wired communication in some implementations, or for wireless communication in other implementations, and multiple interfaces may also be used.

The memory664stores information within the computing device650. The memory664can be implemented as one or more of a computer-readable medium or media, a volatile memory unit or units, or a non-volatile memory unit or units. Expansion memory674may also be provided and connected to device650through expansion interface672, which may include, for example, a SIMM (Single In Line Memory Module) card interface. Such expansion memory674may provide extra storage space for device650, or may also store applications or other information for device650. Specifically, expansion memory674may include instructions to carry out or supplement the processes described above, and may include secure information also. Thus, for example, expansion memory674may be provided as a security module for device650, and may be programmed with instructions that permit secure use of device650. In addition, secure applications may be provided via the SIMM cards, along with additional information, such as placing identifying information on the SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory, as discussed below. In one implementation, a computer program product is tangibly embodied in an information carrier. The computer program product contains instructions that, when executed, perform one or more methods, such as those described above. The information carrier is a computer- or machine-readable medium, such as the memory664, expansion memory674, or memory on processor652, which may be received, for example, over transceiver668or external interface662.