This extension no longer works.

[mpalpha]

Shows "Loading..." forever.

[wojoNZ]

Would be greatly appreciated to have this fixed.

[ingo]

Sorry, I missed the notifications. It's still working for me. Does anything appear in the error console? Can you show a screenshot of what it shows?

[wojoNZ]

Not sure how to show a proper error console. But hopefully this helps?

https://imgur.com/a/6UeCNnQ

[ingo]

Thanks. The screenshot shows two items, but only the info one is fully displayed. How about the full text of the one in red? Also, which browser are you using (and which OS version)?

[charlesweir]

Nothing in Chrome's Javascript error console. I'm using 96.0.4664.110 on MacOs Catalina 10.15.7, looking at a simple chat in a University Teams account

.

[charlesweir]

Ah - found out how to enable error logging. I get:

Guess maybe adding https://teams.microsoft.com/ to permissions in manifest might help?

[Penagwin]

It looks like teams has changed the classes they use.

.ts-msg-name	->	.ui-chat__message__author
.message-datetime	->	.ui-chat__message__timestamp
.message-body-content	->	.chat__message__content

I haven't checked the others or if other things in the exporter needed modifications. This seems likely though.

EDIT: This method of scraping the DOM may no longer work on it's own, it looks like teams might be loading/unloading chats live as you scroll now

[charlesweir]

teams might be loading/unloading chats live as you scroll now

Indeed so. Loading as you scroll isn't a problem (there are several plugins to automate scrolling), but Teams now unloads all messages but those closest to the page you're viewing. So to do the job properly we'd need to force scroll AND cumulatively save messages as we do so.

[charlesweir]

Teams now unloads all messages but those closest to the page you're viewing

Wait a moment.... Just thought to check this by taking my machine offline and then scrolling back to the 'unloaded' messages. No. Teams doesn't unload the off-screen messages; instead it keeps them cached, but renders them as grey blocks until it has a chance to catch up. In fact, it loads a lot more messages initially than it shows. When I capture the grey blocks using a breakpoint, I find it's a virtual-repeat HTML element: I'm guessing that's a Chrome optimisation of the Angular-JS md-virtual-repeat element. It contains only the currently-rendered messages. To get the rest, maybe one could query its provider object?

[StoreMax]

Hi, has there been any progress on this?

[pbulteel]

Anything? It's been a year 😄

[1JotaPe1]

yeah it's over! :) but it was a good project thou

[ingo]

I believe I've fixed it now (sorry for the delay). Give it a shot.

[charlesweir]

Nice! Yes, it now works beautifully.

Thank you very much!!!!