> maybe the site has a library that mucks around with createElement
A really good guess. I hadn't thought of that.
Snag the old function, put yours in its place, and call the old one on
traditional arguments.
So I gathered all the javascript from oranges.com, deminimized, and grepped for
createElement.
document.createElement is never assigned anything. The site does not overload
it.
It is, I assume, the base browser function.
We could test this by writing a little script and letting other browsers
process it. What do they do?
Here are the unusual calls from oranges.com.
'<a></a>'
'<div class=\'' + j + '\' data-action=\'' + e + '\' data-send=\'false\'
data-layout=\'' + g + '\' data-show-faces=\'false\' data-href=\'' + c +
'\'></div>'
'<div class=\'' + j + '\' data-href=\'' + c + '\'></div>'
'<div></div>'
'<iframe name="' + e + '" ></iframe>'
'<iframe name="stLframe" allowTransparency="true"
style="body{background:transparent;}" ></iframe>'
'<iframe name="stframe" allowTransparency="true" scrolling="no"
frameBorder="0"></iframe>'
'<iframe></iframe>'
'<img></img>'
'<span></span>'
'g:plus'
'g:plusone'
Karl Dahlke
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
