* Get a script connection, and if there is no script associated with the tab, it injects it. * * @param {string} scriptId * @param {number} tabId

* Adds a static context as a children of this context * * @param {StackingContext} context

* Initialize the settings inside local storage to their default values

* Update the devtools pages visibility status in order to decide whether to start or stop the DOM observer * * @param {number} tabId The tab id *

* Just a utility function to allow adding and removing it as an event listener

* Executes the check callback on the element passed as a parameter. Returns wether or not this Node creates a static context. * * @param {N

* Find the stacking context that contains a specific node as a child of its element. If the node creates a stacking context, return it. * * @param

* Get the relative position of a specific element in the page (iframes included) * * @param {StackingContext} context * @return {Object} The relat

Get the svg element as a string from a file source

* Check whether or not this element has an open shadow DOM * * @param {Node} element The element to be checked * @returns {boolean}

* Initialization method

* Creates the element that will be used to highlight the contexts in the page. * * @return {Node} The actual DOM element with coherent styles appli

* Inject the content script into a tab

* Check if an element is an iframe that exposes its content to javascript * * @param {Node} element The element to be checked * @returns {boolean}

* Load the extension settings * * @returns {Promise<Object>}

* Send a DOM Changed warning to the extension panel and sidebar

* Attach a mutation observer to the DOM and notify the extension that the contexts should be refreshed

* Start the DOM Observer * * @param {number} tabId

* Stop the DOM Observer * * @param {number} tabId

Get the single svg element from a string that may contain also other elements

* This will convert a stacking context to a JSON-friendly object in order to pass it to the background script and the devtools panel and sidebar.

* Utility method to traverse a DOM element and check if it's a stacking context. It's recursive and * will traverse all the children down the tree.

* Analyzes the page related to a specific tab id and returns a JSON description of the stacking contexts. * * @param {number} tabId * @returns {A

* Analyse the page and initialize the 'allContexts' and 'rootContext' variables.

* Creates a new Stacking Context object * * @param {Node} element * @param {boolean} isInIframe * @param {Node} frame * @

* Creates a new ContextsContainer * * @param {string} name The container name * @param {Node} element The element related to this cont

* Instruct the content script related to a specific tab to get the details about the last inspected element. * * @param {number} tabId * @param {

* Detect which node was tagged as "last inspected" from the devtools, and initialize the related variable.

* Returns a copy of all the contexts converted to JSON. * * @return {Array} list of all contexts converted to JSON.

* Get some details about the last selected element and its context * * @param {number} tabId * @returns {Object} The element details

* Get some details about the last inspected element. * * @returns {Object} An object containing the id of the context associated to the element and

* Get all the iframes sources, to implement inspection on iframes * * @return {Array<string>} All the iframes src attributes

* Returns a path to get the element of a specific context even if it is inside an iframe or shadow DOM * * @param {Integer} contextId * @returns

* Highlight a context on a specific page. * * @param {number} tabId * @param {number} contextId The id of the context to be highlighted

* Highlight the DOM Element related to a context. * * @param {number} id The id of the context to be highlighted.

* Check whether or not we're interested in this mutation and want to send a warning in the extension panel and sidebar * * @param {MutationRecord}

* Check whether a specific mutation found by the observer was caused by our own extension or was generated by the page * * @param {MutationRecord}

* Send a message to the extension panels to warn that the contexts should be refreshed.

* Handle the background handler errors (right now it just prints them to the console)

* Save the new settings in the local chrome extension storage * * @param {Object} newSettings The updated settings * @returns {Promise}

* Scrolls the page related to a specific tab id in order to show a context. * * @param {number} tabId * @param {number} contextId

* Scroll the page to show the element related to a specific context. * * @param {number} id The context id.

* Send a message to the extension panels to warn that the contexts should be refreshed.

* Start observing the changes in the DOM

* Stop observing the changes in the DOM

* @returns A JSON-friendly object to represent this container

* Remove the highlight that was set on the context. * * @param {number} tabId

* Remove the highlight element from the page.