You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I initially ran into this on Yahoo (web and Android), but upon further testing I found a similar behaviour on Gmail Android with a non-Gmail account.
Both Yahoo and Gmail attempt to remove HTML comments. However, Yahoo partially removes HTML comments if -> (single dash) is within the comment, while GANGA (Android) partially removes HTML comments if 2 occurrences of -> is within the comment. This happens even if the HTML comment is technically valid.
Optionally, text, with the additional restriction that the text must not start with the string ">", nor start with the string "->", nor contain the strings "", or "--!>", nor end with the string "<!-".
Yahoo
The following is a valid HTML comment, however Yahoo assumes it ends at ->:
<!-- some comment -> text starting here is visible on Yahoo-->
GANGA
The following is also a valid HTML comment, however GANGA (Android at least) assumes it ends at the second ->:
<!-- another comment -> here -> text starting here is visible on GANGA-->
The text was updated successfully, but these errors were encountered:
I initially ran into this on Yahoo (web and Android), but upon further testing I found a similar behaviour on Gmail Android with a non-Gmail account.
Both Yahoo and Gmail attempt to remove HTML comments. However, Yahoo partially removes HTML comments if
->
(single dash) is within the comment, while GANGA (Android) partially removes HTML comments if 2 occurrences of->
is within the comment. This happens even if the HTML comment is technically valid.HTML comments syntax
https://html.spec.whatwg.org/multipage/syntax.html#comments
Yahoo
The following is a valid HTML comment, however Yahoo assumes it ends at
->
:GANGA
The following is also a valid HTML comment, however GANGA (Android at least) assumes it ends at the second
->
:The text was updated successfully, but these errors were encountered: