[Resolved] Firefox 19, Noscript, and Gmail's new compose

[rcrumbb]

I am using Windows 7 Ultimate 64-bit SP1, Firefox 19, and Noscript 2.6.5.8rc2.

I am trying to use the new Gmail compose. After clicking on "Compose", a blank email form appears in the bottom right corner of the screen on top of the existing page contents (the old compose simply took the user to a new page containing the blank email form). I can click in the "To" section to place the cursor there and begin typing, and I can do the same with the "Subject" section. However, I cannot place the cursor in the large section where the email message would be typed. Clicking in that message area takes the cursor away from the "Subject" section but nothing at all happens when I begin to type. Choosing the NoScript option of "Allow Scripts Globally" makes no difference to my problem. I tried resetting NoScript back to default, clearing all cookies, and disabling all addons except for NoScript. Still my problem remains. However, disabling NoScript solved the problem but that is hardly a solution.

I don't know why this problem exists, nor do I know how to solve it within the NoScript settings. Any suggestions would be extremely welcome, and I thank you for your time and courtesy.

[therube]

I see a "pop-out" arrow (next to the minimize & close button).
From there you can open pretty much fullscreen if you wanted.

(Now let me turn of JavaScript & rid myself of that "stuff".)

(I'm still on 2.6.5.7rc1 if that matters?)

[rcrumbb]

From there you can open pretty much fullscreen if you wanted.

Clicking that arrow makes the form change from an overlay and makes it pop into its own window, and then I can click the message area to set the cursor there and begin typing. So that works.

But that doesn't exactly solve the problem. Something about NoScript is blocking the cursor from being set in the message area of that overlay. The overlay functions perfectly when I disable NoScript. I'm wondering if this problem is bug-related or settings-related because I'd really love to know how to resolve it if a problem like this comes up again on another website.

[Giorgio Maone]

It has been fixed yesterday in latest development build 2.6.5.8rc3.
Sorry it didn't get in autoupdate until now, though.

[therube]

Fixed, thanks.