Content deleted Content added
Mike Gracia (talk | contribs) m Removed line re: "Especially for users of gmail" as no citation and was from 2015. Things changed with gmail in 2016 and they started to support a LOT more CSS use. See this article for info: https://www.smashingmagazine.com/2017/01/introduction-building-sending-html-email-for-web-developers/ under the heading "GMAIL SUPPORT FOR INLINE CSS AND MEDIA QUERIES" |
The reference link was broken. Just removed Tag: references removed |
||
Line 15:
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 separate style from content.{{cn|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 |date= |accessdate=2012-06-24}}</ref> this has caused no shortage of frustration among newsletter developers, spawning the [[grassroots]] [http://www.email-standards.org/ Email Standards Project], which grades email clients on their rendering of an acid test, inspired by those of the [[Web Standards Project]], and lobbies developers to improve their products.
{| class="wikitable"
| |||