Do I need to escape the semi-colon?

Well, I went back to my original code and found nothing wrong there. So I tested the simple code again, this time using simpler coding. See below.

The page has 2 buttons and 4 Text fields. The black words are the names of the text field alias’s. Inside the code below I provided the Text field data for each f the 4 text boxes. Notice the only difference between the first 2 and the second 2 is the use of "; " or "… ".

The idea here is to start Site Monitoring, start up the “live” page, then click Button 1. Site Monitoring reveals an error message and no output logs. Then click Button 2. Site Monitoring reveals the two expected console logs and no error. Something is wrong…what is it?

$w . onReady ( function () {
});

// sku: 8040.725.004; price: $290.00; Carlson Label Fiberglass Tripod…
// sku: 8040.725.002; price: $130.00; Carlson Label Fiberglass Tripod…

// sku: 8040.725.004… price: $290.00… Carlson Label Fiberglass Tripod…
// sku: 8040.725.002… price: $130.00… Carlson Label Fiberglass Tripod…

export function button1_click ( event ) {
let element0 = $w ( ‘#instrumentAccessoryText0’ ). text
let element1 = $w ( ‘#instrumentAccessoryText1’ ). text
console . log ( "element 0 = " , element0 )
console . log ( "element 1 = " , element1 )
}

export function button2_click ( event ) {
let element10 = $w ( ‘#instrumentAccessoryText10’ ). text
let element11 = $w ( ‘#instrumentAccessoryText11’ ). text
console . log ( "element 10 = " , element10 )
console . log ( "element 11 = " , element11 )
}

Thanks for the simple example.

I created a super minimal example:

Clicking Button2 works just fine.
Clicking Button1 causes the error.
This doesn’t even need the console.log() statements for the error to occur. Just getting the string from the Text Element is enough to cause the error. Also, this shows up in the Browser console log as well as the Site Monitoring log.

I have passed this on to QA for evaluation.

@yisrael-wix i can see you have verified the problem. thank you.

Just got word from the devs that this issue has been fixed. Please give it a another shot and let me know how it goes.

I reran my test code and that worked. I am pretty sure it will work in my original code. Thanks for the heads up.