JDK-6423287 : PargraphView returns wrong minimum span
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 6,6u1
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2006-05-09
  • Updated: 2017-05-16
  • Resolved: 2011-07-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7 Other
7 b20Fixed OpenJDK6Fixed
Related Reports
Duplicate :  
JDK-6559929 - JEditorPane within a JScrollPane can throw Swing into an infinite loop
Relates :  
JDK-6978666 - closed/javax/swing/text/html/TableView/4813831/bug4813831.java failed
Relates :  
JDK-6751407 - GlyphView.getMinimumSpan return value is not the minimum span
Relates :  
JDK-6612541 - api/javax_swing/text/LabelView/index.html#getXXX[LabelView0004] fails since JDK 7 b20
Relates :  
JDK-6306218 - JEditorPane is unable to do reasonably spaced indentation in complex HTML tables
Relates :  
JDK-6539700 - JTextPane line wrap radically different from previous versions in jre 1.5.0_10+
Description
Note: this is not a regression. 
PargraphView minimum span returns maximum of minimum spans for the views it contains.
That is wrong since we not necessarily break rows on the View boundaries.
For example :
<b>bold</b><i>italic</i>
The minimum width for this should be the width of 
<b>bold</b><i>italic</i> but not the 
max(width(<b>bold</b>), width(<i>italic</i>))
Comments
EVALUATION Sergey moved this bug from Fix Deliveried to Fix failed because of: "The fix, as delivered into 7b20, is invalid. It contains a logical mistake (see 6751407) and caused regressions (see 6612541 and 6539700). The fix should be re-done concerning all the details." All three CRs (6751407, 6612541 and 6539700) mentioned above is closed, therefore I'm moving this CR back to Fix Delivered
22-04-2011
EVALUATION The fix, as delivered into 7b20, is invalid. It contains a logical mistake (see 6751407) and caused regressions (see 6612541 and 6539700). The fix should be re-done concerning all the details.
16-07-2009
SUGGESTED FIX Webrev NFS: /net/sa.sfbay/export/home/swing/data/7/6423287 Webrev URL: http://sa.sfbay.sun.com/projects/swing_data/7/6423287.4
30-07-2007
EVALUATION calculateMinorAxisRequirements in ParagraphView doesn't take into account adjacent views without break possibility between them, like this: F<b>O</b>O This makes three views. The total minimum span requirements for the above is the sum of minimum requirements of all three, but currently ParagraphView returns maximum value of the three as total minimum requirements, which is incorrect.
30-05-2006