duckdotapk / ao3-enhancement-suite Goto Github PK

This is weird behaviour. Example work.

These should be managed better like hide lists and settings.

Probably do this with a timeout of a few seconds after you stop typing into it.

Currently, there's no way to tell what work(s) you have a comment saved for.

Example of one such comment: https://archiveofourown.org/comments/417968933

Basically wrapping each selected line in a <p> tag and then wrapping the whole thing in a <blockquote> should be good enough.

Maybe as an optional part of the FloatingWindow class in general, idfk.

I originally intended to implement this in #23 but kinda forgot about it.

Basically replicate what AO3 does with works that have many kudos by default and collapse excessive tags into a button that says And X more tags that you can click on to view the rest.

Generally overhaul the basic settings system to make adding settings much simpler.

It would also be great if they were saved as soon as they're changed instead of explicitly having to click "Save" I think.

A generic window class that encompasses all of the functionality of the hardcoded window the floating comment box uses.

These windows will also have minimize, maximize and close buttons with optional event handlers for each one (or at least close).

Maybe this is overengineering, since idk if anything else in this project will ever use windows like this, but I still think it'd be cleaner to make it more generic rather than hacking more shit into the comment box file.

An option alongside the existing collapse behaviour.

This project should be upgraded to TypeScript to improve the code's maintainability.

Most of them should probably have them any way. Just add it as a second argument.

I'm guessing this is as simple as adding it to the selector for the content script but definitely investigate this more.

There are various implementations of this around but I'd like to try making my own.

Currently, there is no way to view which of these things are hidden outside of happening across a work hidden by them.

Currently, the extension inadvertently removes all other objects in the savedComments storage when saving a new comment. THis is a big issue.

"hours" should be "hour" when it's only 1, same for minutes.

I forgot about these completely when making the Search Preset feature.

This will probably require restructuring stuff a bit.

Just creating this issue to close it immediately. The problem was I wasn't prepending "works" or "admin_posts" before the id when calling savedCommentManager.delete.

Be it a single chapter or for each chapter when viewing an entire work.

I consider this especially important as more and more features are added to this extension.

This might unfortunately require breaking user's existing blocklists however this has the massive benefit of keeping users blocked should they change their username.

I really should've done it like this in the first place but I only just considered it. 🤦‍♂️

AO3 even suggests doing it this way in their news post.

No idea why this happens, from memory at least. Will investigate.

Maybe just attach an event handler to the submit button or something.

I consider this somewhat of a priority because the user could tell the browser to not show them anymore popups and that'd break saving Search Presets.

Based on word count and a customisable read speed.

The read speed would default to some average, I'll probably just Google it and pick something sensible.

This seems vastly more complex because of this page's UI.

I believe I need to do this at this point in order to continue publishing updates on the Chrome Web Store.

This is more of a clusterfuck due to series stats not having class names on them.

Could probably greatly simplify the CSS with SCSS and also bundle it all into one file instead of a bunch of files.