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 234820 - With dark theme, tabs are inconsistently colored
Summary: With dark theme, tabs are inconsistently colored
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 7.4
Hardware: All All
: P4 normal with 2 votes (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords: NO74
Depends on:
Blocks:
 
Reported: 2013-08-22 18:31 UTC by twolf2919
Modified: 2014-12-09 20:16 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Shows the issue (68.16 KB, image/png)
2013-08-22 18:36 UTC, markiewb 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description twolf2919 2013-08-22 18:31:29 UTC 
The editor's tabbed pane and most other windows' tabbed panes show the active tab highlighted.  But there are some which do the reverse: they highlight the inactive tabs and leave the active tab unhighlighted.  The examples I found are:

- All the tabbed panes under Tools/Preferences
- The Output Window's tabs
- The HTTP Server Monitor's tabs

There might be others, but at least these should be fixed.
Comment 1 markiewb 2013-08-22 18:36:38 UTC 
Created attachment 139089 [details]
Shows the issue

Added the screenshot from the mailing list which shows the issue
Comment 2 Marian Mirilovic 2013-08-23 13:53:14 UTC 
Dark themes were moved to the NetBeans Update Center for NB 7.4
Comment 3 twolf2919 2013-08-23 14:02:12 UTC 
Marian, how does this affect this bug?
(In reply to Marian Mirilovic from comment #2)
> Dark themes were moved to the NetBeans Update Center for NB 7.4
Comment 4 lkishalmi 2014-11-02 11:16:02 UTC 
This issue seems to be fixed somewhere between 7.4 and 8.0.1, at least I could not see this kind of visual inconsistency, neither with dark metal nor with dark nimbus.
Comment 5 eda 2014-12-09 18:02:11 UTC 
Verfied to still have this fault in Dark LAF 1.0.2 with NB 8.0.1, RCP 1.26.1 .
I tested on GNU+Linux, so I'm changing platform to all hardware & OSes.

I checked the following and see they are still shown with the selected tab as dark whereas other tabs I see the selected tabs are light.

- Tools --> Options
- Output tabs
Comment 6 markiewb 2014-12-09 20:14:34 UTC 
(In reply to eda from comment #5)
> Verfied to still have this fault in Dark LAF 1.0.2 with NB 8.0.1, RCP 1.26.1
> .
> I tested on GNU+Linux, so I'm changing platform to all hardware & OSes.
> 
> I checked the following and see they are still shown with the selected tab
> as dark whereas other tabs I see the selected tabs are light.
> 
> - Tools --> Options
> - Output tabs

@eda: Please do not reopen fixed issues. It is unlikely that they will be fixed this way. Please file a new issue and add a link this one.

Also do NOT (never) change the target milestone. That is not a wish property for the reporter, it is used by the NB developers to show in which version the issue has been fixed.

I will reset the original target milestone to 7.4 and mark the issue as fixed.
Comment 7 markiewb 2014-12-09 20:16:14 UTC 
(In reply to markiewb from comment #6)
> (In reply to eda from comment #5)
> > Verfied to still have this fault in Dark LAF 1.0.2 with NB 8.0.1, RCP 1.26.1
> > .
> > I tested on GNU+Linux, so I'm changing platform to all hardware & OSes.
> > 
> > I checked the following and see they are still shown with the selected tab
> > as dark whereas other tabs I see the selected tabs are light.
> > 
> > - Tools --> Options
> > - Output tabs
> 
> @eda: Please do not reopen fixed issues. It is unlikely that they will be
> fixed this way. Please file a new issue and add a link this one.
> 
> Also do NOT (never) change the target milestone. That is not a wish property
> for the reporter, it is used by the NB developers to show in which version
> the issue has been fixed.
> 
FYI: Same for version. This shows where the issue first occurred. So do not change it