Access for Product Owners Only
Please note that this forum/thread is exclusively for product owners only.Please visit the Community Passport to register your products now and unlock this area.

We'd like to know about your workflow in Fusion!
Do you storyboard, work on visuals first? Maybe you focus on the code/logic right from the start - we'd love to know!CLICK HERE to take part in our poll/discussion when you have a moment!

ClickConverse b103 (beta) - Report any bugs here

Please report any bugs you find with Build 103 here. Please do not post feature requests here, I have made a separate thread for those. This thread will be heavily moderated to keep it to bug reports only so I can keep a track of everything.

Simon, please reconsider the save name, I don't think saving the logs to the application folder is a good practice for chatrooms. Also, I'm not sure but you might be missing leading 0s from some of the timestamp.

White-out bug

I saved a HTML document when the CC window whited out. The document shows no chat messages at all, although CSS is saved correctly. This indicates a file handle issue, and/or if WebX is saving the document itself, an issue with the object.
Here's the codes:

That's an interesting one and I instantly sse not something with a straightforward answer...

The default document which is created when a new chat window is opened contains a standard document definition, CSS and some javascript which interacts with MMF and the page.

New lines are added by creating a new node and appending it to the DOM, by calling a function from MMF. IE doesn't see this added content reliably (if at all) when you make a standard save request. Instead, I have a function to return the innerHTML of the whole page, which MMF can then read.

At this point it recreates the document but without the javascript (which is unnecessary for a log save, in MMF. The return is injected into this.

That you hsve the output file you do means WebX has either not returned the data at all, that it did return data but this overflowed a buffer or something, or, that the WebX had silently reset and restored the initial document (which was blank).

I shall have to ask Fernando what he thinks... it certainty hasn't locked up MMF so I'm leaning toward WebX creating a data loss here somewhere.