This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 248287 - Autocomplete misbehaves when closing HTML tags
Summary: Autocomplete misbehaves when closing HTML tags
Status: RESOLVED WORKSFORME
Alias: None
Product: web
Classification: Unclassified
Component: HTML Editor (show other bugs)
Version: 8.0.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-30 19:59 UTC by velinath
Modified: 2015-08-24 12:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description velinath 2014-10-30 19:59:00 UTC
When trying to close an HTML tag, the autocomplete has the potential to insert an extra closing tag inside the typed text.

Basically, if you type out "</div>", and then press Enter, the expected behaviour would be for the closing tag to show up and then a newline.

Instead, (as shown in screencast here: https://www.youtube.com/watch?v=te95MKBz3uU), the autocompleter inserts its own </div> tag inside the one that was just typed out. This is not a problem with typing too fast; although I was typing fairly quickly in the video, I've verified the bug still exists after waiting up to 5 seconds after typing the close angle bracket before hitting Enter.

Let me know if I can provide any more details.
Comment 1 Milutin Kristofic 2015-08-24 12:27:51 UTC
Hi,
I am sorry I get to your report so late. Can you still reproduce this? What is your netbeans version? Can you describe in more detail steps how to reproduce this. Since I don't know how.

Thanks
Comment 2 velinath 2015-08-24 12:51:05 UTC
Hi Milutin - 

I have changed computers at work since this issue was created, and am unable to reproduce in 8.1 beta which I am using now. I unfortunately can't speak to more than that
Comment 3 Milutin Kristofic 2015-08-24 12:52:18 UTC
Ok, that are good news. If you encounter again this bug, please reopen this issue.