#709 closed defect (duplicate)
dj_eval b0rken for JSON response evaluation
| Reported by: | Owned by: | anonymous | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Core | Version: | 0.3 |
| Keywords: | 710 | Cc: | |
| Blocked By: | Blocking: |
Description
For a particular JSON response (something like {name:value, name:value, name:value} ) , the dj_eval global evaluation of the content using dj_eval("(" + text + ")") is causing problems because dj_global is pointing to the "window" object instead of the "document" object that correctly handles eval() in this instance.
I've tested and dj_global definitely is the window, which does have an eval() function, but for some reason the document object eval() function is the only one that actually works.
This could be a FF bug, hard to tell what changed as the changelog in dojo doesn't suggest anything new..(maybe it's a side effect happening somewhere else). My FF version is 1.5.0.3 on ubuntu linux.
Also noticed that the only way to get ComboBox? found was by including it in the packaged dojo.js file. (tag not found). I've debugged and verified that it's correctly calling and recieving the ComboBox? sources via xmlhttp, so I think this is a global evaluation bug in general.
Change History (4)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Nevermind my suggestion that this has something to do with not recognizing tag handlers, that problem is related to http://trac.dojotoolkit.org/ticket/710. The window.eval() of JSON responses is still a bug though.
comment:3 Changed 14 years ago by
| Keywords: | 710 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
This actually was all completely related to 710. After chaning that everything seems a-ok. Sorry for the extra noise.
I should note that this is based off of a built dojo build (using most current revision as of a few minutes ago ), with dojo.js being loaded into the head of the document.