Remove #project-browser from CSS and use more specific selectors.

I'm a little concerned about the use of positional selectors - that makes the styling very vulnerable to slight changes in markup, and without visual regression testing, it's way too liable to break randomly on us.

Removed the fragile selector as i completely agree with @phenaproxima.It's up for another round of review and some manual testing.

I mean...that CSS looks fine to me! 🎉

I'll tentatively mark this RTBC, hopefully @chrisfromredfin and/or @narendrar can kick the tires a bit to see if we accidentally regressed anything.

Moving to NW just to get an answer to my question about that other class. but it may be out of scope for this issue .

I have changed the selector coming from upstream with the selector in our scope.Marking it NR again.

The code looks good to me, so I am tentatively RTBCing this, but it will need some pretty solid manual testing from someone who is more familiar with the look of this module than I am.

Manually tested in Claro and Gin theme. No visual regressions.

documenting here that the animation thing seems a little changed after my rebase, but I think it was correct based on past diffs of Utkarsh's work.

Automatically closed - issue fixed for 2 weeks with no activity.