JDK-4456754 : Scroll buttons of JTabbedPane are not working in consistent manner
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.4.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2001-05-10
  • Updated: 2001-07-12
  • Resolved: 2001-07-11
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.
Other
1.4.0 beta2Fixed
Related Reports
Duplicate :  
JDK-4479158 - Scrollable tab buttons of JTabbedPane don't work for special size of TabbedPane
Description
Scroll buttons in JTabbedPane with SCROLL_TAB_LAYOUT policy are behaving
inconsistently with the attached code on both Solaris & Windows platforms.

To reproduce the above problem:

1. Compile & Execute the attached code.
2. Scroll towards right by pressing RIGHT scroll button till it gets disabled.
3. Then again start scrolling towards left. It won't scroll.

This is happening only with the launched JFrame size. If you decrease the
size of the JFrame a bit, before executing the test instructions, and then
test it, it is working fine.

I traced back with the old builds. It is working fine with builds before b52.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta2 FIXED IN: merlin-beta2 INTEGRATED IN: merlin-beta2 VERIFIED IN: merlin-beta2
14-06-2004
PUBLIC COMMENTS Verified with Build 1.4.0-beta_refresh-b71. No longer a bug.
10-06-2004
EVALUATION Should be fixed for FCS. scott.violet@eng 2001-05-10 JViewport will potentially notify its changelinsteners a number of times. This is throwing off BasicTabbedPaneUI as it will only reset leadingTabIndex to 0 if the new location is 0. If in setting the first location a change notification is sent out the ChangeListener resets the leadingTabIndex to 0, the index will subsequently not be adjusted and it is confused. The fix is to always adjust the leadingTabIndex in the change notification. scott.violet@eng 2001-06-22
22-06-2001