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

Orangutan SVG (svg/emoji_u1f9a7.svg) not rendering correctly #363

Closed
jdherg opened this issue Sep 22, 2021 · 2 comments · Fixed by #366
Closed

Orangutan SVG (svg/emoji_u1f9a7.svg) not rendering correctly #363

jdherg opened this issue Sep 22, 2021 · 2 comments · Fixed by #366
Assignees

Comments

@jdherg
Copy link

jdherg commented Sep 22, 2021

The orangutan SVG (svg/emoji_u1f9a7.svg) is broken, in what looks to be the same way it was broken before being fixed by 24a33c4 -- there's a reference to a jpg that doesn't actually exist.

@jdherg jdherg changed the title Orangutang SVG (svg/emoji_u1f9a7.svg) not rendering correctly Orangutan SVG (svg/emoji_u1f9a7.svg) not rendering correctly Sep 22, 2021
@anthrotype
Copy link
Member

Yes, I can confirm the orangutan has a badly broken arm, it looks like this when I load the emoji_u1f9a7.svg in Chrome

image

Inspecting it in a text editor reveals that it suddenly grew an unsupported <image> element that references an external (missing) JPEG file:

<image style="overflow:visible;" width="139" height="153" xlink:href="72D8D7011A0AC19D.jpg"  transform="matrix(0.48 0 0 0.48 59.52 -1.44)"></image>

Removing the line containing the <image> element still leaves the arm broken like so:

image

According to git blame the commit that first introduced this was 9bdaf2e from 11 May this year (5 montsh ago)

@anthrotype
Copy link
Member

A previous commit 24a33c49 on main from November 2020 was meant to fix the orangutan (and two others) that had been broken in a similar way by an even older commit 31f714f3.
It looks like 9bdaf2e involutarily reverted the orangutan to a broken state (with the arm pointing to a missing JPG image).

I suggest we revert it again to the good state from 24a33c4 -- I'll send a PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants