Forum › Fluttering Feelings [SPOILER THREAD]
Fan art by krevascii:
Tried copying the author’s style, donno if it worked…
Anyway, read this manhwa if you haven’t, these two are seriously cute couple x)
Source:
http://krevascii.tumblr.com/post/120387384246/tried-copying-the-authors-style-donno-if-it
http://41.media.tumblr.com/2a2167c8371d7e24df65567f3dbfa955/tumblr_np8j11bUbF1u3wk9fo1_1280.jpg
last edited at Aug 18, 2015 2:52AM
@ kyra / Doonge
For chapter 36 (last week's chapter), I just re-tried the overtooning (overlay) translations via the bookmarklet.
It worked in one Chrome profile but in a completely new Chrome profile as well as in Firefox, it didn't work.
Specifically, the issue that I observed was as follows.
If you are doing the overtooning method for the first time, it works. You click the bookmarklet, and the chapter is translated.
But if you reload the page and try it again, it doesn't work anymore. When you click the bookmarklet, only the orange Overtooning logo appears next to the Comico logo on the top left, but the chapter won't get the overlays.
However, if I clear cookies, then it works once again. But just like before, it only works once then never again.
So I took a look at the "OverTooning CONSOLE".
This is when it works:
[overlayLoader.path] pathname: /titles/[0-9]+/chapters/[0-9]+$
[overlayLoader.run] End of pathing.
[overlayLoader.query] Ping feed: http://blackhorus.bumblebits.net (1)
[overlayLoader.path] Queries to be made: 2
[overlayLoader.run] End.
[overlayLoader.cors] http://bumblebits.net/oddsquad/feed/comico.toast.com/85/37.json?1
[overlayLoader.cors] http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0
[overlayLoader.cors] Response returned with non-OK status
[overlayLoader.cors] undefined
[overlayLoader.cors] https://[...]/kr/37/no37p01.png
[...]
[overlayLoader.cors] https://[...]/kr/37/no37p15.png
This is when it doesn't work:
[overlayLoader.path] pathname: /titles/[0-9]+/chapters/[0-9]+$
[overlayLoader.run] End of pathing.
[overlayLoader.query] Ping feed: http://blackhorus.bumblebits.net (1)
[overlayLoader.path] Queries to be made: 1
[overlayLoader.run] End.
[overlayLoader.cors] http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0
[overlayLoader.cors] Response returned with non-OK status
[overlayLoader.cors] undefined
I noticed that the difference between the two is that the one that works has
http://bumblebits.net/oddsquad/feed/comico.toast.com/85/37.json?1
http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0
and the one that doesn't work only has
http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0
http://bumblebits.net/oddsquad/feed/comico.toast.com/85/37.json?1
appears to contain all the URLs for the FF overlays.
(The other one is for other comics.)
But it only loads it the first time, and every subsequent time, it no longer loads, and I assumed that this is why it would fail.
I wasn't sure why it doesn't load it the second time. I suspected it might have to do with what is saved in Local Storage the first time around due to this part in the naver.reader.oss.js code:
for(var j = 0; j < this.data.feedList.length; j++) {
if(accessFeed.indexOf(j) == -1 && this.data.feedList[j].lastUpdate + 60 * 24 * 7 < MTime) {
overlayLoader.addLog('[overlayLoader.query] Ping feed: ' + this.data.feedList[j].url + ' (' + j + ')');
this.queries.push({feedID: j, udpdate: true});
}
}
where this.data comes from:
this.data = localStorage.getItem('overloaderData');
This would also make sense because when you clear cookies, Local Storage is also cleared.
So after a little more investigating, turns out it was definitely due to what was stored in Local Storage.
If I remove "Local storage" for the site "comico.toast.com", it works again.
Alternatively, I could go to edit Local Storage for "comico.toast.com"
Key:
overloaderData
Value:
{"feedList":[{"url":"http://bumblebits.net/oddsquad/feed","name":"Oddsquad","lastUpdate":23885657,"teamUrl":"http://www.oddsquad.org"},{"url":"http://blackhorus.bumblebits.net","name":"BlackHorus Scans","lastUpdate":0}],"webtoonList":[]}
If I change "lastUpdate":23885657 to "lastUpdate":0, then it works again.
Also, like I mentioned before, I have one specific Chrome profile where this issue is not occurring, as in, I use the bookmarklet multiple times without any problems. This is probably due to whatever was stored in Local Storage before.
In that Chrome profile, this is what's in Local Storage:
Key:
overloaderData
Value:
{"feedList":[{"url":"http://bumblebits.net/oddsquad/feed","name":"Oddsquad","lastUpdate":23885623,"teamUrl":"http://www.oddsquad.org"},{"url":"http://blackhorus.bumblebits.net","name":"BlackHorus Scans","lastUpdate":0}],"webtoonList":[{"wI":"85","wT":"Fluttering Feelings","wA":"ssamba","wB":"'Seol-a' and 'No-rae', two college girls that stumbled on one another.{endl}The sweet and sour story of two girls who are different in almost every single way.","fL":[0]}]}
So did something change in the naver.reader.oss.js code recently? This didn't used to be an issue.
Would you be able to find what's the issue?
Thanks!
The stuff below is what I initially thought was the problem when I first posted.
Now, I know that it has nothing to do with the issue.
However, it is still an error that you guys may want to look into.
In Firefox's Console, when I click the bookmarklet, I see this:
"[overlayLoader.path] pathname: /titles/[0-9]+/chapters/[0-9]+$" naver.reader.oss.js:1990:8
"[overlayLoader.run] End of pathing." naver.reader.oss.js:1990:8
"[overlayLoader.query] Ping feed: http://blackhorus.bumblebits.net (1)" naver.reader.oss.js:1990:8
"[overlayLoader.path] Queries to be made: 1" naver.reader.oss.js:1990:8
"[overlayLoader.run] End." naver.reader.oss.js:1990:8
"[overlayLoader.cors] http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0" naver.reader.oss.js:1990:8
Use of attributes' nodeValue attribute is deprecated. Use value instead. naver.reader.oss.js:2177:0
GET
XHR
http://blackhorus.bumblebits.net/comico.toast.com/85/37.json [HTTP/1.1 200 OK 242ms]
"[overlayLoader.cors] Response returned with non-OK status" naver.reader.oss.js:1990:8
"[overlayLoader.cors] undefined" naver.reader.oss.js:1990:8
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0. (Reason: CORS header 'Access-Control-Allow-Origin' does not match 'http://comic.naver.com').
Note the error at the end (bolded).
If I load
http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0
and check the HTTP header, indeed, I see this:
Access-Control-Allow-Origin: http://comic.naver.com
For this error to not occur, it would be to have "Access-Control-Allow-Origin" be "http://comico.toast.com" when serving URLs under http://blackhorus.bumblebits.net/comico.toast.com/. As far as I know, it is not possible to have multiple domains in "Access-Control-Allow-Origin".
last edited at Jun 1, 2015 2:28AM