UI does not show search link in category widget

Context

I was testing something else, related with widgets and found out that my chrome browser in my ubuntu linux does not show the search link in category widgets.

Steps to Reproduce

1. Open this embed in my computer with my chrome: https://team.carto.com/u/rtorre/builder/7eee47fb-3a67-4491-b137-abe037ddb296/embed

Current Result

Here is a screenshot of builder showing the element that is not rendered. CSS properties are computed in such a way it has height = 0 for some reason, as shown in the screenshot.

Expected result

This is how it works in all other browsers (chrome or firefox, as long as they are not my chrome in my linux):

Browser and version

Google Chrome	59.0.3071.115 (Official Build) (64-bit)
Revision	3cf8514bb1239453fd15ff1f7efee389ac9df8ba-refs/branch-heads/3071@{#820}
OS	Linux
JavaScript	V8 5.9.211.38
Flash	26.0.0.131 /home/rtorre/.config/google-chrome/PepperFlash/26.0.0.131/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Command Line	/usr/bin/google-chrome-stable --flag-switches-begin --flag-switches-end
Executable Path	/opt/google/chrome/google-chrome
Profile Path	/home/rtorre/.config/google-chrome/Default

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04 LTS
Release:	16.04
Codename:	xenial

.carto file

This is the base .carto file that I worked with, but it shouldn’t matter that much which one to use:

An_overview_of_Nigeria_institutions__on_2017-03-13_at_11.51.55_.zip

Additional info

No error in requests nor in js console.

I asked several colleagues with linux machines to try the same embed with chrome. I was the only one having that problem.

Consider this low priority for the moment, as I’m the only one affected and I have a workaround. But lets keep track of especially it in case we find out there are more people affected.

cc/ @jsanz and @xavijam for awareness.

[noguerol]

Ok, I then suggest we close this until it happens again.

[rafatower]

I reported the bug the best I could and I investigated the root cause and documented my findings, but as stated above I cannot pursue it any further w/o some help from others.

I added it to the response kanban (as candidate) for prioritization cc/ @noguerol