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 65656 - [50cat] error_stripe doesn't display red box or annotations when xml is wrong
Summary: [50cat] error_stripe doesn't display red box or annotations when xml is wrong
Status: NEW
Alias: None
Product: xml
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@xml
URL:
Keywords:
: 66193 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-10-03 03:36 UTC by claudio4j
Modified: 2007-02-16 14:48 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description claudio4j 2005-10-03 03:36:52 UTC
[ BUILD # : beta 1 ]
[ JDK VERSION : 1.6 ]

The test, 

1) open any well formed xml document
2) change anything to break the parsin (eg: remove a close tag)
3) error stripe shows a gray box, only 

 Error stripe should:
a) print the red box 
b) an annotation to warn the user
c) when pass the mouse pointer over the red box displays the number of errors
Comment 1 claudio4j 2005-10-03 03:38:36 UTC
Another related thing: when the xml document is well formed and parseable, the
green box is not displayed.
Comment 2 Jan Lahoda 2005-10-07 07:29:53 UTC
This is not an error stripe problem. The errorstripe only shows annotations that
are already shown in the editor. The XML editor does not provide an
online-checker, and so the error stripe has no data to show.

BTW: there is an experimental version of such a checker in contrib/editorhints/xml.
Comment 3 Petr Jiricka 2005-10-10 15:55:35 UTC
Yes, this is not supported for XML, so reclassifying as enhancement.

The question is, whether the error stripe should be displayed at all, and what
code is responsible for displaying it? Honzo, should not it be hidden for XML?
Comment 4 Jan Lahoda 2005-10-10 16:11:55 UTC
From the technical point of view, it is possible to show the error stripe only
for specific mime types. This was discussed in issue #61235, and the final
decision (mine) was to leave the error stripe in all editors and only change the
"global status" to gray if the global status is not usefull.

The reason is that the error stripe may show bookmarks which are usefull for
nearly all mime types.

But, if you think it would be better to disable ES in the unsupported mime
types, please reopen issue #61235 so we can discuss it. We can disable it for
general XML and enable for ant scripts (to get breakpoints), etc.
Comment 5 Marek Fukala 2005-10-11 08:18:09 UTC
*** Issue 66193 has been marked as a duplicate of this issue. ***
Comment 6 Jaroslav Pospisil 2006-03-13 13:35:24 UTC
TM 5.0->TBD
Comment 7 Marek Fukala 2007-02-16 14:48:27 UTC
Reassigning to default owner of selected subcomponent. New owners are gladly
welcomed.