ghen wrote:JDunphy wrote:I have one of our web developers looking at the js now to see if we can come up with a quick fix.
The quick fix is to restore /opt/zimbra/jetty/webapps/zimbra/js/MailCore_all.js and .zgz from P15.
(and either flush browser cache, or bump zimbraCacheBusterVersion and restart mailboxd.)
Thanks again and your posts have been very helpful.
That fix definitely works for the simpler Canada Post tracking email but that patch seems to fix a side effect and not the underlying root problem and we have seen emails that even patch 15 didn't fix but thought it was OWASP. As a result, we are attempting to get past this game of whack-a-mole. There seems to be an issue with how the table elements are being interpreted by the browser as an inline element vs a block element and how Zimbra wrapped their style around the message and how css inheritance behaves in that environment. Compounding the problem is that the email provided a large amount of table style in the middle of the document in addition to using a large number of nested tables to provide their layout. Also much of the emails table style has been deactivated (ripped out) by OWASP. Turning OWASP off however doesn't fix the problem but it will make it easier to get to the root cause with the browsers debugger if there is something more systemic here with how style is inherited.
Firefox can display the html from the email correctly by itself but once Zimbra wraps their iframe around this html and then applies its style than things get a little wonky. One of the things we are contemplating now is how strict browsers are with interpreting some of this style inheritance and we wonder if Firefox might be stricter at present than chrome/safari and if there are some big surprises in the future as browsers become stricter. All speculation at this point.
We are trying to find a way to break the problematic inheritance.
I could have this completely incorrect from her description but that is what I think she has told me.
