Bug 40873 Comment 205 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I need to do a bunch more validation, testing and reading but I'm pretty happy with this approach now.

I explained it more above. It's be good to validate with product regarding what would block landing this type of work. We could split out the export, but we'd lose some ability to do comparison tests of HTML->MHTML and then reftesting those two files.

I think the only real missing part now is adding a pref to wrap it.
I need to do a bunch more validation, testing and reading but I'm pretty happy with this approach now.

I explained this new approach more [above](https://bugzilla.mozilla.org/show_bug.cgi?id=40873#c203). It'd be good to validate with product regarding what would block landing this type of work. We could split out the export, but we'd lose some ability to do comparison tests of HTML->MHTML and then reftesting those two files.

I think the only real missing part now is adding a pref to wrap it.
I need to do a bunch more validation (namely I didn't check iframes, I think we might need to propagate the loadinfo flags downwards into the child frame), testing and reading but I'm pretty happy with this approach now.

I explained this new approach more [above](https://bugzilla.mozilla.org/show_bug.cgi?id=40873#c203). It'd be good to validate with product regarding what would block landing this type of work. We could split out the export, but we'd lose some ability to do comparison tests of HTML->MHTML and then reftesting those two files.

I think the only real missing part now is adding a pref to wrap it.

Back to Bug 40873 Comment 205