I tried it in windows with Chrome Beta 4.0.249.64 and works for me. It doesn't show any error and shows the number '4' instead.
On Sat, Jan 16, 2010 at 5:36 PM, Aaron Boodman <a...@google.com> wrote: > On Sat, Jan 16, 2010 at 4:56 PM, Aaron Boodman <a...@google.com> wrote: >> On Fri, Jan 15, 2010 at 6:17 PM, Michael <gundl...@gmail.com> wrote: >>> Content scripts share a global namespace, so that document_start >>> scripts can define a global variable that document_end scripts can >>> access. >>> >>> Except at http://wonderwall.msn.com (with Chrome Beta 4.0.249.64) when >>> all_frames=true for both content scripts, this doesn't work. The >>> document_end script doesn't see the variable defined at >>> document_start. >>> >>> Which behavior is the bug? >> >> All content scripts for the same extension/page pair should share a >> context. If you aren't seeing this, it is a bug. I'll investigate. > > I don't see this bug on mac beta 4.0.249.30. It's certainly possible > it is windows specific, but I don't have access to a Windows machine > until Tuesday. I'll try and reproduce it then. > > - a > > -- > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
