Garret Wilson

From examining the code visually, I would suggest that the following in `W3CDom` might fix this bug. Of course we wouldn't know without running regression tests. (I haven't looked at...

You can assign me to this ticket. I've already started working on it.

Looks like several unit tests particularly in `W3CDomTest` are breaking. This is because the unit tests are simply wrong. For example: ``` org.opentest4j.AssertionFailedError: expected: but was: at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151) at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)...

This is almost finished, but I need some clarification about usage of `W3CDom.asString(Document doc)` and `W3CDom.asString(Document doc, @Nullable Map properties)`. This is used in a lot of the tests to...

I went with the assumption that you want `W3CDom.asString()` to continue providing "clean" HTML5 output and not showing a `xmlns` default namespace attribute. The workaround is a bit of a...

Is anyone still working on this library and approving submitted bug fixes? I haven't received any feedback on the pull request.

Thank you, @ajarmoniuk . It's really so nice to see this project is getting quick and useful responses. I sincerely appreciate it. Have a good weekend.

It's not surprising that at one time Maven created some reasonable, internally consistent versioning schema, and it is notable and commendable that Maven actually created a specification for this at...

Let me ask you this question: looking at Maven Central, does it appear that the authors of `javax.faces:javax.faces-api` intended the `-pfd` suffix to be interpreted as Maven interprets it? Or...

> Time of the release does not participate in the process. Only version string. I did not assert that the time of release participates in the comparison process or that...