Dropdown is not working in Safari

Hello @kongenskoreskole

Hope you’re doing well today! Thank you for reaching out to us.

I was able to replicate the issue with the dropdown select field (V?lg pakke) on the page URL you shared when I visited the form on Safari browser. However, the dropdown works fine on Firefox and Chrome browsers.

Further, I tried to replicate the issue on my test site on the Safari browser but the select dropdown was working fine. It means that the issue could be related specifically to the form added to your site.

Hence, we will need to take a closer look at your form so that we can troubleshoot the issue further. For this, would you mind sharing the form export with us so that we can take a closer look?

You can follow the guide below on how you can export the Forminator form.
https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#import-export

After exporting, please share the code using services such as https://pastebin.com or https://justpaste.it/ which are free to use.

Please feel free to remove any sensitive information the form might contain.

Awaiting your response.

Kind Regards,
Saurabh

Find export here: https://pastebin.com/hUHrPgh7

Hi @kongenskoreskole

It seems you have exported a copy of this form, which does not have pagination, which exist in oryginal form on the page you shared with us.

With the exported form we cannot replicate this issue in Safari. Can you export correct form and share it once more?

Kind Regards,
Kris

Find new export here: https://pastebin.com/qr0QYtHE

Hi @kongenskoreskole

With your form on my lab site issue still does not exist.

it seems issue exist only in Safari and this is some conflict with this CSS from theme.css file

.position-relative {
  position: relative; }

.new-stacking-context {
  position: relative;
  z-index: 1; }

Issue seems to be more complex here, because as soon this CSS is removed, still select from Forminator does not work fully.

I pinged our SLS Team to review this closer and see what we can do in this case. We will post an update here as soon as more information is available.

Kind Regards,
Kris

Hi @kongenskoreskole,

Our Second Level Support team suggested the following workaround, can you please try adding the code using a mu-plugin?

<?php

add_action('wp_footer', 'wpmudev_form_selection_fix', 9999);
function wpmudev_form_selection_fix() {
	global $post;
	if ( is_a( $post, 'WP_Post' ) && !has_shortcode($post->post_content, 'forminator_form') ) {
		return;
	}
	?>
	<script type="text/javascript">
    jQuery(document).ready(function($){
		setTimeout(function() {
			$('.forminator-custom-form').trigger('after.load.forminator');
		},100);

		$(document).on('after.load.forminator', function(e, form_id) {
			if ( e.target.id == 'forminator-module-5446' ) { // Please change the form ID.
                $('#select-2 select').on('select2:open', function(e) {
					var select_offset = $('#select-2 select').position().top;
                    setTimeout(function(){
                        var left = $('.forminator-select-dropdown-container--open').css('left');
                        $('.forminator-select-dropdown-container--open').attr('style', "left: " + left + "!important; top: " + select_offset + "px !important; position: fixed !important;");
                    },2);
                });
            }
        });
    });
	</script>
	<?php
}

Please find more about how to add a mu-plugin in the following documentation: https://wpmudev.com/docs/using-wordpress/installing-wordpress-plugins/#installing-mu-plugins

I hope that helps.

Kind Regards,
Nebu John

Hi @kongenskoreskole,

Since we haven’t heard from you for a while. I’ll mark this thread as resolved for now. Please feel free to open a new thread if you have new queries.

Best Regards
Nithin

I am sorry but installing the mu-plugin is to technical for me. The case has not been solved and I must await a standard update from your end.
When will that happen, as it must be a general problem?

Hi @kongenskoreskole,

Considering that it seems to be a theme-related conflict, and as we haven’t received any similar reports so far, we currently don’t have plans for a fix at the plugin end. I understand this might be inconvenient. Would it be feasible for you to try switching to a default WordPress theme to see if the issue persists?

Additionally, I recommend reaching out to your developer or hosting support to explore the possibility of implementing the suggested workaround. Their assistance might be valuable in resolving this matter.

Kind Regards,
Nebu John