In older builds, I'm sure we had some CSS that specified that the cursor should be an I-beam when you hovered over any part of the contents of the mail compose or composer window (or a text field, or textarea). But at some point that changed. Now, I get the arrow cursor when hovering over composer content that is not a text frame. This is confusing, and wrong.

cc: tucson

No we never had I-Beam over the entire content area in any 6.x or 4.x version. And neither does Word or Word Perfect. When cursor is not over text, like an image, it makes sense to use an arrow cursor to indicate that when you click on an object, it will select it. Any other opinions before I mark this invalid?

I agree with the arrow over images and other objects, but I think an I-beam over the rest of the content makes sense. Every other Mac word processor acts this way. Maybe this needs to be platform-specific?

If this doesn't bother any Windows or Linux users, I'm ok with using I-Beam text cursor over entire content area. Not worth the hassle for OS-subversions.

I checked some linux editors: xemacs, gedit, kedit and kword all use an I-beam over the entire content area. gvim is the only dissenter, with an arrow everywhere. So Linux people would generally expect the same as mac, I-beam over text and blank areas (I suspect that other word processors like abiword and staroffice also follow that convention).

Comment on attachment 72426 [details] [diff] [review] Fix. r=brade

Comment on attachment 72426 [details] [diff] [review] Fix. sr=sfraser

Comment on attachment 72426 [details] [diff] [review] Fix. a=asa (on behalf of drivers) for checkin to the 1.0 trunk

checked in

Verified on Win XP using the 04-30 trunk build. Marking VERIFIED.