AMP respects the ⚡but rejects ⚡️, which is confusing since the macOS emoji picker creates ⚡️, that is, the representation with the Unicode Variation Selector-16.
The AMP validator checks for the presence of the representation without Variation Selector-16, but then replaces it with amp, the same happens on the AMP cache.
To avoid this confusion, AMP could potentially allow for both, ⚡️ and ⚡, and then just replace them with the textual attribute amp.
To avoid this confusion, AMP could potentially allow for both, ⚡️ and ⚡, and then just replace them with the textual attribute amp.
It would probably be best to accept all variants of the lightning bolt instead of just two of them. That could involved either checking against all 16 possibilities or normalizing the attributes by removing all variant selectors (at least for the purpose of the bolt check).
Both⚡️ and ⚡ look the same, but they're different:
AMP respects the⚡ but rejects ⚡️ , which is confusing since the macOS emoji picker creates ⚡️ , that is, the representation with the Unicode Variation Selector-16.
The AMP validator checks for the presence of the representation without Variation Selector-16, but then replaces it with
amp
, the same happens on the AMP cache.To avoid this confusion, AMP could potentially allow for both,⚡️ and ⚡ , and then just replace them with the textual attribute
amp
.More background on this bug: https://blog.tomayac.com/2019/12/12/same-same-but-different-unicode-variation-selector-16/.
The text was updated successfully, but these errors were encountered: