- System Setup -------------------------------

Operating System and version: Mac OS X 10.4.2 and Windows XP SP2
Eclipse version: 3.1
Eclipse build id: I20050627-1435
Fresh Eclipse install (y/n): y
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 4.0.0 GA
Eclipse JDK version: Apple 1.5.0_02 on Mac and Sun 1.5.0_04 on Windows


- Message Body -------------------------------

I've noticed in the HTML and JSP editors that the auto-close feature for HTML tags seems to get confused at times. Normally it works flawlessly, automatically inserting the appropriate end tag once </ is entered. Sometimes, however, when you move inside nested tags you'll get the wrong closing tag. For instance, if I have the following code:

Code:

<ul>     <li></li> </ul>

And I begin typing the following inside the <li> tags:

Code:

<a href="whatever.html">My Link Here</

I expect the closing </a> tag to be inserted, but I get </ul> instead. Can anyone else confirm this bug?

- Erik Mattheis

BTW: On an unrelated note, the preview button on the forum takes me back to the homepage for some reason...

Erik,

We have noticed this issue. In the next release, the auto-closing feature will be changed to just auto-suggesting so it doesn't actually automatically force the tag closed.

Quote:

BTW: On an unrelated note, the preview button on the forum takes me back to the homepage for some reason...

If you first click "Post Reply" and then use the Preview button on this page, it should work fine.

Hmmm...not much of a fix :?

I'd rather have the feature how it is now than lose it altogether. Interestingly enough, the suggestion panel that pops up seems to suggest the correct closing tag.

I noticed in the release notes for 4.0.1 it mentions that the behavior was changed back to suggest instead of complete. I'd like to voice my disapproval of this again. I think it's pretty poor to remove a feature because you couldn't make it work properly. Even thought the implementation was partially broken, it was still a big time-saver for me! Are there plans to re-incorporate this feature in the future? At least provide a checkbox to enable/disable it if it still causes trouble.

- Erik Mattheis

Erik,
Sorry this caused a problem for you, the reason for this is because with MyEclipse 5.0 we are doing a refresh of ALL the editors code bases against the most recent WTP release so there is going to be quite a bit that may change. This is just a temporary "better it be simpler and work until we revamp the editors, than burn up a week in the parsing code so we can just replace it in 2 months" issue.

Understood. Here's hoping it makes it back in eventually ;)

- Erik Mattheis