mytlogos / enterprise-addon Goto Github PK

As long as the server is unreachable, any messages (on the premise that the offline session is valid) should be cached/saved, so that if the session begins right after the server is up again, all saved message are pushed (WebSocket) to the server. Messages should be saved in storage, so that a sudden browser shutdown does not result in a loss of data.

Search for RSS/Atom Feeds and sends it to server so it can scrape it/subscribe for update messages.

Display a error text below the finish button.

The ContentSelector should recognize if the current page harbors/is intended for update messages, like a table with latest updates and notify server about this page, so it can scrape it later for update messages.

If the overWatch executes multiple times with different results for the same result ancestor element, notify server of latest valid metadata and remove former data. This should be done by adding a number to each result, which starts at zero when the contentScripts are loaded in the specific page.
Pages with multiple contents may change link even if the page itself changes minimal, so give each contentScript at the start a number, so it referres the results with their result- and contentScript-id´s.
ContentScript ID´s reset at the start of the extension. Not needed ID´s should be freed so that it should be never run out of numbers.

The ContentSelector in analyzer script should recognize, if the current page is an ToC of one or multiple media and return ToC Content only. Notify Server of ToC.

On this youtube video the analyzer extracts the title incorrectly, (from the playlist or the video suggestions) if the window is small enough so that youtube playlist is below video (about half the screen width).

User should be able to set options of the extension, like blacklisting websites, enable offline support.

As an specific example, on this Youtube Video only the artist is matched, not the whole title.

Up to now, I just just console.log to log messages.
Using a log framework which sends data to server (if it can), should make discovering issues easier.

Clicking anywhere on the document may result in a message being send to background script, which could lead to an error being thrown if user is not logged in.
The click listener should check if the popup is even shown and return if it isn't shown or no selectText function is set.

The Background Script does not process any messages pertaining results of the overWatch Script, be it just an analyzeResult or progressResult.
The server should be notified of any of these result, so package it and send it to server over Websocket.

The highlighting (currently a border and reduced brightness) is not removed when the user is clicking the 'Reject' Button in the result popup in the bottom right corner.