New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 673589 link

Starred by 9 users

Issue metadata

Status: Closed
Owner:
Closed: Oct 11
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-10-11
OS: Mac
Pri: 3
Type: Bug


Sign in to add a comment

Update Find-in-page bar to Material Design (Mac)

Project Member Reported by shrike@chromium.org, Dec 13 2016

Issue description

Here is the spec (and note that icon colors, etc. probably have to flip for Incognito, but are also overridden by the theme).


 
SPEC-core-ui-fip.png
195 KB View Download

Comment 1 by lgrey@chromium.org, Feb 24 2017

Is there a spec/prior art for how to do the shadow? I found the views code, but hoping there's an established way in Cocoa

Comment 2 by shrike@chromium.org, Feb 25 2017

Cc: tapted@chromium.org
It might make sense to just do this in Views and ship it with #md-secondary-ui

Comment 3 by tapted@chromium.org, Feb 28 2017

Ooh interesting - I didn't realise this is so close in appearance to a floating window/bubble. So, it does look possible to do this. The current MD window/animation does compile and "work" on Mac, but it's pretty janky (see attached).

Issues 
 - framerate could be better (partly due to debug build maybe)
 - appears to "pop" in rather than slide (again, partly due to using a debug build in this video, but there's something to optimize/waitfor here)
 - when sliding out, the contents move out over a white background (making the background transparent should fix this, but might have shadow implications)
 - sometimes the WindowServer-drawn window shadow doesn't get invalidated, or doesn't get drawn (I couldn't repro that in this video, but it can happen).

Also plumbing this through for a Cocoa browser could get curly because of possible assumptions around whether the findbar is an NSView versus and NSWindow.
md_findbar_mac.mov
1.7 MB Download

Comment 4 by shrike@chromium.org, Mar 20 2017

Blocking: 593693

Comment 5 by tapted@chromium.org, Apr 12 2017

Blockedon: 710506

Comment 6 by tapted@chromium.org, May 25 2017

Cc: lgrey@chromium.org
 Issue 726045  has been merged into this issue.

Comment 7 by tapted@chromium.org, May 25 2017

Labels: MacViews-Dialogs Proj-MacViews

Comment 8 by tapted@chromium.org, Jun 16 2017

Blocking: 48568

Comment 9 by tapted@chromium.org, Aug 25 2017

Blocking: 758522
Labels: -M-57 M-X
Owner: ----
Status: Available (was: Assigned)
This is waiting on macviews secondary UI, but doesn't need to block Harmony launch, so I'm tagging M-X.
Blockedon: 651643 646734
Blocking: 671916
Labels: -Pri-2 Pri-3
Since we are using the NSView findbar for Harmony Phase 1, this should perhaps be labelled MacViews-Browser. Fixing it separately is not on the agenda AFAIK, so I'm dropping priority.

It also basically works already: See  Issue 646734 .

The *Harmony* bug for this on non-Mac is  Issue 651643 , and it is mostly done.

Unless we are planning to replace the NSView findbar before MacViewsBrowser, I don't think we need to keep this bug open.
Blocking: 815129
This needs a milestone attached to it. We can't have this UI for 69. And I assume we don't want it for MacViews in 67?
This is going to be tied to MacViews-Browser shipping, which is targeted at M69. Once MacViews-Browser ships, this will happen automatically. Does that work, bettes@?

Getting the Views find bar to work with the Cocoa browser window (pre-M69) or getting the Cocoa find bar to look like this would both be undertakings.
Labels: -M-X M-69
Labels: -M-69 Target-69
Owner: ellyjo...@chromium.org
Status: Assigned (was: Available)
MacViews triage: marking this as Target-69 and assigning to myself (to ensure that that happens).
Labels: M-69
Cc: mikesmith@chromium.org krisr@chromium.org hbono@chromium.org suzhe@chromium.org
 Issue 48568  has been merged into this issue.
Labels: -M-69
Labels: M-69
Labels: Group-Cleanup
Labels: -Proj-MacViews -MacViews-Dialogs Hotlist-CocoaBrowser
Per c#14, this is really a Cocoa thing.
Can we close this out with MacViews?
yeah I think we can WontFix everything in Hotlist-CocoaBrowser in bulk. (at some point). (if things go to plan). Although there's a lot more.. like, 3 of the bugs blocked on this one that we can probably also close out.
Labels: -M-69 -Target-69 M-71 Target-71
NextAction: 2018-10-11
Punting Hotlist-CocoaBrowser to M71, at which point I will mass-close them. NextAction is the M71 branch point.
The NextAction date has arrived: 2018-10-11
Status: Closed (was: Assigned)
Hotlist-CocoaBrowser -> Closed :)

Sign in to add a comment