Raised by @M-J-Robbins in ampproject/amphtml#22318
As emails are rendered inside the email client, they are technically not separate documents per se. The specific implementation detail of rendering inside an iframe currently does make them separate documents, but this isn't the case for regular HTML emails, which are just inlined.
In other words, broadly speaking, an email client that displays an email thread with multiple emails can be either:
A single document displaying multiple articles (emails).
A document containing multiple documents inside of it.
Currently, due to implementation details, AMP emails are considered separate documents and HTML emails are considered articles inside a single document.
If we choose to align AMP emails with HTML emails, email clients need to set the appropriate role (either presentation or article) and we also need to ban (initially deprecate) tags such as <main>, as only one can exist per document, so multiple emails having this would be against a11y practices.
If we choose they are separate documents, email clients must set role=document on each AMP email when they render it (there may be other implications of doing this).
Hi @fstanis ,
can you suggest us how we attach PHP file in amp scripts.?
@fstanis sir I have sanded a mail also regarding this query on filip@stanis.me mail.
Raised by @M-J-Robbins in ampproject/amphtml#22318
As emails are rendered inside the email client, they are technically not separate documents per se. The specific implementation detail of rendering inside an
iframe
currently does make them separate documents, but this isn't the case for regular HTML emails, which are just inlined.In other words, broadly speaking, an email client that displays an email thread with multiple emails can be either:
Currently, due to implementation details, AMP emails are considered separate documents and HTML emails are considered articles inside a single document.
role
(eitherpresentation
orarticle
) and we also need to ban (initially deprecate) tags such as<main>
, as only one can exist per document, so multiple emails having this would be against a11y practices.role=document
on each AMP email when they render it (there may be other implications of doing this).