Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Select Menu Issue - 2 Mouse Clicks Required to Open Menu #6318

Closed
RichieMcMullen opened this issue Mar 29, 2019 · 13 comments
Closed

Select Menu Issue - 2 Mouse Clicks Required to Open Menu #6318

RichieMcMullen opened this issue Mar 29, 2019 · 13 comments

Comments

@RichieMcMullen
Copy link

RichieMcMullen commented Mar 29, 2019

I've noticed on Chrome Version 73.0.3683.86 the select menus need 2 mouse clicks to open. On the first mouse click, it flickers and fails to open. It then opens normally on the second mouse click.

This issue can be replicated directly on the materialise website:
Click to View Issue

Environment Details
Web Browser: Chrome Version 73.0.3683.86
Materialise Version: 0.100.2
OS: macOS Mojave Version 10.14.2 (Desktop)
My Project: https://ardeecc.club/register

Tested this on Firefox & Opera, no issues.

ezgif com-video-to-gif

@andresilva-cc
Copy link

I'm suffering from the same issue on my project. Does anyone have a quick fix for this?

@RichieMcMullen
Copy link
Author

RichieMcMullen commented Mar 31, 2019

Gently bumping this issue!

Very keen to have this issue resolved otherwise it will mean having to change framework, something I'd rather not have to do if at all possible.

Thanks in advance!

@websiteinfo
Copy link

I have the same problem, well, for now mdbootstrap is better option :/

@Sebastriani
Copy link

The same for me together with #6312 it seems the Chrome update 73 broked a lot of things in materializeccs

@Dogfalo
Copy link
Owner

Dogfalo commented Apr 1, 2019

If upgrading to 1.0.0 is possible for your project, this is currently the best solution for the issue.

@Sebastriani
Copy link

@Dogfalo Not possible, I'm using v0.98.1 and I customized the hell out of it with SCSS, I would have to diff each file I changed...

@DanielRuf
Copy link
Contributor

This is a duplicate issue about a Chrome regression. Also see https://bugs.chromium.org/p/chromium/issues/detail?id=941910#c6

@websiteinfo
Copy link

If upgrading to 1.0.0 is possible for your project, this is currently the best solution for the issue.

Ver. 1.0.0 (beta?) without jquery has other problems too :/

@RichieMcMullen
Copy link
Author

RichieMcMullen commented Apr 1, 2019

I've reported the issue to Chrome. There seems to be some activity on the topic, so hopefully they find and fix the issue soon.

Bug Report Tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=947874#c3

@DanielRuf
Copy link
Contributor

@websiteinfo
Copy link

Fix in js file (line 1774) add value 100:

// Add click close handler to document setTimeout(function () { $(document).on('click.' + activates.attr('id'), function (e) { hideDropdown(); $(document).off('click.' + activates.attr('id')); }); }, 100);

@DanielRuf
Copy link
Contributor

This is no right fix. Debounce it for example. See amsul/pickadate.js#1140

@RichieMcMullen
Copy link
Author

Fix in js file (line 1774) add value 100:

// Add click close handler to document setTimeout(function () { $(document).on('click.' + activates.attr('id'), function (e) { hideDropdown(); $(document).off('click.' + activates.attr('id')); }); }, 100);

That has worked for me. Happy days!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants