Bug Report: autocompletion in "To:" field of Private messages

abacus

hero member

Activity: 618

Merit: 500

a clockwork miner

Quote from: binaryFate on May 13, 2014, 01:51:10 PM

I'll let you know here if I find a reason for that error, I'll check carefully all my requests going in/out.

Yes, let us know, this thing is getting curious.
And in case you find out that there aren't additional requests, AFAIK I'm left with one doubt:
How the hell fast do you type? Cheesy

binaryFate

legendary

Activity: 1512

Merit: 1012

Still wild and free

Quote from: theymos on May 13, 2014, 12:51:36 PM

You can get that error if you're sending HTTP requests too quickly. Each character typed generates a request, but this shouldn't be enough to trigger rate-limiting unless you're also doing many additional requests elsewhere. Maybe it could happen if your browser is doing prefetching, or if it isn't caching images properly.

Ok, thanks for the info. I don't think I'm doing anything special in terms of HTTP activity (and only one forum tab open). I don't get 503 errors on anything else when using the forum. Browsers are firefox 29.0 and chrome 34.0.1847.116 on ubuntu 12.04.

The good news is that it seems to happen only to me

I'll let you know here if I find a reason for that error, I'll check carefully all my requests going in/out.

theymos

administrator

Activity: 5222

Merit: 13032

You can get that error if you're sending HTTP requests too quickly. Each character typed generates a request, but this shouldn't be enough to trigger rate-limiting unless you're also doing many additional requests elsewhere. Maybe it could happen if your browser is doing prefetching, or if it isn't caching images properly.

binaryFate

legendary

Activity: 1512

Merit: 1012

Still wild and free

Quote from: abacus on May 12, 2014, 10:34:41 PM

I've just tried with fast random typing too, but still can't replicate it.

To see where that "" is coming from, in Firefox for example you can open Firebug, go to Console tab, click on the latest GET request and then look at the Response tab. This should give you some hint.
If you want to post here this Response PAY ATTENTION it is just html and DO NOT post also some sensitive data from other tabs like PHPSESSID or SMFCookie that could bring you security problems (if it happens then just logout, clear all cookies and login again ASAP; it should be enough).

Maybe it's worth mentioning that it's not sure that this kind of bug - if it's a bug - would be considered prioritary and then addressed because of the new forum software in development.
But that's just my impression; let's see if there is some news from the staff.

Good suggestion. Found that it happens whenever I get a 503 error on the autocompletion request. The response is then:

Code:


503 Service Temporarily Unavailable

503 Service Temporarily Unavailable
nginx

Truncated then to the first line which replaces the nick I'm typing (didn't check the javascript part but it must be that).

Still, I don't know why I often get this with a good connection on two different browsers and computers, in different locations, and that nobody else can reproduce. Huh

Indeed it's not high priority anyway.

abacus

hero member

Activity: 618

Merit: 500

a clockwork miner

I've just tried with fast random typing too, but still can't replicate it.

To see where that "" is coming from, in Firefox for example you can open Firebug, go to Console tab, click on the latest GET request and then look at the Response tab. This should give you some hint.
If you want to post here this Response PAY ATTENTION it is just html and DO NOT post also some sensitive data from other tabs like PHPSESSID or SMFCookie that could bring you security problems (if it happens then just logout, clear all cookies and login again ASAP; it should be enough).

Maybe it's worth mentioning that it's not sure that this kind of bug - if it's a bug - would be considered prioritary and then addressed because of the new forum software in development.
But that's just my impression; let's see if there is some news from the staff.

binaryFate

legendary

Activity: 1512

Merit: 1012

Still wild and free

Ok I will try to record a video tomorrow (simple pictures wouldn't be meaningful).
I think it happens only when I type fast enough (I can type quite fast) for the autocompletion to be useless (ie, it never gets time to propose me something before I hit next char).
I have high-speed connection, this is for sure not an issue here.

I can see this problem on both my desktop and laptop and both firefox and chrome. All under linux.

Lauda

legendary

Activity: 2674

Merit: 2965

Terminated.

Quote from: abacus on May 12, 2014, 04:07:46 PM

I am not able to replicate this bug. Autocompletion of this field seems to work flawlessly in my case.

Are you experiencing some slow internet connection when it happens? Or maybe are you using too many browser windows or tabs opened at the same time?

That field sends an Ajax request with the chars you typed and then you have to wait for the server response (the matched username).
Maybe that "" you see is the beginning of a message from the server (or also by the javascript that sends the request) like an error or timeout.

I have just tried this on Chrome and I couldn't replicate it either.
OP how about you record your screen and let us see what actually happens? This seems like simple step.

abacus

hero member

Activity: 618

Merit: 500

a clockwork miner

I am not able to replicate this bug. Autocompletion of this field seems to work flawlessly in my case.

Are you experiencing some slow internet connection when it happens? Or maybe are you using too many browser windows or tabs opened at the same time?

That field sends an Ajax request with the chars you typed and then you have to wait for the server response (the matched username).
Maybe that "" you see is the beginning of a message from the server (or also by the javascript that sends the request) like an error or timeout.

binaryFate

legendary

Activity: 1512

Merit: 1012

Still wild and free

Apologize if it was already posted, couldn't find it.

Happens to me on both firefox and chrome.
Step to reproduce: Go to messages, click new message. In the "To:" field, write: ' "luckybitsupport" ' (coud be any other name, but I think the longer the higher chance of issues).
See the weird (stochastic, looks like it depends on typing speed) behavior. Sometimes it works but most of the time the string just become ""

Topic: Bug Report: autocompletion in "To:" field of Private messages (Read 647 times)

503 Service Temporarily Unavailable