in another area i tried to post a support question but ended up with web objects placed over where i needed to type the title of my post. can someone tell me how to get those objects away? i will retry it to get a screen capture.
Please share screenshots, if possible, to help us understand the issue.
Are you trying to post in Support and Help or some other category?
3 Likes
I am going to take a wild guess that this is what you are seeing.
Or something similar…
Go to the lock icon in your browser, clear cookies for this site, hard reset usually with Shift+F5.
Now open to create a new topic and the composer will likely be minimized towards the bottom of the screen.
You can then grab the top bar and resize to just under where the category and tag bar are located.
Should allow you to post normally again.
2 Likes
FWIW, the Ubuntu Summit registration banner seems to mess up some offsets. It does go away when scrolling down but seems to take up some “phantom” space which trips up object placement. I noticed this when I realized the shortcut link atop the timeline to jump to the first post was almost fully covered in some topics.
The issue is that the editor can be resized so the top resize handle is behind the title banner. Looks like the editor needs a different z-axis coordinate to be in front of everything else. That also explains my issue, because everything seems to slide under or behind said top banner, so the top portion is covered by it.
It does indeed look like an issue with some CSS rules fighting with each other. I’ll make some tweaks to fix that composer window from extending above and behind the nav bar.
3 Likes
Seems to be fixed, thanks.
3 Likes
Can you also have a look at the timeline thing? As I said, I think it’s because the very to of the page slides behind the navbar.
See how “May 19” is partially covered; it’s not as bad as it was a week ago, though.
Looks like it’s fixed. Thank you berry much! 
It’s doing it again. I must have posted my last reply with the composer in fullscreen mode and that state got saved and is restored when trying to reply to another post. But the navbar at top covers all the buttons at the top, so exiting fullscreen in the normal way is impossible; I had to employ @rubi1200’s workaround, which is a bit destructive though. The editor is usable but, because it’s at a higher z-layer than the emoji selection popup, for instance, I cannot see the latter. And, since all buttons are hidden behind the navbar I wouldn’t even be able to upload this screenshot:
As a somewhat related issue, the “Close” dialog popup is also hidden behind the editor, when the latter is in fullscreen mode.
Currently I am not able to reproduce this, so I don’t quite know how to trigger this, but this was the third time it happened. I’d really like to get to the bottom of this, because said workaround is a bit destructive, since it also deletes the session cookie, so I must re-login every time this happens.
Try switching to Light mode, can you reproduce the same issue?
Via Preferences >> Interface
I don’t know if that is valid method to narrow the issue down to the color scheme, because currently I cannot even reproduce this in Dark Mode. (edit: I have switched to the “Default” (light) color scheme, though)
Maybe this is caused by some more obscure and somewhat random issue. I did have some issues with loading the site, which were reminiscent of the DDoS mitigation fallout. So my thinking is that perhaps some assets weren’t correctly loaded in the background and failed silently (for me at least), so the saved state of the editor got corrupted.
When writing my previous post, the screenshot upload was denied multiple times: “try again”; can’t remember if there was an error number. That’s an indication that not everything is back to normal (all the time), I guess.
I’ll try to use fullscreen mode for my next post(s) and see how that goes.
@aaronprisk Do you have time to look into this?
Thanks
Just a status update, the issue hasn’t returned yet. I believe it must have been a fluke caused by the state not being saved correctly due to some timeout; I seem to remember that the last post before it happened took some rather long time to be saved.