"webanywhere$ACAhas$ACAloaded" is an invalid sound ID.

[Cameron Wong]

Hi Jeff,

submission r231 might have injected bugs. WA is no longer working. It
keeps complaining "webanywhere$ACAhas$ACAloaded" is an invalid sound
ID.

WA works fine with r230.

Not sure whether you still remember. I have made some change to the
encoding of speech text in r129. Before r129, we use some hash
algorithm that doesn't support unicode. After r129, most short English
string will have a direct mapping. Long sentence will calculate a MD5
value. The final sound name letters are in
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789_$". I
am not sure whether "$" make things broken. But it works well in the
past.

Could you please have a check whether there are some conflicts with
your submission in r231? Thanks!

Cameron

[Cameron Wong]

In wa.js, there are following lines. WA throw error of
"top.web_proxy_url undefined" and it doesn't work any more (it keeps
warning "webanywhere$ACAhas$ACAloaded" is an invalid sound ID). If I
add "top.web_proxy_url" to the first IF statement to avoid entering
the branch when web_proxy_url is undefined, things can run normally
although it still warns "webanywhere$ACAhas$ACAloaded" is an invalid
sound ID once.

I am running WA on localhost. Please confirm that we should add
condition for checking whether top.web_proxy_url is defined. Thanks!

Cameron

===== in wa.js =====
// No need to proxy from our own server;
// can cause problems when running on localhost.
if((rewriteForSure || !sameDomainRegExp.test(loc)) && !(/^\//.test(loc))) {
loc = top.web_proxy_url.replace(/\$url\$/, WA.Utils.Base64.encode64(loc));
if(subdomain && subdomain.length > 0) {
loc = top.webanywhere_location + loc;
loc = loc.replace(top.webanywhere_domain,
(subdomain + '.' + top.webanywhere_domain));
}
}

2009/12/27 Cameron Wong <hgn...@gmail.com>:

[Wendy Chisholm]

Cameron,

I am trying to replicate this issue but have not been able to. You've checked in several changes over the last few days, have you fixed the bug or are you still running into issues?

Thanks,
--wendy

--

You received this message because you are subscribed to the Google Groups "webanywhere-dev" group.
To post to this group, send email to webanyw...@googlegroups.com.
To unsubscribe from this group, send email to webanywhere-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/webanywhere-dev?hl=en.

--
Wendy Chisholm
Web Accessibility Specialist
http://sp1ral.com/about/
http://staff.washington.edu/chiswa/
twitter: wendyabc

[Cameron Wong]

This issue seems disappear after I fix the issue of "Issue 30:
invalid flag after regular expression"
http://code.google.com/p/webanywhere/issues/detail?id=30&can=1

Cameron

2010/1/5 Wendy Chisholm <chishol...@gmail.com>: