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 262550 - Visual ordering of compiler errors leads to usability problems
Summary: Visual ordering of compiler errors leads to usability problems
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Editor (show other bugs)
Version: 8.2
Hardware: All All
: P3 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-23 15:24 UTC by _ gtzabari
Modified: 2016-06-27 11:33 UTC (History)
0 users

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 _ gtzabari 2016-06-23 15:24:39 UTC
As we all know, when javac prints out errors to the console, earlier errors tend to be a lot more accurate than later errors.

The problem is that console error ordering does not always correspond to the visual ordering in the source-code. For example, given:

  Collector.of(supplier, accumulator, combiner);

sometimes the first compiler error spans "supplier", the second error spans "Collector.of()", the third one spans "accumulator" and so on.

Visually-speaking, when users see error annotations they typically hover over the top-left most position and (as a result) see the wrong (not the first) error message.

See #262359 for a concrete example where the second error message is terribly incorrect but visually-speaking the first error annotation points to this error.

I don't have any suggestions for how to improve this situation, but I'm hoping that you might.