Root cause:
1. In the existing implementation if userAgent string contains safari, then we are skipping creating soap document element with default namespace. And istead the namespace is added later using setAttribute method.
2. In chrome 137, as per https://issues.chromium.org/issues/415370691#comment16, the namespace attribute will be removed if it is not created with createElementNS.

Solution: createElementNS is supported by almost all the browsers now including safari. We should avoid using setting namespace explicitly and add it using createElementNS while creating element.