Menu widget problems on version 3.2

After updating to version 3.2 my menu widget that is used as side menu became corrupted.

I have found out that your developing team had added #top value to the numerous elements in layout.css and now my child theme’s style.css or even Quick CSS cannot substitute these elements any more… even after adding old layout.css to my child theme folder… even after adding #top. Just a little piece of code from the new layout.css:

#top .widget_nav_menu .nested_nav{
padding-bottom:30px;
}

#top .content .flex_column .widget_nav_menu li a {
  padding: 0.8em 3px;
}

#top .content .flex_column .widget_nav_menu li a:hover,
#top .content .flex_column .widget_nav_menu ul:first-child>.current-menu-item, 
#top .content .flex_column .widget_nav_menu ul:first-child>.current_page_item{
  /* background-color: rgba(255,255,255,0.4); */
}

#top .content .flex_column .widget_nav_menu li {
  /* background-color: transparent; */
  /* margin: 0; */
  /* padding:0; */
  /* border-bottom-style: solid; */
  /* border-bottom-width: 1px; */
}

#top .content .flex_column .widget_nav_menu li:first-child {
  /* border-top-style: solid; */
  /* border-top-width: 1px; */
}

Of course, I will replace layout.css with my old one and never update it (and it can cause problems in the future), but I would like to propose to your developing team not to use the methods of the last chance to make modifications because there are your clients that will modify theme later. For example, developers can use #header instead of #top, it works most of the time. And, of course, the support team will have less headache.

Sorry for being emotional.