Millisecond Forums

It may be that Google has followed through w/ their plan to completely remove plugin support from Chrome before the end of 2014:

https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/xEbgvWE7wMk

However, I am not aware of a recent update pushed to Chrome stable (afaik, the stable release is still 39.0.2171). So I am not sure why you observed that change in the last few days. I would recommend double-checking the browser's plugin settings just in case.

https://support.google.com/chrome/answer/142064?hl=en
https://support.google.com/chrome/answer/1247383?hl=en

Using an alternative launch method (e.g. the web player) is the way to go. As to why some of your textboxes are malformatted when running the script via the web player is hard to tell without any further details. Please provide the link to the launch page and -- if possible -- some screenshots illustrating the formatting issue.

Hi Dave,

Here is the link:

http://research.millisecond.com/ccritchley/EmotionsandproductperceptionsA.web
I have also attached a screenshot below so you can see what it looks like when this happens.  As I said in my earlier message, this only happens when I use the web player.  It is fine all the other ways I have tested it. 
Many thanks,

Rebecca 
 web

Hi again Dave,

I have had another look at the help page for chrome and they say that:

"Windows 8 users: Due to system limitations, only plug-ins using Pepper API, such as Flash, Native Client, and Chrome PDF Viewer will function properly when Chrome runs as a Windows 8 app. Learn more about plug-in free browsing from Microsoft"

Is this perhaps why the Inquisit plug in will not run on my PC (which runs windows 8.1)?

Thanks again,

Rebecca 

As the article you linked says,

"Starting with Windows 8, IE is one web platform that provides two browsing experiences: the new IE in the new Windows UI optimized for touch devices, and the traditional browsing experience of Internet Explorer for the desktop."

The "app" version accessible via the Metro UI does not support plugins. The regular version does (which is the one you should use). I am not sure whether this relates to the original problem you described.

As for the instructions not being displayed completely (re. your screenshot), there are a couple of issues:

<instruct>
/ windowsize = (70%, 70%)
/ nextlabel = "Space Bar to Continue"
/ prevlabel = " "
/ wait = 1000
/ font = ("Arial", -30, 700, 0, 34)
/ nextlabel = "Press the <P> key to continue"
/nextkey=("P")
/ prevlabel = "Press the <Q> key to go back"
/prevkey=("Q")
/font = ("Arial", -30, 400, 0, 49)
</instruct>

#1: Note that you have two conflicting /font definitions. Eliminate one.
#2: Use the /fontstyle attribute instead of the legacy /font attribute.
#3: Express the fontsize in screen percentages instead of absolute values. E.g

/ fontstyle = ("Arial", 3%, true)

#4: Consider using the <defaults> elements /canvasaspectratio, /canvassize and /canvasposition attributes to get more consistent results across varying screen resolutions and screen aspect ratios.

Hope this helps.

Thanks Dave,  that will help re the type on the screen.  I didn't realise that I had two definitions  and  I will certainly take on your other suggestions.  Can I ask one more web player question.  I have run it again on my computer using web player and for the AAT task, while I can "push" the images using the mouse easily, when I "pull" the images they often freeze (and the only way I can clear them is to push them).  I have not seen this before when running the script with the usual plug-in, although I have heard of one other person who has had this problem (which I now realise is probably with web player?). Do you know why this is happening?  Do you have any suggestions of how to fix this issue?

Thanks again Dave,

Rebecca 

Frankly that's the 1st time I've heard of this ("pulling" leading to freezing, while "pushing" doesn't) and I have no spontaneous idea as to why that might happen in general or when using the web player specifically.

As for "fixing" it, have you double-checked the respective code to ensure that there isn't any (subtle) mistake in there that may be responsible for this difference in behavior between pushing / pulling?