| Age | Commit message (Collapse) | Author | 
|---|
|  | We should insert the styles at the very start, because they hide things
that are displayed when you start watching. The credits handling always
happens at the end of the video.
Also reorder imports alphabetically. | 
|  | TV series on Netflix now display a "Watch Credits" button when the
credits start rolling.
We can hide this button using CSS and the credits will continue playing
to the end, but while it's displayed, the player controls are hidden.
Automatically click the button to make it go away and reactivate the
player controls.
The tricky thing, though, is that the "Watch Credits" button doesn't
have a click handler. Instead, it listens to the "pointerdown" event, so
we have to construct one programmatically (and turn on `bubbles`,
otherwise the button doesn't react to the event) and dispatch it.
Moved `with_player` to `wait_element`, because now I need to wait for
more DOM elements than just the player element.
Add a new `controls` module since I need to hide the player controls in
both `fullscreen_credits` and `watch_credits`.
Add the `DOM` lib to `tsconfig.json` to give us DOM types. | 
|  | This button appears now when the credits of TV series start playing. | 
|  | Move this function to a new module as I'd like to use it for checking
the "Watch Credits" button.
Also change from a callback to a `Promise`. Need to include the
`Promise` lib via ES2015 in tsconfig to be able to build with promises. | 
|  | I had initialised the `stylesheet` variable before the element existed
in the DOM. | 
|  | Since it looks like everything's going to happen in the content script,
might as well make this a user script instead.
Build with Browserify in order to get a compiled JS file compatible with
browsers.
For some reason I'm currently getting an error complaining that the
`stylesheet` variable is `null`. Need to look into that. | 
|  | Makes more sense to put it in the fullscreen_credits module. | 
|  | That was for testing and is no longer needed. | 
|  | Start to establish a bit of separation and organisation. | 
|  | I'd like to split up some functionality into modules, and it seems like
using TypeScript would be a good way to achieve that. |