367690 - clicking on checkbox in applet puts applet in Dock, applet does not accept click

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Ray Kiddy]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1


I am seeing a problem with the behavior of an applet opened within Firefox.

I am using WebObjects from the Xcode 2.1 distro on Mac OS X 10.4.8. The current java on this box is build 1.5.0_06-112.

In WO, you can create a D2W application. This uses a rule-generated user interface. To change the user interface of the web app you produce, you connect to the app you are creating and open an applet and the applet has UI for changing the rules that drive the generation of the UI of the app.

When I click on a checkbox in that applet, it sends the applet window to the Dock, as if I had clicked on the "minimize" button of the window. One can pull the applet window out of the Dock and see that the click was not accepted.

I can connect to the same application with Safari, open the same applet and that applet does not have the problem.


Reproducible: Always

Steps to Reproduce:
I can point to some docs and a demo. Whatever will be helpful.

Comment 1

[Steven Michaud [:smichaud] (Retired)]

Please provide a test case.

Comment 2

[Ray Kiddy]

Do you have a Mac with Xcode? WebObjects is an optional install from the Xcode DVD. In order to reproduce this case, one would need Xcode and WebObjects.

I can try to isolate the applet, but I have not done that before. If you have written up anything about how to pull an applet out of its context, please point me at it. Otherwise, I will have to experiment with it.

Comment 3

[Steven Michaud [:smichaud] (Retired)]

I can install WebObjects easily enough ... but I need a well written
(and commented) test case before I can begin to understand what you're
talking about :-)

(And in general, there isn't much point in reporting a bug without
demonstrating how to reproduce it.)

Comment 4

[Ray Kiddy]

Sure. I did not know how much time you were going to be able to put into this.

FYI, there is a tutorial movie on using WO that covers the EOModeler part of this at: http://ia311541.us.archive.org/1/items/WebObjects_5_in_15_Minutes/wo5in15.mov

To reproduce:

1) create a table in a database. I used MySQL and:
<code>
CREATE TABLE `people` (
  `name` varchar(64) default NULL,
  `people_id` int(11) NOT NULL,
  `email` varchar(64) default NULL,
  PRIMARY KEY  (`people_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
</code>

2) open the project I will attach to this bug (people.tgz).

3) You will need to open the model with EOModeler and put in the correct user name and password for your database. To get EOModeler to open the model, launch EOModeler and use the File->Open menu. Double-clicking on the model in Xcode will get you the wrong interface. To get to the connection info in the model, click on the top icon in the left-hand view of the model and hit the (I) button. The inspector will have a username and password field. Save the model.

4) build and launch the project.

5) click on the 'Enable Assistant' checkbox and click on the Login button.

6) on the next page, click on the 'hour-glass' symbol on the right side of the "People" row.

7) click on the 'Customize' button in the toolbar of the app.

8) click on the "name" row in the "Show:" table in the middle of the applet that comes up. See the screenshot to see how it should look at this point.

9) try to change the value of the pull-down menu on the right side of the applet, for example, to D2WDisplayLargeString.

Instead of taking the change in value, the applet zooms into the Dock.

Many interactions with the applet just send it to the Dock. Also, while I was doing this, Firefox crashed. Tell me if the crash log means anything to you. If not, I will file a separate bug.

Comment 5

[Ray Kiddy]

Attachment: project used in use case

Comment 6

[Ray Kiddy]

Attachment: project used in use case

Comment 7

[Ray Kiddy]

Attachment: log for crash in FF when I was reproducing this

Comment 8

[Ray Kiddy]

sorry for the dupe attachment. Back button is not so smart sometimes, or too smart...

Comment 9

[Steven Michaud [:smichaud] (Retired)]

Thanks for your tests case(s) and detailed description.  It's going to
take me a long time to work through it/them.

But as I skimmed through what you wrote, it struck me that some of the
problems you describe sound like a bug that I fixed in JEP 0.9.6 (item
#13 in the change log posted at bug 364158).

Follow the instructions at bug 364158 comment #0 to replace the JEP
that's bundled with Firefox 2.0.0.1 with JEP 0.9.6, and let me know
your results.

(The crash is (of course) unrelated.  But let me know if you keep
having crashes with JEP 0.9.6.)

Comment 10

[Ray Kiddy]

Attachment: screen shot of app with UI applet

Comment 11

[Ray Kiddy]

Yes, as you guessed, adding the 0.9.6 version of the plugin fixes the problem....

FYI, I noticed that you had some version 49.0 class files in your jars in the plugin, but the classes seemed to be clearly targeted at 1.5 features, so it looks as though you have a handle on the problems that result from trying to get a pre-1.5 JVM to load these class files. Just wanted to mention it, though.

Comment 12

[Steven Michaud [:smichaud] (Retired)]

> so it looks as though you have a handle on the problems that result
> from trying to get a pre-1.5 JVM to load these class files.

Yes.  As you noticed, there are some Java-1.5-specific classfiles that
I compiled using the Java 1.5 javac (and some other
Java-1.4.1-specific files that I compiled using that version's javac).
But all the rest were compiled using the Java 1.4.2 javac.