Consider compiling your application with style=PRETTY or DETAILED so you can see more detail on the name of methods and the classes that surround the code you have questions about, it can make it easier to hunt these down.
I pretty-printed the code snippet you shared, which results in this:
{
j = k.substring(Z, m);
l = k.substring(m + $)
} else {
j = k;
l = fb
}
c[j] = l
}
}
else if (j == xb) {
k = i.getAttribute(vb);
if (k) {
try {
d = eval(k)
} catch (a) {
alert(yb + k + zb)
}
}
} else if (j == Ab) {
k = i.getAttribute(vb);
if (k) {
try {
e = eval(k)
} catch (a) {
alert(yb + k + Bb)
}
}
}
}
}
__gwt_getMetaProperty = function(a) {
var b = c[a];
return b == null ? null : b
};
The catch blocks have an alert in them, not something we typically see in GWT. It turns out this is part of the default linker, what looks like an old workaround to support extra meta tags contributing error handling code.
if (eq >= 0) {
name = content.substring(0, eq);
value = content.substring(eq + 1);
} else {
name = content;
value = '';
}
metaProps[name] = value;
}
} else if (name == 'gwt:onPropertyErrorFn') {
content = meta.getAttribute('content');
if (content) {
try {
propertyErrorFunc = eval(content);
} catch (e) {
alert('Bad handler \"' + content +
'\" for \"gwt:onPropertyErrorFn\"');
}
}
} else if (name == 'gwt:onLoadErrorFn') {
content = meta.getAttribute('content');
if (content) {
try {
onLoadErrorFunc = eval(content);
} catch (e) {
alert('Bad handler \"' + content + '\" for \"gwt:onLoadErrorFn\"');
}
}
}
}
}
// Set some of the variables in the main script
__gwt_getMetaProperty = function(name) {
var value = metaProps[name];
return (value == null) ? null : value;
}
This is used by most of the built-in linkers - there is an alternative file, processMetasNull.js, which could be used to remove these entirely. To use that, extend your current linker (presumably CrossSiteIframeLinker) and override getJsProcessMetas to return "com/google/gwt/core/ext/linker/impl/processMetasNull.js".