Please log in. To create a new account, enter the name and password you want to use.
If you supplied an email address when you signed up or added a email later, you can have your password reset.
This user name doesn't exist. If you want to create a new account, just verify your password and log in.
This user name exists. If you want to create a new account, please choose a different name.
Enter the current email address you have registered in your profile. You'll get an email containing your new password.
You have no email address in your profile, so you can't have your password reset.
Password reset. Check your email in a few minutes
That account does not exist.
The email address specified is not registered with this account.
Delivery to this email address has failed.
From about several days ago, maybe due to some code update of my Firefox (13b) or site, Firefox works exactly like Chrome, which is very undesirable for me. Is it possible to restore it back by modify Post.highres();? Of course if you can make Chrome works like Firefox too it would be the best.
All right, apparently this bug is quite weird ಠ_ಠ
The problem starts when I replacing about:blank instances in javascript with /image/blank.gif.
As it turns out, the "about:blank" in chrome and firefox behaves differently: firefox tries to load http://yande.re/post/show/123/about:blank while chrome tries to load "about:blank" (the blank page) - that explains why it behaved differently between firefox and chrome.
Now after I replaced it with /images/blank.gif, both behaves exactly same - the unwanted one. small image ==> blank ==(wait_until_complete) ==> full.
Even if I change the url to something nonexistent, behavior in chrome stays same (small image ==> error/blank ==(wait_until_complete) ==> full) while it reverted to correct one in firefox.
tl;dr: bug turned into feature, fixed bug: loss of feature (ノಠ_ಠ)ノ彡 ┻━┻
edogawaconan
The problem starts when I replacing about:blank instances in javascript with /image/blank.gif.
As it turns out, the "about:blank" in chrome and firefox behaves differently: firefox tries to load http://yande.re/post/show/123/about:blank while chrome tries to load "about:blank" (the blank page) - that explains why it behaved differently between firefox and chrome.
Now after I replaced it with /images/blank.gif, both behaves exactly same - the unwanted one. small image ==> blank ==(wait_until_complete) ==> full.
Even if I change the url to something nonexistent, behavior in chrome stays same (small image ==> error/blank ==(wait_until_complete) ==> full) while it reverted to correct one in firefox.
tl;dr:
bug turned into feature, fixed bug: loss of feature (ノಠ_ಠ)ノ彡 ┻━┻
I'll see if there's actual solution for this.