tridactyl/src/commandline_content.ts

/** Inject an input element into unsuspecting webpages and provide an API for interaction with tridactyl */

/* TODO: 
    CSS
    Friendliest-to-webpage way of injecting commandline bar?
    Security: how to prevent other people's JS from seeing or accessing the bar or its output?
        - Method here is isolation via iframe
            - Web content can replace the iframe, but can't view or edit its content.
            - see doc/escalating-privilege.md for other approaches.
*/

// inject the commandline iframe into a content page
let clFrame = window.document.createElement("iframe")
clFrame.setAttribute("src", browser.extension.getURL("static/commandline.html"))
clFrame.setAttribute("style", "position: fixed; top: 0; left: 0; z-index: 10000; width: 100%; height: 36px; border: 0; padding: 0; margin: 0;");
window.document.body.appendChild(clFrame)

/** Focus the commandline input */
export let focus = ():void => clFrame.focus()
Unprofessionally large commit - Implement just about working commandline - Clean up excmd code - Move controller logic out of parsing - Document workarounds of webext problems 2017-09-29 18:29:36 +01:00			`/** Inject an input element into unsuspecting webpages and provide an API for interaction with tridactyl */`

			`/* TODO:`
			`CSS`
			`Friendliest-to-webpage way of injecting commandline bar?`
			`Security: how to prevent other people's JS from seeing or accessing the bar or its output?`
			`- Method here is isolation via iframe`
			`- Web content can replace the iframe, but can't view or edit its content.`
			`- see doc/escalating-privilege.md for other approaches.`
			`*/`

Convert to es6 modules Motivation: - Most test frameworks expect modules - I'm told they're the future Changes: - Every typescript source file is now an es6 module - Build system is now webpack (tho rollup makes nicer outputs) - Outputs of buildsystem are one js file per entry point (background, content, commandline_frame) - These bundled js files are generated by traversing the dependency graph of each entry point 2017-10-02 00:59:51 +01:00			`// inject the commandline iframe into a content page`
			`let clFrame = window.document.createElement("iframe")`
			`clFrame.setAttribute("src", browser.extension.getURL("static/commandline.html"))`
			`clFrame.setAttribute("style", "position: fixed; top: 0; left: 0; z-index: 10000; width: 100%; height: 36px; border: 0; padding: 0; margin: 0;");`
			`window.document.body.appendChild(clFrame)`
Unprofessionally large commit - Implement just about working commandline - Clean up excmd code - Move controller logic out of parsing - Document workarounds of webext problems 2017-09-29 18:29:36 +01:00
Convert to es6 modules Motivation: - Most test frameworks expect modules - I'm told they're the future Changes: - Every typescript source file is now an es6 module - Build system is now webpack (tho rollup makes nicer outputs) - Outputs of buildsystem are one js file per entry point (background, content, commandline_frame) - These bundled js files are generated by traversing the dependency graph of each entry point 2017-10-02 00:59:51 +01:00			`/** Focus the commandline input */`
			`export let focus = ():void => clFrame.focus()`