Hi. Thanks for writing in and apologies for the inconvenience, @lastala.
Could you set up a test page where we can see what you have now and figure out what is missing?
Well, you can see it in the following address.
https://www.lauriastala.com/551
In the text, there’s a link/underlined words that get to the popup.
Sorry, cannot set up a real test environment.
@lastala – The example seems to be working correctly based on its settings. It has a white background for me, with a partially white & transparent overlay behind it.
If that isn’t what you are seeing it could just be that your site or browser caching needs purged/cleared.
Let us know
@danieliser – No, that is not correct!!! You can compare the usage of the previous version of Popup Maker in here:
https://www.lauriastala.com/ (has the previous version of popup maker)
with
https://www.lauriastala.com/551 (has the last version of popup maker)
Please scroll the popup window up and down, and see the difference!!!!!
At least your plugin is malfunctioning on Safari 14.0.3 and FireFox 86 (and iPhone).
If you resize the window while the popup is on, then the popup starts to behave as is should. (But who should think that you should resize your window to make the website work.)
However, depending on the size of the window, when you open the popup, it can scroll down partially visible or totally invisible (for instance on an iPhone screen or a small window on a computer screen). This cannot be normal or correct.
@danieliser I updated the plugin again today when I saw there was a new update. But I also noticed that the update didn’t solve the problem described before.
Are you still thinking the plugin updates work as supposed? Or are you investigating the bug I described?
1. Not sure what this is supposed to be, but it isn’t something we recommend, even if there was a <popup> html element, it wouldn’t be used for the trigger, but rather the popup itself.

2. Went over every change in the latest version just now. Only one could have any potential impact here as all other front end changes were purely code formatting. IE only one thing changed, and that is that we changed when we force focus the first item in the popup until after it was open (visible), as doing it before often leads to failures since the item isn’t yet visible, and second allowed it to focus on the close button if nothing else was focusable.
Neither of those changes sounds like it should have any impact, BUT, you only have one focusable element in the popup at the bottom. So if there was a change on our end causing it, this is literally the only one possible.
Try disabling accessibility features for that popup via its Advanced settings.
If it turns out to be related to the new change, that change we made is necessary for WCAG accessibility standards so can’t go back.
—
One thing that I just thought of is that the browser may be calculating the position of the popup while the focused element is focused, since focusing an element brings it on screen (scrolls to it), the popup when its position is to be determined is scrolled way off the top of the screen.
Our position logic should not be affected by that, but just spitballing since I’m at a loss with no other changes.
-
This reply was modified 5 years, 2 months ago by
Daniel Iser.
@danieliser I tried “disabling accessibility features for that popup via its Advanced settings” and that did solve the problem.
Thanks
@lastala – Then strangely the last thing makes the most since, will have to investigate how the focus moving to the bottom of the popup after its shown, could affect positioning, which should be calculated before the popup is shown, or at least try to determine if that truly is the cause.
First gotta duplicate it locally.
Glad you got it working for now at least.