Change strategy type

[SebastianStehle]

I have no idea why this needs to be changed, but it only works when the strategy type is Specialized.

Types of Changes

Prerequisites

Please make sure you can check the following two boxes:

• [ ] I have read the CONTRIBUTING document
• [ ] My code follows the code style of this project

Contribution Type

What types of changes does your code introduce? Put an x in all the boxes that apply:

• [ ] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
• [ ] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] My change requires a change to the documentation
• [ ] I have updated the documentation accordingly
• [ ] I have added tests to cover my changes
• [ ] All new and existing tests passed

Description

[Place a meaningful description here.]

[egil]

The reason is related to the order in which the compares are executed. Specialized comparisons are executed after the generalized ones. We also have another issue. In the current implementation these two HTML elements would be considered equal: <input /> and <br />. That's obviously not correct.

After sleeping on it, I want to change the solution to this entirely, and instead make the element compare configurable, such that you can pass a boolean to it to make it enforce tag closing. Ill close this issue and push an update that would show up as a preview release in an hour or so.

[SebastianStehle]

Good to know. It is a little bit unexpected because usually just the order defines how filters are executed (see .NET Middleware).