0

Running a few canvases which work fine in chrome but fail in the latest version of Mozilla. I know this was an issue a while back and I thought the new processing-1.4.1.js was fixed to accommodate for the for loop failure seen here. Does anyone know if they did or if not, why this is happening and how to fix it?

edit:

Test code that will not work:

void setup() {
String names[] = {"Alexis", "Thomas", "Antoine"};
   for(String name : names) {
     alert(name);  // doesn't on Firefox 17+, bug?
   }
}

void draw() {
}
ZekeDroid
  • 7,089
  • 5
  • 33
  • 59
  • were you going to add any code to illustrate what generated the error? because without that it's unlikely anyone can reproduce the error. – Mike 'Pomax' Kamermans Aug 24 '13 at 20:31
  • well it's a pretty common error in foreach loops but sure, this is some test code that will not work: void setup() { String names[] = {"a", "b", "c"}; for(String name : names) { alert(name); // doesn't on Firefox 17+, bug? } } void draw() { } – ZekeDroid Aug 27 '13 at 17:36

1 Answers1

0

This is a problem with Processing.js and some recent changes in Firefox as discussed here.

You have two options: Solution 1 is to hack Processing.js file as discussed by alexbbrown in the aforementioned link (a harsh and nasty solution), essentially finding the actual Processing.js file, editing it with your favourite text editor and change lines 291-292 from:

if (obj.iterator instanceof
Function) return obj.iterator();

to:

if (obj.iterator instanceof Function && obj.hasNext instanceof Function)
return obj.iterator();

Solution 2 is to change your code and live without the lovely for-each syntax (a softer, compromising solution), replacing the lines:

for (String name : names) {
  alert(name);  // doesn't on Firefox 17+, bug?
}

with the common for syntax:

for (int i = 0; i < names.length; i++) {
  alert(names[i]);
}

whatever you do, may the for be with you...

Petros Koutsolampros
  • 2,790
  • 1
  • 14
  • 20
  • ok thanks. I was just wondering if they had updated this in the newer processing.js versions but I guess they haven't yet. – ZekeDroid Sep 01 '13 at 23:01