/*** custom social bookmarks widget  ****/
function social_bookmarks_register_widget() {
register_widget( 'add_social_bookmarks' );
}
add_action( 'widgets_init', 'social_bookmarks_register_widget' );

class add_social_bookmarks extends WP_Widget {
public function __construct() {
  $widget_ops = array(
    'classname' => 'socialbookmarks-widget', 
    'description' => __('A widget that displays the social bookmarks', 'avia_framework') 
    );
  parent::__construct( 'add_social_bookmarks', THEMENAME.' Social Bookmarks', $widget_ops );
}

public function widget( $args, $instance ) {
  $title = apply_filters( 'widget_title', $instance['title'] );
  echo $args['before_widget'];
  //if title is present
  if ( ! empty( $title ) )
  echo $args['before_title'] . $title . $args['after_title'];
  //output
  echo $before_widget;
  $social_args = array('outside'=>'ul', 'inside'=>'li', 'append' => '');
  echo avia_social_media_icons($social_args, false);
  echo $after_widget;
}

public function form( $instance ) {
  if ( isset( $instance[ 'title' ] ) )
  $title = $instance[ 'title' ];
  else
  $title = __( 'Social Bookmarks', 'avia_framework' );
  ?>
  <p>
  <label for="<?php echo $this->get_field_id( 'title' ); ?>"><?php _e( 'Title:' ); ?></label>
  <input class="widefat" id="<?php echo $this->get_field_id( 'title' ); ?>" name="<?php echo $this->get_field_name( 'title' ); ?>" type="text" value="<?php echo esc_attr( $title ); ?>" />
  </p>
  <?php
}

public function update( $new_instance, $old_instance ) {
  $instance = array();
  $instance['title'] = ( ! empty( $new_instance['title'] ) ) ? strip_tags( $new_instance['title'] ) : '';
  return $instance;
}
}

for quick css like above:

#footer .social_bookmarks {
    float: left;
    margin: 15px 0 0 ;
    position: relative;
}

#footer .social_bookmarks li {
     float: left;
    clear: right !important;
    margin-right: 10px;
    border: 1px solid #999;
}

You will then have your own widget for it and can drag it in a widget-area of your choice
All social Buttons you will define on Enfold Options will be there

these are the lines in formatting.php (WordPress File) to be responsible for multiple br replacement:
line 476ff

// Change multiple <br>s into two line breaks, which will turn into paragraphs.
	$pee = preg_replace('|<br\s*/?>\s*<br\s*/?>|', "\n\n", $pee);

what makes me wonder is that the old filter in functions.php child-theme:

remove_filter( 'the_content', 'wpautop' );
remove_filter( 'the_excerpt', 'wpautop' );

seems not to work as it should.

Even the filter tiny_mce_before_init i try to influence it via that filter

add_filter( 'tiny_mce_before_init', 'change_mce_options' );
function change_mce_options( $init ) {
	$init['extended_valid_elements'] = '*[*]';
	$init['remove_linebreaks'] = false; 
        $init['convert_newlines_to_brs'] = true; 
	$init['remove_redundant_brs'] = false;
	return $init;
}

no effect

the edited textblock.php ALB Element with no wpautop stripslash : https://pastebin.com/M91L76av
_________________
A multiple <br> will always be tranformed to one p-tag

I don’t think you’re doing yourself a favor with a bump. This gives your theme a new timestamp and is therefore more recent. The mods I think work it off chronologically.
Besides, it’s not an enfold problem. The wpautop function is WordPress own and the TinyMCE is a bit hard to be influenced there.
I have already tried tinymce.init, but have not yet had any success.
It’s up to you to use a <br class="noclear"> in the html editor field several times instead of <br>.

Ah – one thing to mention: if you show the sidebar on mobile phones ( small screens) these rules have to be in media querries to have the normal behavior on responsive case

@media only screen and (min-width: 767px){
.page-id-29934 .container_wrap.sidebar_right .container {
  display: flex;
  justify-content: space-around;
  align-items: flex-start;
}

.page-id-29934 .sidebar  {
  position: -webkit-sticky;
  position: sticky;
  bottom: 0;
  align-self: flex-end;
  width: 25% !important
}
}

i did it here with a sidebar:

https://webers-testseite.de/buttons/

and we have to change the overflow rule ( the #top has to be present in the rule) to ( in this case only for that pages):

.responsive body#top.page-id-29934,
.responsive body#top.page-id-33933 {
    overflow-x: visible;
}

.page-id-29934 #wrap_all,
.page-id-33933 #wrap_all {
    overflow: visible;
}

The sticky goes to the sidebar itself – but to find the right parent is a bit different – on that case:

.page-id-29934 .container_wrap.sidebar_right {
  display: flex;
  justify-content: space-around;
  align-items: flex-start;
}

.page-id-29934 .sidebar  {
  position: -webkit-sticky;
  position: sticky;
  bottom: 0;
  align-self: flex-end;
  width: 25% !important
}

The only thing – flex does change something to width definition – the sticky element needs the width info of enfold basic setting – in my case 25%

Rikards code will solve the problem, but I don’t understand why it was created. Did you set a new rule that affects the headings?
On default there is a rule for .html_elegant-blog #top .post-entry .post-title, .html_elegant-blog .avia-content-slider .slide-entry-title

