Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wg-amp4email Status Update 2019-12-04 #12

Closed
dreamofabear opened this issue Dec 23, 2019 · 0 comments
Closed

wg-amp4email Status Update 2019-12-04 #12

dreamofabear opened this issue Dec 23, 2019 · 0 comments

Comments

@dreamofabear
Copy link
Collaborator

Highlights

  • Held email mini-summit at ACS 2019 in NYC
  • Outlook.com launches AMP for Email to developer preview
  • VerizonMedia merged an OSS Java implementation of the AMP validator
  • Gmail rolls out AMP for Email to Android

WG Meeting Notes (9/12, 10/17, 11/8)

  • Working on unified sender registration process (shared form in review)
  • Received feedback on proposed shared HTML/CSS whitelist standards
  • Consensus on standardizing max email size (200KB), max template SSR size, etc. (Discussion: AMP element limits #4)
  • More discussion on "CORS for email" proposal (Discussion: CORS for email #7)
  • New proposal for email sender authentication (ecosystem-friendly replacement for proxy assertion tokens)
  • Discussed AMP validator versioning and mitigating version skew across providers
  • Consensus on allowing limited CSS attribute selectors (e.g. useful for amp-selector)
  • Proposed new component in AMP4EMAIL spec: amp-autocomplete
  • Self-hosting AMP JS and rollout patterns
  • New outreach channels for email senders and ESPs

Focus areas

  • Standardizing AMP for email behavior across providers by using AMP4EMAIL spec as single source of truth
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant