Taylor Southwick

Yes, but I'm still confused as to what you are looking for. That `RemoveMalformedHyperlinksRelationshipErrorHandler` you're using is a test one, and by no means is it expected to be used...

We can probably make the RelationshipErrorHandler handle this kind of thing, but it doesn't appear to out of the box. I'm fairly busy right now and can't investigate the design...

There appears to be a memory leak here in the .NET Standard version of the library.

I was able to repro this issue outside of the DocumentFormat.OpenXML SDK using just the BCL. I've logged an issue at dotnet/corefx to see what the issue is.

This is something that needs to go into .NET itself - I've tried multiple ways to shim it at our layer and have not been able to get around it....

I already had thought about moving the part loading to its own feature to encapsulate the logic there. Once that is done, it would be much easier to enable this...

That's the beautify of the "Features" infrastructure - things can be opted in to for experimental stuff. Once #1294 is completed, it will be much easier (currently much of this...

Closing for now for no movement. Still not sure we want to enable this in the repo

I'd like to get this fixed (at least a work around) for v3.0. I've created a set of abstractions that allow for more control over things and I *think* we...

Unfortunately, I wasn't able to get it to work and had other priorities. I'll move this to v3.1 to see what can be done