ttu: mostly unchanged save for refactoring
mokuro: parses page per page (or double page per double page), not much is done aside from that since the new popup system works fine with it now
readwok: nothing in particular, parses with every new thing that comes in, and does the same thing as ttu to not parse out of view paragraphs
texthooker: same as readwok
wikipedia: parses text in view (many things are still unparsed because of the amount of html elements, but not a hard fix), popup text gets parsed but going for the reader's popup can close wikipedia's popup depending on position, but that's basically a wikipedia problem (and the text in the popup is just the article's first few lines so people who really need it can just go to that other page)
pain points/unsure/more work later stuff:
mokuro files need mokuro in the file name because I didn't look up much on how better it could be handled
likewise, some people use texthooker pages locally, we could make a rule for filename if there's nothing better
I considered maybe a button in the settings thing (next to settings) like "this is a mokuro manga", "this is texthooker page" otherwise, but again, maybe I'm missing something better
not sure all the web_accessible stuff in the manifest.json was needed
"stuffAfter" name is bad but honestly don't know what else to call it, brain is mush
some more refactoring can be done as I noticed a lot of similarities after implementing readwok/wikipedia that I hadn't before doing the refactor
mokuro has a \<p> per line even within a textbox, so words/expressions that crosses over doesn't get parsed properly, kind of not a jpdbreader problem I think, and thankfully most manga is typed properly that it might be a rare occurence to be an issue, I might fix this with userscript or weird jank later
ttu: mostly unchanged save for refactoring mokuro: parses page per page (or double page per double page), not much is done aside from that since the new popup system works fine with it now readwok: nothing in particular, parses with every new thing that comes in, and does the same thing as ttu to not parse out of view paragraphs texthooker: same as readwok wikipedia: parses text in view (many things are still unparsed because of the amount of html elements, but not a hard fix), popup text gets parsed but going for the reader's popup can close wikipedia's popup depending on position, but that's basically a wikipedia problem (and the text in the popup is just the article's first few lines so people who really need it can just go to that other page)
pain points/unsure/more work later stuff:
tested on firefox/chrome