hardware(mess) {
            //since Chrome extension content-scripts do not share the javascript environment with the page
            //script that loaded jspsych, we will need to use hacky methods like communicating through DOM
            //events.
            const jspsychEvt = new CustomEvent("jspsych", { detail: mess });
            document.dispatchEvent(jspsychEvt);
            //And voila! it will be the job of the content script injected by the extension to listen for
            //the event and do the appropriate actions.
        }
/**
         * Allows communication with user hardware through our custom Google Chrome extension + native C++ program
         * @param		mess	The message to be passed to our extension, see its documentation for the expected members of this object.
         * @author	Daniel Rivas
         *
         */
Allows communication with user hardware through our custom Google Chrome extension + native C++ program
@param               mess    The message to be passed to our extension, see its documentation for the expected members of this object.
@author      Daniel Rivas
Allows communication with user hardware through our custom Google Chrome extension + native C ++ program @param mess The message to be passed to our extension see its documentation for the expected members of this object . @author Daniel Rivas
hardware(mess) {
            const jspsychEvt = new CustomEvent("jspsych", { detail: mess });
            document.dispatchEvent(jspsychEvt);
        }
hardware ( mess ) { const jspsychEvt = new CustomEvent ( "jspsych" , { detail : mess } ) ; document . dispatchEvent ( jspsychEvt ) ; }
Allows communication with user hardware through our custom Google Chrome extension + native C++ program
 @param               mess    The message to be passed to our extension, see its documentation for the expected members of this object.
Allows communication with user hardware through our custom Google Chrome extension + native C ++ program @param mess The message to be passed to our extension see its documentation for the expected members of this object .
//since Chrome extension content-scripts do not share the javascript environment with the page
 //script that loaded jspsych, we will need to use hacky methods like communicating through DOM
 //events.
 //And voila! it will be the job of the content script injected by the extension to listen for
 //the event and do the appropriate actions.
