HTML email: Difference between revisions

Content deleted Content added
Line 17:
Among those email clients that do support HTML, some do not render it consistently with [[W3C]] specifications, and many HTML emails are not compliant either, which may cause rendering or delivery problems.
 
In particular, the <code><nowiki><head></nowiki></code> tag, which is used to house CSS style rules for an entire HTML document, is not well supported, sometimes stripped entirely, causing in-line style declarations to be the [[De facto standard|''de facto'' standard]], even though in-line style declarations are inefficient and fail to take good advantage of HTML's ability to [[Separation of content and presentation|separate style from content]].{{citation needed|date=January 2015}} Although workarounds have been developed,<ref>{{cite web|author=Dialect <http://dialect.ca/> |url=http://premailer.dialect.ca/ |title=Premailer: make CSS inline for HTML e-mail |publisher=Premailer.dialect.ca |accessdate=2012-06-24}}</ref> this has caused no shortage of frustration among newsletter developers, spawning the [[grassroots]] Email Standards Project, which grades email clients on their rendering of an acid[[Acid test]], inspired by those of the [[Web Standards Project]], and lobbies developers to improve their products. To persuade [[Google]] to improve rendering in [[Gmail]], for instance, they published a video montage of grimacing web developers,<ref>{{cite web |url=http://www.email-standards.org/gmail-appeal |title=The 2008 Gmail Appeal &#124; Email Standards Project |publisher=Email-standards.org |accessdate=2012-06-24 |url-status=dead |archiveurl=https://web.archive.org/web/20120515030536/http://www.email-standards.org/gmail-appeal |archivedate=15 May 2012 }}</ref> resulting in attention from an employee.
 
{| class="wikitable"