- From: <bugzilla@jessica.w3.org>
- Date: Thu, 01 Mar 2012 22:07:31 +0000
- To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16185 --- Comment #4 from Aryeh Gregor <ayg@aryeh.name> 2012-03-01 22:07:31 UTC --- Oh, I misunderstood. So the problem in WebKit's case only affected <font face>, and only because of non-browser e-mail clients. Some e-mail clients (evidently including Outlook 2007) don't parse quotation marks in <font face>. Given that, adding quotation marks when serializing font-family would cause problems for editing. Basically, the problem is that some very common editing actions will find the computed font-family (which is serialized per CSSOM rules) and re-output it in <font face>. This will break e-mail clients like Outlook 2007 if the original font-family had quotation marks added by CSSOM, so if CSSOM does this, we'd need workarounds in the editing spec/implementations to work around it. It's also more verbose, and if you use double quotes, it adds entities in the HTML serialization. So I still suggest that font names should be serialized with quotes only if they can't be serialized without quotes. (Yes, it's kind of lame that editing has to account for broken e-mail clients. Web browsers are broken enough. But users object if their richtext webmail doesn't display right for Outlook 2007 users.) I really should have made two bugs. Oops. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 1 March 2012 22:07:33 UTC