Hello DEV Team
I found another bug. On desktop view, everything is fine, but on mobile view, on every single page and every pickaxe, I get the following layer that blocks literally every click, everything in this box that is laying “behind” it. It is blocking 100% of all functionalities “behind” it.
Would be great if this could be fixed asap! Thank you!
I had AI write my own script to kill that, just in general; it kills this ghost, but if I’m on mobile and want to use the menu, there is another ghost element that is blocking everything.
I wrote a script that kills both ghost elements. The problem is that this background was intended to be behind the menu, but it’s in front of the menu, so it looks rather unpleasant now without that background. In general, the menu should close after a click because it stays open now and the user can’t really see that it actually loaded the page or the new pickaxe that the user clicked on.
you can see here really the behavior and how it looks, and you have to manually close the menu to actually see what’s happening. Behind this is for sure not intended to be like this.
Thanks for the detailed screenshots and Loom, @easydeutsch. We just reproduced the overlay issue on mobile and filed it internally as Linear PRD-643 so engineering can jump on it. We will keep you posted as soon as the fix ships—in the meantime the desktop layout is the safest option. Appreciate you surfacing this so quickly.
@easydeutsch what Luna said - I have set the issue to urgent, and we hope to have a fix for you very soon!
hi there Jan !
i just took a look at this issue myself on mobile. pretty cool script you have hiding the nav and i admire the ingenuity haha.
this one is a simple fix actually, in this portal you have the opacity slider set to 10%
this is almost fully transparent, and explains the bleed through/misplaced content you mention above.
in my testing: setting it to 40% solved the issue, i’ll leave it for you to tinker with as i don’t want to change your portal settings without consent, but that should clear things up 
Hello Carson ´… yeah Grok wrote that Script 
So Credits go to Elon
JUst to clarify - the nav-background was on top of the menu so it pretty much blocked the entire menu and made everything except the bottom part of teh screen “dead” area.
My script kills the background - if not I would have to reload the page everytime I went to the menu as it also “hides” the menu close button on the top right! SO taht opacity settings should have no effect atm because the element it is applied to is kileld by my script. 
The other issue with the other ghost element that is not just in the navigation but everywhere, is that solved so I can take out the script?
to make it ore clear here a video:
pushed a fix, should be good to go !! but please let us know if the ‘ghost’ element is giving you problems any further 
No further problem with this, but now on mobile, on my home page, the entire navigation disappears. I do not have a login or sign up -->That right upper menu is missing, and also the main navigation between the different Pickaxe/agents is completely missing.
On the home page only! On every other page, it is there, but if they just put ai.easy-deutsch.de (that´s my home page) in there, all navigation is fully gone. It’s loading, but at the moment, when the page is fully loaded, the menus disappear!
On desktop it’s only the main navigation between the different Pickaxe agents, but on mobile both menus disappear.
Hi @easydeutsch ,
We found the root cause of this issue. It was caused by a script you wrote inside the HTML section of your home page, and we have now fixed it.
I explained the cause and the fix in more detail in the separate thread you created here:
Hello Danny! Thank you very much the navigation ghost element is solved yes but tehre is still the iniltially reported ghost element (first message here) that is still blocking anything other than the lower part and teh edges of the screen. This problem still exists on my end! The second one is fixed!
Hi,
Thank you for your patience while we looked into this further.
The element in question seems to be the native mobile hamburger button that opens the navigation menu. That button is present in our own portals as well, but in our testing it behaves normally and does not block the page or interfere with clicks on mobile.
Based on what we reviewed, the issue appears to be related to the custom code on your portal that affects floating mobile elements and pointer-event behavior. That code may be interfering with the native mobile navigation button and causing it to behave like a blocking layer.
Could you please temporarily disable the custom code that affects floating buttons, overlays, or pointer events on mobile and then test again? If that resolves the issue, we will know the behavior is being caused by the custom script. If it still happens after that, please let me know and I will reopen the investigation from our side.
this is solved now thank you
