Search results

No

That is the full implementation. We're not going to display the chapters themselves in our reader. e: Oops, I think I misunderstood your question. Yeah, if there's no "chapters" here on MangaDex yet it's just because nobody has created them yet. It's a manual process.

@Army_bloodcore Unfortunately your Edge version exists in a weird spot where it's just recent enough that it doesn't load polyfills, i.e. certain browser feature fixes, but it's also just outdated enough that it would need a certain polyfill and thus crashes. The easiest solutions would be...

Okay, I think I know what the issue is then. I'll try to do something about it.

@Army_bloodcore At first I wasn't surprised if Edge isn't working, but trying it now, I'm not seeing anything wrong. What's the version number? If you don't know how to check that, you can see it from this link...

^

Sorry, but I have to reject the suggestion as it stands. It'd be unnecessarily complex to implement and cache for, not to mention we have plans to make changes to the follows regardless and language-specific follows wouldn't really work. That said, maybe there's some other way to achieve a...

And what browser are you using

Sorry, but I don't think I will. It would cause some pretty confusing behaviour inside the reader if you think about it for a moment.

The other one was deleted. There were several duplicates. Chapters 7, 30 and 31 to be specific

@Wolvenworks Yeah, if there are two chapters with the same number and by the same group, the reader doesn't like it at all and starts doing weird things. I'll have to fix it some day, although people shouldn't be uploading the same chapter twice anyway.

@Wolvenworks Are you sure you don't just feel like it's 15 minutes? lol Seriously though, I don't know how or why that would ever happen. It's only a couple of minutes.

Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience. Besides the MangaPlus update thing, I removed axios in favor of standard fetch, and also use Image.decode now to try and prevent flashing on page turns.

The chapter listing order on the manga pages is dumb and I probably should've fixed that ages ago already. I'll make it mimic the reader ordering sooner or later.

I don't think we'll be adding chapter-specific tags like this. Seems pretty rare that any given manga would have only a couple of explicit chapters. Unless you have a good bunch of examples to give, it seems to me that the H toggle and the Smut tag should take care of this.

@IAmInept I don't know how much worse it could've been. I guess the text could be in red and all over the artwork.

@sastrathebest Like I said, it's not a priority since doing editable widgets properly would involve basically rewriting the frontend, but it's not rejected per se. Just don't expect to see it any time soon. The point is, I don't really understand why it actually bothers you. I can completely...

What on earth is going on with the typesetting

Making the front page widgets editable would be nice, but not particularly a priority. Other than a couple of text-based update widgets, the entire front page is very much focused on various manga recommendations. Why the OP decides to place such focus on the one thing that isn't, I don't...

@Markgraf lol, admittedly not the first interpretation that would've come to my mind