Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

type numeric answer - chrome #425

Open
magvt opened this issue Apr 12, 2016 · 17 comments
Open

type numeric answer - chrome #425

magvt opened this issue Apr 12, 2016 · 17 comments

Comments

@magvt
Copy link

magvt commented Apr 12, 2016

The screen isn't accepting any response - from laptop or extern
numeric response
al keyboard.

@vsoch
Copy link
Member

vsoch commented Apr 12, 2016

@IanEisenberg added some kind of keyboard tracking to the experiments, and I think this would lead to the error you are seeing. Let's wait for his report on what he did.

@vsoch
Copy link
Member

vsoch commented Apr 12, 2016

Does the pop up appear continuously no matter what you do, and when you click "ok" ?

@magvt
Copy link
Author

magvt commented Apr 12, 2016

The error msg appeared only when I clicked NEXT.

@vsoch
Copy link
Member

vsoch commented Apr 12, 2016

Ok, so the order of operations is:

  • see page
  • click Next (without answering)
  • pop up appears
  • pop up won't go away / keyboard /mouse not responsive?

@magvt
Copy link
Author

magvt commented Apr 12, 2016

The order is:

· See page

· Try to type in response

· Click Next

· Pop up appears

I didn’t try to close the pop up.

From: Vanessa Sochat [mailto:notifications@github.com]
Sent: Tuesday, April 12, 2016 10:53 AM
To: expfactory/expfactory-experiments expfactory-experiments@noreply.github.com
Cc: Mary Ann Greene Mary.Ann.Greene@dartmouth.edu
Subject: Re: [expfactory/expfactory-experiments] type numeric answer - chrome (#425)

Ok, so the order of operations is:

  • see page
  • click Next (without answering)
  • pop up appears
  • pop up won't go away / keyboard /mouse not responsive?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/425#issuecomment-208946219

@vsoch
Copy link
Member

vsoch commented Apr 12, 2016

Ok, so you were unable to type anything in the box before hitting next, or clicking next cleared your answer from the box?

@vsoch
Copy link
Member

vsoch commented Apr 12, 2016

Could you please look in the console for errors? (right click on screen --> view source --> console tab). I just tested this experiment in the same battery, and after I get the error message I'm able to type in the box and continue:

image

@vsoch
Copy link
Member

vsoch commented Apr 12, 2016

It could be something specific to windows that was not tested.

@magvt
Copy link
Author

magvt commented Apr 12, 2016

I was unable to type anything in the box, and so I hit next in order to proceed. That’s when the pop up appeared,.

From: Vanessa Sochat [mailto:notifications@github.com]
Sent: Tuesday, April 12, 2016 11:14 AM
To: expfactory/expfactory-experiments expfactory-experiments@noreply.github.com
Cc: Mary Ann Greene Mary.Ann.Greene@dartmouth.edu
Subject: Re: [expfactory/expfactory-experiments] type numeric answer - chrome (#425)

Ok, so you were unable to type anything in the box before hitting next, or clicking next cleared your answer from the box?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/425#issuecomment-208956546

@magvt
Copy link
Author

magvt commented Apr 12, 2016

I closed out that experiment – and had to restart my laptop so I think it’s lost.
If you can get me back to it, I’d be happy to.

From: Vanessa Sochat [mailto:notifications@github.com]
Sent: Tuesday, April 12, 2016 11:31 AM
To: expfactory/expfactory-experiments expfactory-experiments@noreply.github.com
Cc: Mary Ann Greene Mary.Ann.Greene@dartmouth.edu
Subject: Re: [expfactory/expfactory-experiments] type numeric answer - chrome (#425)

Could you please look in the console for errors? (right click on screen --> view source --> console tab). I just tested this experiment in the same battery, and after I get the error message I'm able to type in the box and continue:

[image]https://cloud.githubusercontent.com/assets/814322/14465737/e265d3fa-0088-11e6-916e-139771196ce4.png


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/425#issuecomment-208963104

@vsoch
Copy link
Member

vsoch commented Apr 12, 2016

Sure thing, here you go

@magvt
Copy link
Author

magvt commented Apr 12, 2016

OK, here you go:

  1. screen 1 - I cannot enter a number in. I've attached the screen shot and console text.
  2. I hit next, got the error msg. I could not get to the console when the pop up was showing. I attached screen shot.
  3. I closed the pop up and copied the console text.

enter number - screen 1 console.txt
enter number - screen 1
enter number - screen after hitting next - console.txt

@vsoch
Copy link
Member

vsoch commented Apr 12, 2016

Thanks! Sorry I gave the wrong instruction - you want to do:

  • right click
  • inspect element
  • then select the "console" tab - it looks like this:

image

Some browsers will show it on the right side of the page as well. We are looking for text in red that would indicate an error.

@IanEisenberg
Copy link
Member

There is no keyboard tracking in this experiment. Nothing has been changed and other subjects have successfully completed it.

From the console output, she is using an old version of the cognitive reflection task, even though it has been updated on expfactory.org. (And was updated days ago). Not sure why.

@vsoch
Copy link
Member

vsoch commented Apr 12, 2016

@IanEisenberg please see expfactory/expfactory-docker#110 I have confirmed the commit in expfactory is identical to the current:

expfactory/expfactory-surveys@e9541ef

and that the survey.tsv files are identical between the one installed in expfactory, and the one pulled from a github this morning. Could you please clarify what you see to reflect this being an old version?

@IanEisenberg
Copy link
Member

You're correct, looking back at the html the experiment is up to date. Hm, not sure what's going on given that the task works for me and other users on Windows and Mac using chrome.

@vsoch
Copy link
Member

vsoch commented Nov 20, 2017

@IanEisenberg @magvt is this still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants