Bug 209346 – Web Inspector: REGRESSION(r257835): close and undock buttons are shown in remote inspector

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector

[Devin Rousso]

# STEPS TO REPRODUCE:
1. connect an external device or open an iOS simulator
2. inspect anything

[Devin Rousso]

Created attachment 394097 [details]
Patch

[Blaze Burg]

Comment on attachment 394097 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=394097&action=review

r=me

> Source/WebInspectorUI/UserInterface/Base/Main.js:900
> +    WI.tabBar.resetCachedWidths();

How does the tabBar invalidate cached widths when the inspector window / view is resized? Surprised this is only called in one place.

> Source/WebInspectorUI/UserInterface/Base/Main.js:2359
> +    let closeHidden = WI._closeTabBarButton?.hidden;

o_O I guess it's OK!

[EWS]

Committed r258778: <https://trac.webkit.org/changeset/258778>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 394097 [details].

[Radar WebKit Bug Importer]

<rdar://problem/60698896>

[Devin Rousso]

Comment on attachment 394097 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=394097&action=review

>> Source/WebInspectorUI/UserInterface/Base/Main.js:900
>> +    WI.tabBar.resetCachedWidths();
> 
> How does the tabBar invalidate cached widths when the inspector window / view is resized? Surprised this is only called in one place.

When we're docked, the size of each `WI.TabBarItem` should never change, as we don't expand to fill available space.  When undocked, however, `WI.TabBarItem` do expand to fill as much available space as possible.  Along these lines, we have logic inside `WI.TabBar.prototype.layout` that handles this exact scenario :) <https://trac.webkit.org/browser/webkit/trunk/Source/WebInspectorUI/UserInterface/Views/TabBar.js?rev=258623#L469>