CSS :root selector removed from code [172000114]

Assigned

Bug

Status Update

No update yet.

Description

ma...@salesforce.com

created issue #1

Oct 30, 2020 12:11PM

A short description of the issue: Gmail removes the CSS :root selector. This selector is supported in the AMP playground and in mail.ru.

If appropriate, a small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.

<!doctype html>
<html ⚡4email>
<head>
  <meta charset="utf-8">
  <script async src="https://cdn.ampproject.org/v0.js"></script>
  <style amp4email-boilerplate>body{visibility:hidden}</style>
  <style amp-custom>
    :root{background:green;}
  </style>
</head>
<body>
  Hello, AMP4EMAIL world.
</body>
</html>

What is the expected output? What do you see instead? If you see error messages, please provide them. With this code I’d expect the background of the email to be green. But in Gmail it isn’t. On inspecting the code I can see the selector has been removed.

Comments

se...@google.com <se...@google.com> Oct 30, 2020 01:19PM

Assigned to se...@google.com.

se...@google.com <se...@google.com> #2Oct 30, 2020 02:47PM

Are you using Linkify?

ma...@salesforce.com <ma...@salesforce.com> #3Oct 30, 2020 04:35PM

Can you provide the below requested information to better understand the issue:

Device used
Which device did you use to reproduce this issue?

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

se...@google.com <se...@google.com> #4Nov 4, 2020 11:30AM

I cannot reproduce the issue on my side with a sample app. I have this in production.

Conditions to have this crash:
- Android 8.0.0, whatever the manufacturer (Samsung, Sony, LG…)
- Have the Accessbility Service enable (which is for an optional feature on my application)

Into the last 7 days I got few thousands of users affected which represents 5% of users with both conditions.

I understand this bug is now fixed on your side (because I don't have any report on 8.1 for example) but as Android 8.0 is more and more deployed I have more crash reports everyday.
It can be really very useful to have a workaround from our application side to avoid this issue rather than just "wait for 8.1 to be more deployed".

is...@google.com <is...@google.com> Jan 25, 2023 06:19PM

Status: New

jp...@google.com <jp...@google.com> Jul 13, 2023 01:30AM

Assigned to wo...@google.com.

Issue 172000114