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 128995 - Incorrect "folded" texts
Summary: Incorrect "folded" texts
Status: RESOLVED DUPLICATE of bug 142711
Alias: None
Product: editor
Classification: Unclassified
Component: Code folding (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Svata Dedic
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2008-03-03 12:51 UTC by Jan Lahoda
Modified: 2012-06-07 07:59 UTC (History)
2 users (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 Jan Lahoda 2008-03-03 12:51:17 UTC
[trunk build #20080303072759 from Hudson]

In NB6.0, when the span between starting and ending element was folded (e.g. folding <html>foo-bar</html>), the text
that appeared in the folded box was "<tag>...</tag>" (e.g. "<html>...</html>"). In the aforementioned trunk build, the
box contains "{...}", which seems much less useful and much less appropriate than the 6.0 behavior.
Comment 1 Marek Fukala 2008-03-03 13:32:12 UTC
The HTML, CSS and JavaScript folding is implemented within the GSF framework which doesn't allow me pass the text to the
fold name. The only range of the fold is provided by the fold implementation. Some GSF extension required here.
Comment 2 Petr Jiricka 2009-08-21 14:07:45 UTC
Still reproducible. Has this been addressed on the GSF/CSL side?
Comment 3 Marek Fukala 2009-09-17 14:57:06 UTC
No, passing to CSL
Comment 4 Vitezslav Stejskal 2009-11-11 08:24:00 UTC
StructureScanner.folds only returns type of a fold and its range, but not its description. Currently a generic descriptions is defined for each fold type.
Comment 5 David Strupl 2010-09-28 14:44:48 UTC
I would like to enhance the editor APIs instead of CSL. If it is not relevant/possible please assign back to CSL ... Thanks.
Comment 6 Svata Dedic 2012-06-07 07:59:53 UTC

*** This bug has been marked as a duplicate of bug 142711 ***