Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#13558 closed defect (fixed)

Dijit Textarea - possible defect

Reported by: alanwhurt Owned by: Douglas Hays
Priority: high Milestone: 1.7
Component: Dijit - Form Version: 1.6.1
Keywords: textarea Cc: alanwhurt@…
Blocked By: Blocking:

Description

Using IE7 (version 7.0.5730.13), I am seeing the following behavior with dijit textarea

With a dijit textarea with a lot of content, scrolling down to any arbitrary point of the textarea and clicking to place cursor, the the top of the textarea seems to try to scroll back into view and the point at which I clicked (in the textarea) does not have the cursor as I would expect. Scrolling back down the textarea and clicking again does the same thing.

This can be demonstrated by loading the Dijit themetester at http://download.dojotoolkit.org/release-1.6.1/dojo-release-1.6.1/dijit/themes/themeTester.html and switch to the Textarea tab. Copy and paste the content of the textarea several times and then scroll to the bottom of the textarea and click (or try to select text). The textarea scrolls the first line of the textarea into view and I don't actually have the cursor where I originally clicked.

Additional info - tried setting the scrollOnFocus=false which results in the textarea scrolling into view briefly and then jumping back to where cursor should be. This helps mitigate the issue of losing where cursor was inserted, but still makes it very difficult to select text for example.

Contact: alanwhurt@… if needed

Change History (3)

comment:1 Changed 8 years ago by bill

Component: DijitDijit - Form
Owner: set to Douglas Hays

comment:2 Changed 8 years ago by Douglas Hays

Milestone: tbd1.7
Resolution: fixed
Status: newclosed

(In [25997]) Fixes #13558. Don't process mouse->widget focus events if the widget is already focused to prevent erratic browser scrolling behavior (IE). Refs [21299].

comment:3 Changed 8 years ago by Douglas Hays

In [26192]:

Refs #13558. Only test for this.focused in IE since other browsers (FF) need help focusing child elements with onmousedown events, and they don't scroll the element to the top after a programmatic focus.

Note: See TracTickets for help on using tickets.