PR# 16862 Tooltip on feature declaration don't go away

Problem Report Summary
Submitter: manus_eiffel
Category: EiffelStudio
Priority: High
Date: 2010/06/17
Class: Bug
Severity: Critical
Number: 16862
Release: 6.6.8.3602
Confidential: No
Status: Closed
Responsible: larryl
Environment: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.70 Safari/533.4
Synopsis: Tooltip on feature declaration don't go away

Description
When you are in the editor and you are over the name of a feature, a small white (with blue border) rectangle appears and if you move your cursor on it, a tooltip showing the contract will appear.

In previous releases (possibly not 6.5 or 6.4) clicking on the editor made that thing go away, no it doesn't. At least on Windows. On Linux I'm not sure if it doesn't just go in the back instead.

Larry can you look at the Windows issue and see what is going on?

Thanks,
Manu
To Reproduce

										

									

								

							

						

					

				

			

		

	









	

		

			
Problem Report Interactions

			

				

					
					

						

							
							

								

									
									
										

											

									
											From:larryl   
											Date:2010/06/21   
																							Status: Closed   
											
											Download   
										

										

                                            
											
										 	
It doesn't work, because in previous releases, it will get keyboard focus (steal focus?) when the pop-up tooltip appears. In 6.6, it will not get keyboard focus just after shown, so focus out actions (to close the pop-up tooltip window) will not executed if you clicked on the editor. If you first click on the pop-up tooltip (to give it focus), then click on the editor, it will disappear.

In revision#83652, the pop-up tooltip will be closed just after user pointer leave the pop-up tooltip window area. Personally, I think this is better than clicking on the editor to make it go away. Close the bug report now.

If you don't like the solution, please reopen the bug.

Thanks for your report.