castarco, 2 months ago So... I'm... surprised. It's obviously "not a bug", because both #Chrome and #Firefox behave the same way. I didn't expect this, that a standard browser API would be so broken (I suppose that this is because of and old rotten spec?) Anyone around who knows why they left DOMParser behave this way? #infosec #security » const parser = new DOMParser() » const html =
So... I'm... surprised.
It's obviously "not a bug", because both #Chrome and #Firefox behave the same way.
I didn't expect this, that a standard browser API would be so broken (I suppose that this is because of and old rotten spec?)
Anyone around who knows why they left DOMParser behave this way?
DOMParser
#infosec #security
» const parser = new DOMParser() » const html =
jonny, 2 months ago @castarco Wait that looks right to me? How should it behave?
@castarco Wait that looks right to me? How should it behave?
Add comment