I found a really strange behavior when using a Materialize CSS modal in Firefox (66.0.1). It works fine in Chrome (73.0.3683.86) and MS Edge (where do you find the version?). I'm using Windows 10. It does this with the modal demo in the official Materialize CSS website as well.
The problem seems to start if you display a modal with enough content so that it displays a vertical scrollbar. It needs to have links or buttons to see the problem I will describe. You can simulate this by resizing Firefox so that its vertical height is small enough to make the scrollbar appear. Now close the modal. Then resize the height of Firefox so that the modal will appear without scrollbars. Open the modal and hover over a link or button and any hover effect that should happen, does not. Click once on any link or button and nothing happens. Click a second time and it works properly.
And even odder, after opening the first modal with a scrollbar, you can open the second without a scrollbar and do nothing for about 15 seconds and then the links or buttons will work fine.
When this happened, I tried right-clicking on the button to "inspect the element" in the Firefox Inspector. Instead of getting the button, I got the modal overlay element behind it. Note that when this happens, the overlay is not above the button or any of the modal content. It's not a z-index problem. To see whether it was a problem with the overlay, I added an onOpenEnd() function to the modal options that would remove the overlay as soon as the modal opened. I had the same problem. When I tried again to open it in the inspector, I got whatever was behind the button. So it's almost like the modal isn't even there until I click on the modal first or wait for 15 seconds.
I then tried to add some code to the onOpenEnd() function that would give focus to the button, but no effect with that. I tried tabbing to the button, but that didn't work either.
Just before submitting this I found another piece of the puzzle. As I said, hovering over the buttons when this is happening will not show the usual hover pointer. But if I hover above and a bit to the left of the buttons, the cursor does change. When I click there, the color of the buttons does change like it's been clicked, but the action (closing the modal) does not happen. Hmmmmm....
If you want to test this out, go to the Materialize CSS webisite and open the page for modals. (https://materializecss.com/modals.html) Reduce the vertical size of Firefox so that when you open the demo modal it has a vertical scrollbar. Now close the modal. Resize Firefox back to normal vertical height and open the modal again. Hover over the Agree or Disagree buttons and you won't get the pointer cursor. Try click once and nothing happens. Click again and the modal will close. Or wait the 15 seconds and then the buttons work.
Most of my users will have the modal open for more than 15 seconds so it's not a big problem. But sometimes they will open it just to check something and then want to close it. Sure they can click twice, but I'd rather it work properly. Chrome and Edge work fine. Firefox doesn't. Can anyone think of what is causing this and whether there is anything I can do in my code to make it work properly? Thanks.
Related
I have a form in an iframe for cc payment (paymetric). The last field is expiration date from a dropdown list. When the user cursors out of the frame back to my page and hits the submit button FireFox is requiring a click to activate the page then another click to submit. In other words, it seems the user has to click twice on the next button. Again, its only in firefox, and alas i have no live samples to show you :( By the way, losing focus from an input box in the framed form this doesnt happen.
I've tried blur/focus onmouseout of frame, even tried jquery trigger('click') to no avail. Any thoughts anyone?
We have the same Issue - it is solved by cleaning up Firefox:
I'm using the jasny offcanvas menu which works well but strangely, when I open and then close the menu, it slides out and then reappears. I assuming this is a z-index issue or maybe an HTML structure problem, but I can't see it.
Current development site is at http://powerdirect.petersenuploads.co.uk/, shrink the window to <768px to see the effect.
What am I missing here?
Many thanks
Pete
I have a popop on my page with cross button image.
When I open the popup for the first time everything is fine.
But when I close the popup and open it again, the cross button image flickers.
How can I Fix this.
I am facing this problem only in firefox. Are there any configuration settings which i need to make?
Got the issue. A button click function was written twice because of which the popup was loading twice and the image flickering happened.
I have an ajax modal popup that animates the popup panel in.
Everything works fine in Firefox et al, but there are a couple of issues in IE8.
1) The text looks grainy (as per when you use a filter with text).
2) Hover state on buttons does not work.
I'm trying to find a solution, but struggling to come up with an answer. Maybe one solution is to try and call animation from javascript rather than place it in the aspx page.
Any ideas?
I am developing a web application. I used radio buttons for selecting the category as shown in following image.
On Selecting the first radio button hides the Overlay button. On selecting the second radio button shows a button where on click of that i can select the data from overlay.
After clicking on second radio button, if i click on browsers refresh button the option2 is selected by default but the "select From Overlay" is not displayed. This issue is coming in Mozilla Firefox. Can anyone suggest how to solve it?
The value being preserved across the refresh is a convenience feature of forms. In this case, you will need some extra page init script to look at the value on the radio buttons to initialize as if the click happened.
Note: If you refresh with Ctrl+F5, you will generally see the browser will load the page with all the form values from before the refresh tossed out. Your user won't do this, but it illustrates how the browser is juggling your input in an effort to preserve it.