Context aware browser policy
Systems and methods for a web event framework include receiving at a framework plugin an event from a web browser, wherein the framework plugin is coupled to the web browser, generating, by the framework plugin, a framework event based on the event, forwarding the framework event to a framework server coupled to the framework plugin, receiving at the framework server the framework event from the framework plugin, determining, at the framework server, a framework action based on the framework event and a framework policy, forwarding the framework action to the framework plugin, and executing the framework action by the framework plugin, wherein executing the framework action includes modifying one or more settings for the web browser, wherein the modified settings are based on the framework policy and sending an instruction to the web browser to cause the web browser to reload at least one web page under the modified settings.
1. An apparatus, comprising:
a memory; and
a processor operatively coupled to the memory, the processor configured to:
receive a page loaded framework event from a compute device, the page loaded framework event indicating that a page having a domain parameter is loaded on a browser running on the compute device, the browser including initial settings;
further receive an external event indicating a characteristic of the compute device;
identify, based on the page loaded framework event and the external event, a policy that is associated with the domain parameter and that defines modified settings to be used reload the page;
generate an executable file based on the policy, the executable file including action instructions to:
change the initial settings of the browser to the modified settings;
send to the browser a reload instruction to reload the page using the modified settings; and
initiate an external process related to the external event in the browser; and
send the executable file to the compute device such that the compute device, in response to receiving the executable file, executes the action instructions.
2. The apparatus of claim 1 , wherein the executable file further includes action instructions to:
store, prior to execution of the action instructions to change the initial settings, the initial settings; and
reset, after execution of the action instructions to initiate an external process, the initial settings for the browser.
3. The apparatus of claim 1 , wherein the policy is further associated with a type of the browser.
4. The apparatus of claim 1 , wherein the page loaded framework event identifies a user of the compute device, and the policy is further associated with the user of the compute device.
5. The apparatus of claim 1 , wherein the initial settings includes at least one of: a setting associated with a visual element of the page, a setting defining a security element, a setting providing auto-complete functionality, or a setting providing debugging functionality.
6. The apparatus of claim 1 , wherein:
the external event includes a determination that a plugin associated with the browser has been disabled;
the plugin is configured to detect that the page is loaded on the browser, and cause the compute device to generate the page loaded framework event; and
in response to determining that the plugin being disabled, the external process includes termination of a functionality associated with the browser.
7. The apparatus of claim 1 , wherein one of the modified settings includes a change to a database entry.
8. A non-transitory processor-readable medium storing code representing instructions to be executed by a processor, the code comprising code to cause the processor to:
receive a page loaded framework event from a first compute device running a first browser, the page loaded framework event indicating that a first instance of a page having a domain parameter is loaded on the first browser, the first browser including first settings;
further receive an external event indicating a characteristic of the first compute device;
identify, based on the page loaded framework event and the external event, a policy defining second settings for a second browser;
generate an executable file based on the policy, the executable file including action instructions to:
change the first settings to the second settings of the policy;
send to the second browser a load instruction to load a second instance of the page on the second browser with the second settings; and
initiate an external process related to the external event in the second browser; and
send the executable file to a second compute device running the second browser such that the second compute device, in response to receiving the executable file, executes the action instructions.
9. The non-transitory processor-readable medium of claim 8 , wherein the executable file further includes action instructions to:
store, prior to execution of the action instructions to change the first settings, the first settings; and
reset, after execution of the action instructions to initiate an external process, the first setting.
10. The non-transitory processor-readable medium of claim 8 , wherein the policy is associated with at least one of: a type of the first browser, a type of the second browser, or a user of the second compute device.
11. The non-transitory processor-readable medium of claim 8 , wherein the first settings include: a setting associated with a visual element of the page, a setting defining a security element, a setting providing auto-complete functionality, or a setting providing debugging functionality.
12. The non-transitory processor-readable medium of claim 8 , wherein the first browser and the second browser are different types of browsers.
13. The non-transitory processor-readable medium of claim 8 , wherein:
the policy is a first policy and the executable file is a first executable file; and
the code further comprises code to cause the processor to:
identify, based on the page loaded framework event and the external event, a second policy defining a stored settings configuration associated with the first browser;
generate a second executable file based on the second policy; and
send the second executable file to the first compute device running the first browser such that the first compute device, in response to receiving the second executable file, reloads the first instance of the page using the stored settings configuration.
14. An apparatus, comprising:
a memory; and
a processor operatively coupled to the memory and configured to execute a plugin associated with a browser, the processor configured to:
generate, in response to detecting a first page being loaded on the browser, a first page loaded framework event indicating the first page being loaded;
further generate a first external event indicating a first device characteristic;
send the first page loaded framework event and the first external event to a compute device such that the compute device, in response to receiving the first page loaded framework event and the first external event, generates a first executable file based on a first policy associated with the first page;
execute, in response to receiving the first executable file, the first executable file to:
change first settings for the browser to first modified settings of the first policy to collectively produce a first settings configuration;
cause, after the changing the first settings, the browser to load the first page with the first settings configuration; and
initiate a first external process related to the first external event;
generate, in response to detecting a second page being loaded on the browser, a second page loaded framework event indicating the second page being loaded;
further generate a second external event indicating a second device characteristic;
send the second page loaded framework event and the second external event to the compute device such that the compute device, in response to receiving the second page loaded framework event and the second external event, generates a second executable file based on a second policy associated with the second page; and
execute, in response to receiving the second executable file, the second executable file to:
change second settings for the browser to second modified settings of the second policy to collectively produce a second settings configuration;
cause, after the changing the second settings, the browser to load the second page with the second settings configuration; and
initiate a second external process related to the second external event.
15. The apparatus of claim 14 , wherein the processor is configured to execute the first executable file to further:
store the first settings prior to the changing the first settings; and
reset the first modified settings after the causing the browser to load the first page.
16. The apparatus of claim 14 , wherein the first policy and the second policy are further associated with a type of the browser.
17. The apparatus of claim 14 , wherein the first policy and the second policy are further associated with a user of a compute device running the browser.
18. The apparatus of claim 14 , wherein the first settings includes: a setting associated with a visual element of the first page, a setting defining a security element, a setting providing auto-complete functionality, or a setting providing debugging functionality.
19. The apparatus of claim 14 , wherein the first settings include at least one setting that is not included in the second settings.