Report Website Bugs Here!
-
Hokay.
So iOS 15 works fine with the new Website.
iOS 13.3 works if you turn off javascript, except that there's a ton of stuff that can't be done without javascript, such as logging into your account, so that's not a solution.
Whether or not iOS 12 would have the same partial functionality if one turned off javascript is as yet unknown.iOS 12 and up still work with the old site.
As I know absolutely nothing about iOS, anything I write following this is pure unadulterated speculation on my part.
Maybe there have been changes to javascript reflected in the new site that don't impact the old site, and part of the changes in the different versions of iOS have occurred as a reaction to the changes in javascript?
Part of the differences in iOS versions has to do with javascript version compatibility, is another way of phrasing that.
If that were the case, then determining which version of javascript is used on the new site and checking the change logs for iOS to see if there was any mention of javascript version compatibility might allow for a clear statement of "You need to be running at least version x of iOS to utilize the new web site"? -
@segoth said in Report Website Bugs Here!:
So I’ve been having a problem with reading manga on my iPad Air since the OS 15 software update. Quite often it gives a website not found, it’s reset my iPad once, and on rare occasions it does work. It’s not a huge deal since I can still read LNs no problem, and I have no problem reading manga on my PC (I don’t read manga that often, but LNs all the time).
Bumping up this issue as I have exactly the same.
-
I don't know if this has been reported already, but the button labels don't quite fit on preordered volumes (see image). Tested with Safari/Chrome, both latest stable versions.
-
@thehalfwit I’m experiencing the same thing. I typically read on an iPad and have had no problems accessing the new website until yesterday. I updated my operating system to iOS 15.1 over the weekend and am now having issues. I can still access and read LN releases, but trying to load manga chapters just doesn’t work. It either won’t load at all or the page crashes as soon as I try and advance to the second page. I’ve tried reading in the app and am having the same problems. Additionally, I’m experiencing the same issues with both Safari and Chrome. Hopefully someone who knows more about this can either advise me how to fix the issue on my end, or determine how to fix it on J-NOVEL end.
-
So I didn’t even think to check manga compatibility, since I normally just read LNs.
I can’t get any manga at all to load on 15.1, it just says an error has repeatedly occurred. iPad Air 2, iOS 15.1.
The weird thing is that my iPhone 12 Pro iOS 14.5.2 can read manga.
-
@thehalfwit Going by that, maybe it has something to do with RAM usage? Older devices will have less, and maybe the manga reader is loading all the images into memory for decrypting without deallocating each one after it's done or something, or maybe it needs them in memory for the canvas element... I don't know.
-
I wonder, might borrow an iPad Pro later today to see if it has issues. Since even the oldest of those get 4GB of ram at a minimum, whereas my iPad Air 2 is limited to 2GB.
-
@thehalfwit Mine doesn't have any issues. iPad Pro 10.5 (2017, A1701), iOS 15.1.
-
Great Cleric, Volume 6 part 8
Yurika! Fight!
Calendar, both sites, says it's out already.
The Series page says it isn't.
Yurika confirms it isn't... -
@weasalopes Should be fixed now!
-
Can't something be done about the reader settings (color, font size...) disappearing so often? It's frankly pretty annoying.
-
I have been having graphical issues with the manga reader on a firefox based browser, sometimes when I change pages some portions of the left part of the image gets duplicated, it seems to be an issue with the animation of the page turning. Clicking on the middle of the page corrects it and it often goes away on its own after a few seconds. I will try to get a screenshot but it goes away fairly quickly
To be more specific, the leftmost 1/4 or so of the page on my monitor (a 27" 1440p monitor) is duplicated 6-8 times going all the way to the edge of the whitespace that should be margin on the page
The same issue occurs on the right side of the page when I go back a page
-
I mentioned it in the Bookworm manga thread, but in case it gets better attention here,
Bookworm Manga 2.5.1 has the wrong page count on the back end, so it won't mark as complete when you finish it. -
@pcj Should be fixed now
-
@cooper-cummings-gk5u8qq What version of firefox exactly?
-
Dahlia in Bloom has just released the prepubs for Vol 3 Parts 5 and 6, but according to the calendar, part 6 is meant to release next week.
-
I’ve been having the same issue of not being able to read manga in Safari on my iPad Pro 9.7” starting relatively recently, possibly associated with OS upgrade (can’t absolutely verify when problem started, I don’t read manga that often). Under at least iOS 15.1/15.2. Honestly not sure how much RAM I have on this; GSMArena says 2GB though, which would be consistent with the ‘not enough RAM’ hypothesis.
-
I felt the calendar page was fuller than before but wasn't sure why at first. Now I see that the page is using the full (extra long) names for all series, instead of the nicknames, which makes it look like a bulkier wall of text compared to before.
I would at least truncate the names so that they remain on a single line and the full name can be displayed when you're over it with the mouse. (I'm clearly talking about desktop-only here though.)
(I know there's supposed to be a feedback topic about the new site but I just can't find it right now so I posted here. 🤨)
-
The time in the calendar page used to auto-update and enable the links to the parts when it hit the release time but now I have to refresh the page for it to happen. I believe it broke after the latest update when the full names where implemented (see my post above).
Looking at my browser's console (Chrome 97; Windows) I'm seeing this error listed 3 times:
Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'sha256-Qj6AdMOUjZkBBUTjGW/OORBoqx2Pohcq8Bg/ZvZzgYw='". -
@terabyte said in Report Website Bugs Here!:
The time in the calendar page used to auto-update and enable the links to the parts when it hit the release time but now I have to refresh the page for it to happen. I believe it broke after the latest update when the full names where implemented (see my post above).
Looking at my browser's console (Chrome 97; Windows) I'm seeing this error listed 3 times:
Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'sha256-Qj6AdMOUjZkBBUTjGW/OORBoqx2Pohcq8Bg/ZvZzgYw='".I've also been experiencing this issue for the past days. I use a windows 10 desktop. I tested with chrome (which I normally use) and edge (which I have never used to visit J-Novel): between 9 and 10 PM, roughly 3 hours before the release of a part due at 1 AM, I set up the calendar on both browsers. I use dark mode in chrome.
Result: shortly after the 1 AM release the edge calendar was still showing 3 hours to release. The calendar in chrome must have updated at some point as it showed 1 hour to release.
Someone please save my F5 button and investigate :-)
