Copilot m365 textbox move to the top when copilot writes or I scroll to the bottom

I've been having the same problem for a few days now, particularly in longer chats the input box keeps moving up higher and higher until eventually i cannot even see the chat contents. If I refresh the page and then navigate back to the same chat then it initially displays the full top of the chat before it starts scrolling to the bottom but as it does that the input box progressively moves up the screen until i once again cannot see any of the chat (or at the very least I have less than an inch of space to scroll through the chat content)

frankly it's made copilot almost entirely unusable for me beyond the initial start of a conversation, starting a new conversation for every followup is a stupid workaround, but i have no choice if I want to use copilot

@Haien-L none of your suggestions seem to be helpful in my case, the closest i can get to making it readable again is to set the page zoom to 25% at which point the text is so tiny I can't even read it with a magnifying glass. All browsers are affected, including Chome, Opera, Edge, MS-Teams, CoPilot app, etc. basically EVERY implementation of Copilot has this bug and it's affecting my entire team at work on every computer.

unable to even scroll to the top of the chat because the scroll bar is rendered entirely off screen making it inaccessible

I have this exact problem myself. I get the dialog box a half to two-thirds of the page. I just started with a new company, and it is happening on a new install, nothing is blocking it, cache or otherwise. The specific <div> causing this is: <div id="m365-chat-inputt-shared-wrapper">

I was using a fresh Windows 11 laptop, updated, and the first time using Edge.

From the looks of it, it seems to be an issue with the website.

Our work also has this issue across multiple staff.

Does Microsoft have any fixes yet?

Fully closing the desktop app and reopening, then going back to a previous conversation is unacceptable. It will then move the contents up again after it generates the next response.

Yeah this is happening to me, both in the browser and on the app. I keep doing workarounds, but it is really crushing my productivity to the point where I might have to use something else until this gets fixed. Ive tried all the suggestions on various postings Ive found about this.

I have this exact same issue since a few days ago. This seems like a regression to me, and none of the solutions suggested here have worked.