hello, I had solved it using this suggested 'workaround', but now that
iOS has released version 18, it is happening again in Safari. Has anyone
experienced the same problem and found a solution?
You are leaving our website
You are leaving our site and we cannot be held responsible for the content of external websites