Mateusz Turcza

@Louhike That's almost exactly how it was handled in versions [prior to 3.2.1](https://github.com/mendhak/angular-intro.js/blob/v3.1.3/src/angular-intro.js#L10). Skipping this in later versions made the package unusable with Webpack / TypeScript.

For those who are still using angularjs in 2021, and came across this issue - you can silence this warning with the following hack: ```js Object.defineProperty(angular.element.prototype, 'className', { get() {...

Progress of implementation is tracked in https://github.com/xemlock/htmlpurifier-html5/projects/1

Just to piggyback on this issue, false positives are reported for number literals ending with `0.`, such as: ```js const x = 10.; const y = 1234567890..toFixed(0); ``` Both values...

Hi @bytestream, yes it should suffice. Thanks!

I've just noticed that versions matrix has been modified. So after a bit of thought, I'm in strong favor of adding our own, in-library definition for this attribute, to avoid...

Superseded by #79.

Hi @larsgw, Thanks for bringing that to my attention. At the moment of creating the issue it was not possible to handle `%` character in `\href{}` (and `\url{}`) in a...

Can you provide a minimal reproduction? Are you sure the right config is used? The following code works as expected (which means that self-closing tags are supported correctly): ```php

Yes, exactly! I was testing against `master` branch, that is why it was working fine for me, and wasn't working on latest version pulled from composer. I (still) need to...