On 2/9/2010 11:50, Alistair Leslie-Hughes wrote:
Hi,
Changelog: msxml4: Prefer to use the native version
Best Regards Alistair Leslie-Hughes
Why do you need this?
On 9/02/2010 9:21 PM, Nikolay Sivov wrote:
On 2/9/2010 11:50, Alistair Leslie-Hughes wrote:
Hi,
Changelog: msxml4: Prefer to use the native version
Best Regards Alistair Leslie-Hughes
Why do you need this?
If a program install msxml4 as part of it install process, it should use the native one, since the current implementation doesn't support any interfaces of msxml4. This way users dont have to override msxml4 via winecfg.
Best Regards Alistair Leslie-Hughes
On 2/9/2010 16:04, Alistair Leslie-Hughes wrote:
On 9/02/2010 9:21 PM, Nikolay Sivov wrote:
On 2/9/2010 11:50, Alistair Leslie-Hughes wrote:
Hi,
Changelog: msxml4: Prefer to use the native version
Best Regards Alistair Leslie-Hughes
Why do you need this?
If a program install msxml4 as part of it install process, it should use the native one, since the current implementation doesn't support any interfaces of msxml4. This way users dont have to override msxml4 via winecfg.
What specific features are your referring? msxml3 isn't complete and has a lot of problems, but it's considered as ready, it's enough for msxml4 to just forward to it. If there's a real problem let's add another forward (as DOMDocument40 already does).
Best Regards Alistair Leslie-Hughes
What specific features are your referring? msxml3 isn't complete and has a lot of problems, but it's considered as ready, it's enough for msxml4 to just forward to it. If there's a real problem let's add another forward (as DOMDocument40 already does).
After some more investigate the crash is caused by fixme:msxml:domdoc_setProperty Unknown property L"SelectionNamespaces" XPath error : Undefined namespace prefix xmlXPathEval: evaluation failed
Which is already covered by a bug already.
Best Regards Alistair Leslie-Hughes
-
Alistair Leslie-Hughes -
Nikolay Sivov