Opened 13 years ago

Closed 9 years ago

#8398 closed defect (wontfix)

Dijit Tooltip Conflicts with Advanced TinyMCE Editor (IE7)

Reported by: rlally Owned by:
Priority: high Milestone: future
Component: Dijit Version: 1.2.3
Keywords: Cc: [email protected]
Blocked By: Blocking:


In IE7, when there is an active scrollbar in the advanced TinyMCE editor, the scrollbar will become unstable after a dijit tooltip is displayed on the page (I am using TinyMCE and Dojo 1.1.1). Cannot reproduce in Firefox or 3.0.5).

To recreate this issue:

  1. Put a dijit tooltip on a page (or use a ValidationTextBox?) with the advanced TinyMCE editor:
<script type="text/javascript" src="path/to/js/dojo/dijit/form/ValidationTextBox.js"></script>
<script type="text/javascript" src="path/to/js/tiny_mce/tiny_mce.js"></script>
<label for="feedback_email">Email address for feedback *</label>
<input type="text" name="feedback_email" id="feedback_email"
	invalidMessage="Please enter a valid email address."
	value="" />


<script type="text/javascript">
	mode : "textareas",
	theme : "advanced"

<form method="post" action="somepage">
	<textarea name="content" style="width:100%">
  1. In Internet Explorer 7, enter enough text into the TinyMCE editor to display the vertical scrollbar. Keep your cursor at the bottom of the text area, so that the scrollbar is also at the bottom.
  1. Activate (display) the tooltip, then deactivate (hide) the tooltip.
  1. Once the tooltip is no longer visible, mouseover the TinyMCE editor - when the mouse pointer leaves the editable area, the scrollbar jumps around erratically, stopping at the top when you stop moving your mouse (even though the cursor itself is still at the bottom of the text area, unseen).

Change History (2)

comment:1 Changed 13 years ago by bill

Milestone: tbdfuture

comment:2 Changed 9 years ago by bill

Resolution: wontfix
Status: newclosed
Summary: Dijit Tooltip Conflicts with Advanced TinyMCE EditorDijit Tooltip Conflicts with Advanced TinyMCE Editor (IE7)

Probably we'll desupport IE7 before getting around to fixing this.

Note: See TracTickets for help on using tickets.