[Mork]

Dear Support,

I spent several hours recently trying to help you wth a serious bug with the JSP designer. Unfortunately, it’s still not fixed in 4.0.2.

I described the problem in detail and posted some code on this forum (but not the entire JSP page since it’s proprietary).

Basically, I have an HTML table on a JSP page. The table has two columns. The first colum is just text. The second column is either a textbox, radio control, or a combo box.

When I delete any row of the table and MyEcliipse’s JSP designer goes nuts “pruning…”, etc, MyEclipse turns all my combos into edit boxes. To make matters worse, they’re fully expanded and all selected (Ctrl-A).

To delete a row, I right click on it in the JSP Designer and click “Delete row”.

Therefore, I’ve had to revert to Dreamweaver for any visual JSP page development.

I posted a “before” and “after” picture of one of the tags affected (before–combo box (correct)), after (edit box (bug!!!)).

I’ll try to help if possible, but I’m not sure what more I can do…

— M

[Scott Anderson]

M,

I spent several hours recently trying to help you wth a serious bug with the JSP designer.
I described the problem in detail and posted some code on this forum (but not the entire JSP page since it’s proprietary).

I assume you’re referring to this thread: https://www.genuitec.com/forums/topic/eclipse-4-0-1-jsp-designer-question/&highlight=
And we thank you very much for the time and the assistance. We’ve created a bug report and it is being worked in development right now.

Unfortunately, it’s still not fixed in 4.0.2.

No it is not as the cause and proper solution is still being researched. 4.0.2 was released only because there was a pervasive bug with the handling of javascript by the designer that affected all pages. That was the only change from 4.0.1 since we didn’t have time for additional development or a full QA cycle to get that fix out. Your bug has been targeted at the next scheduled release, so it is certainly being treated as high priority.

Therefore, I’ve had to revert to Dreamweaver for any visual JSP page development.

I checked the bug report to see if there was a workaround posted by the dev team. It looks like this issue seems to have a workaround by explicitly setting the “size” attribute of the SELECT tag. This will force the display to be explicitly what you want rather than relying on implicit behavior, which is not mandated in the W3C spec. For example:

<!-- Dropdown listbox box -->
<SELECT name="combobox1" multiple="false" size="1">

<!-- Expanded list box -->
<SELECT name="combobox1" multiple="false" size="4">

I’ll try to help if possible, but I’m not sure what more I can do…

You’ve helped greatly and we really do appreciate it as it will enable us to fix this bug for the next release. All we ask is that you give us a little time to work on it since we only found out about it a week ago. 🙂

[Mork]

Thanks Scott for your reply. <s>

— M

[Author]

Posts