Bug 142375 - you're so fast to say Resolved!!! when it is no solved: we need to take marked well noted the active tab in calc
Summary: you're so fast to say Resolved!!! when it is no solved: we need to take marke...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-19 11:05 UTC by jazei-AR
Modified: 2021-05-19 11:35 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
a miss of tabs (43.82 KB, image/png)
2021-05-19 11:06 UTC, jazei-AR 		Details
suggestion mode of colored active tab (40.30 KB, image/png)
2021-05-19 11:07 UTC, jazei-AR 		Details
View All 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 jazei-AR 2021-05-19 11:05:13 UTC 
Description:
the actived tab is not marked we can not see witch is the active tab when all tabs are in white color
don't be so fast to say resoved when it is not solved, read and think before say resolved!!!!!

Actual Results:
screenshot 1 attached https://imgbox.com/kz85ogkS


Expected Results:
screenshot 2 attached https://imgbox.com/Mwl9Nmoo


Reproducible: Always


User Profile Reset: No



Additional Info:
resalt active tab with a colored line upper the active tab
Comment 1 jazei-AR 2021-05-19 11:06:16 UTC 
Created attachment 172171 [details]
a miss of tabs
Comment 2 jazei-AR 2021-05-19 11:07:12 UTC 
Created attachment 172172 [details]
suggestion mode of colored active tab
Comment 3 Mike Kaganski 2021-05-19 11:35:27 UTC 
This refers to tdf#142193, which was in turn marked a duplicate of resolved tdf#141396.

Commit Notification from bug 141396 comment #10:
> ...
> It will be available in 7.2.0.

That bug also has this in its whiteboard: "target:7.2.0".

So have you tested if this is *not* fixed in upcoming version 7.2? You didn't provide any version info. This bug is clearly invalid; if you see that 7.2 has not solved this problem, please comment there with steps to repro in 7.2.