so did you change something for the titles on your css?

this would solve the issue too:

.html_elegant-blog #top .post-entry .post-title, .html_elegant-blog .avia-content-slider .slide-entry-title {
    padding: 0px 0 15px !important;
    margin-bottom: 10px !important;
}

if you want to reduce the distance between the search results play with this value a bit:

#top .template-search.content .entry-content-wrapper {
    padding-bottom: 20px;
}

try again but copy / paste this into your functions.php of child-theme instead.

The code is correct – maybe you have copied it from a post like yours ;) with wrong quotation marks !:

add_filter('avf_logo','av_change_logo');
function av_change_logo($logo){
if(is_page(9)){
	$logo = "http://kriesi.at/wp-content/themes/kriesi/images/logo.png";
	}
	return $logo;
}

And by the way – to get rid of this info in list view Pages / Posts in the backend – ad to functions.php of child-theme:

add_filter('display_post_states','remove_ALB_post_state',999,2);
function remove_ALB_post_state( $post_states, $post ) {
	if("! has_blocks( $post->ID )") {
		unset($post_states['wp_editor']);
	}
	if("!= Avia_Builder()->get_alb_builder_status($post->ID)") {
		unset($post_states['avia_alb']);
	}
return $post_states;
}

danke – das erleichtert die Ratschläge ungemein.
Ich schau dann nochmal rein. Du kannst mir das übrigens auch zusenden, wenn es online ist.
Unter meinem Nick hier sind die Kontaktinformationen ableitbar. click click

theoretically it had to work with the 1280 on both – because only max-width includes the named break-point – the min-width not,
but maybe that is an old relict of the box-modell where the one browser includes the border to the box – the other not (so called 1px bug)
When you go through enfold css you will see that they alway diminish the max value about 1px ( the min-width are on even-numbered values ( 768, 990 etc.)

so this must work too:

@media only screen and (max-width: 1400px) {
.page-id-1602 #av_section_1 { display: none !important; }
}
.page-id-1602 #av_section_2 { display: none; }
@media screen and (min-width: 1280px) and (max-width: 1400px) {
.page-id-1602 #av_section_2 { display: block !important; }
}
.page-id-1602 #av_section_3 { display: none; }
@media screen and (min-width: 900px) and (max-width: 1279px) {
.page-id-1602 #av_section_3 { display: block !important; }
}

https://www.w3schools.com/css/css_rwd_mediaqueries.asp
max-width: 1280px means <= 1280px ( the 1280px is in the rule)
min-width: 1280px means > 1280px (1280px is out of that rule)

so this should be ok !!! but if you want to be sure leave a 1px distance between.

@media only screen and (max-width: 1400px) {
.page-id-1602 #av_section_1 { display: none !important; }
}
.page-id-1602 #av_section_2 { display: none; }
@media screen and (min-width: 1281px) and (max-width: 1400px) {
.page-id-1602 #av_section_2 { display: block !important; }
}
.page-id-1602 #av_section_3 { display: none; }
@media screen and (min-width: 900px) and (max-width: 1280px) {
.page-id-1602 #av_section_3 { display: block !important; }
}

so again my question : does your devices show my website as it should?
Does the header shrink on my website with your devices?
My test with the same Chrome Version as you ( and btw: now it is Version 72.0.3626.81) and with newest Safari and with my ipad shows my page as it should.
It shows the normal Navigation Menu and is shrinking on that case and with all browsers and devices.

The code is in :
enfold/js/avia-snippet-sticky-header.js
on line 62 there is: if(shrinking && !isMobile) change it to: if(shrinking)

The original code states that the shrinking is only performed if the shrinking has been selected in the options and it is not a mobile device.
In that function : function avia_header_size() from line 39 on there will be your classes header-scrolled and header-scrolled-full. It only happens to mobile devices if you get rid of that !isMobile condition.

if this will solve your problem – we can go the next step to make it update independent with a child-theme file and a code to load the alternative file.
Do not forget to refresh merged files in Enfold and to clean all cachings on Safari and Chrome

so post a link to your site , if it had to be not public just post the link in private content. Then you have to wait for a mod.
Without a link it is hard to reproduce the things you described and to understand the problem as well.

Na – anhand des Screenshots kann ich ja wohl auch deutsch schreiben.
Ich versuche halt mit einem livelink mittels developer tools und dem Screenverhalten zu sehen was man da machen kann. Das geht mit einem Screenshot leider nicht.
Gemeint ist da unten, bei weitere Produkte. Die Titles brechen doch aber um bei kleineren Screenweiten oder?

But a subscription is not nedded for the theme. This is a lifetime license. Only the support is limited to a certain time. Personally I haven’t experienced that yet, however, that after the expiration of the time one is deleted here from the board – or no more write permissions would have.

There has only been some confusion since the introduction of the Gutenberg editor in WordPress 5.x, which I personally completely block for Enfold. Meanwhile Enfold also offers this option to use the Classic Editor as default.
The Advanced Layout Builder (called ALB for short) is exactly the ingenious thing about this theme – and in principle a unique selling point. I don’t know of any WP theme that is as intuitive to use as this enfold. I have also been very busy with Divi, but find it by far not as pleasant to use as Enfold.
Maybe you should give it a chance, because the learning curve is very steep.