InformAction Forums

barbaz wrote:Not here.. I cannot reproduce the problem (nor what therube sees) from that test case.
What am I missing?

Maybe this related to browser/OS version? Although I'm and therube use different OS and browser (if therube don't change his useragent), but have same bug. Can you try test case in some Debian Live-CD (in VirtualBox if you worry about security)? It's don't request much time, because live-CD don't request any installation.

Renji wrote:Can you try test case in some Debian Live-CD (in VirtualBox if you worry about security)? It's don't request much time, because live-CD don't request any installation.

Sure, but it'll have to be in VirtualBox, but it's more of a stability question for me than a security question. My computer got killed twice last week, and it cost me half the week getting it back. I really can't afford to lose it yet again.
Downloading Debian 8.3.0 amd64 Cinnamon live ISO now...

... and can't reproduce there either.
Since I can't copy+paste into the live environment, I'm serving the test page off my local server.

I'm doing the following steps:
1) load the live image into blank VM
2) start Iceweasel 38.5.0, install NoScript
3) Navigate the test page on my local server. Temporarily Allow my server, since the page requires script to respond
4) Click the text field, which is pre-filled with "test", and hit Enter.

Page gets redirected to /search.xml (which I redirected to a "diagnostic" page on my server, for convenience) - all this happens successfully.
However, on repeating the steps trying typing something else in the text field, I noticed that the autocomplete popup tries to auto-fill the field with what I typed before. I don't have autocomplete on in my main environments. Could the hitting enter twice thing be autocomplete-related?

barbaz wrote:Since I can't copy+paste into the live environment, I'm serving the test page off my local server.

Just open this thread in browser and copy HTML sample from browser to local file.

barbaz wrote:3) Navigate the test page on my local server. Temporarily Allow my server, since the page requires script to respond

This bug appear only if scripts NOT allowed in NoScript. And no, testing page don't request any scripts. It classical GET request with some strange onClick event.

Renji wrote:This bug appear only if scripts NOT allowed in NoScript. And no, testing page don't request any scripts. It classical GET request with some strange onClick event.

With scripts disallowed pressing enter does nothing at all, regardless of how many times.

With scripts disallowed pressing enter does nothing at all, regardless of how many times.

On my end, first click is "dead", second click works as expected.

(Hitting Return instead of clicking the button does the same. Once the search has completed, it will continue to work. So to see the issue again, you need to open the link in a new tab.)

OK the relevant setting in NS is
NoScript Options > Advanced > Untrusted > Attempt to fix JavaScript links

This message shows up in the Browser Console (Ctrl-Shift-J) every time I click the Submit button or hit enter: This request is coming from NoScript, but I have no understanding of why it'd do that...

But I still don't understand why I'm getting such different behavior than everyone else here.
EDIT Oh, maybe you all are testing with the actual yandex site while I'm using the test page provided by Renji?

barbaz wrote:With scripts disallowed pressing enter does nothing at all, regardless of how many times.

Yes, same for me, if use HTML example. Now remove NoScript (via about:addons "remove"+"restart now" buttons), go to about:config and set javascript.enabled to false. After this pressing enter must work, although scripts still disable.

barbaz wrote:OK the relevant setting in NS is
NoScript Options > Advanced > Untrusted > Attempt to fix JavaScript links

Yes, disable "fix JavaScript links" resolve problem.

Not sure that's a resolution, as this looks to me like it could be a NS bug?

barbaz wrote:Not sure that's a resolution, as this looks to me like it could be a NS bug?

Temporally resolution if you don't need "fix links" option. But yes, it's still a bug.