I suspect that fact that we must eval it is the problem... I'll try to isolate it and submit a chrome bug..