-
Notifications
You must be signed in to change notification settings - Fork 64
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
Object tag is not detected as html #33
Comments
Fixed in 1.0.0, please update, no breaking changes introduced. It's just faster with few minor bugs fixes. |
Great, thank you for your fast response! It's working :) |
Sorry, but I think I've stumbled upon a related issue. The
Line 35063 in my vendor file is pointing to line 34 in your fix.js: Yes, that totally make no sence, but I was not able to find what really breaks UglyfyJs. Do you have an idea? |
UglifyJS doesn't play very well with ES6, it's my bad though, I should have compiled to ES5 since this kind of issues is still expected from build tools. I've released quick fix For future references, if you faced such issues with UglifyJS building other libraries, then you can transpile the source via babel or buble using their respective webpack loaders. Please update and let me know if any error shows up. |
Hi Alex, |
Thanks 😃! I'm actually really grateful for these issue reports since I'm using this library on production. |
Hi Alex,
I'm using emojis which are included with an
<object>
tag. For some reason anchorme does not detect this as html and does mistakenly process the url within the data attribute.I suppose it has something to do with
data="https...
because when I change it tosrc="https...
, the<object>
tag will be recognized and not break any more - but of course then the emoji will not show up.Thanks in advance for any help :)
The text was updated successfully, but these errors were encountered: