fix(geo): tolerate singular view transform when chart size is zero

[laodouya]

Brief Information

This pull request is in the type of:

• bug fixing
• new feature
• others

What does this PR do?

Fixes the TypeError: Cannot read properties of null (reading '0') thrown by every geo/map chart whose size is 0×0 (e.g. a container hidden with display: none) — a regression introduced in 6.1.0.

Fixed issues

• [Bug] Geo/map chart crashes with "Cannot read properties of null (reading '0')" when chart size is 0×0 (regression in 6.1.0) #21706: [Bug] Geo/map chart crashes with "Cannot read properties of null (reading '0')" when chart size is 0×0 (regression in 6.1.0)

Details

Before: What was the problem?

With a zero-sized view rect the overall view transform has zero scale, so its determinant is 0 and zrender's matrix.invert() returns null without writing out. viewCoordSysUpdateOverallTrans passed that return value to legacyCopyOverallTrans unguarded, where matrixCopy(target.invTransform, null) dereferences null[0].

Before 6.1.0, the equivalent code (View.prototype._updateTransform) ignored invert()'s return value — invTransform simply kept its previous contents — so zero-sized geo charts were tolerated. Since the failure happens inside the update pipeline, in real apps it re-throws on every animation frame until the chart is disposed.

After: How does it behave after the fixing?

legacyCopyOverallTrans skips the inverse copy when matrixInvert returned null, keeping the last inverse — the same semantics as before 6.1.0 (and the same as the existing matrixInvert(viewInner.mtRawInv, mtRaw) call in this file, whose return value is likewise ignored). Zero-sized geo/map charts render without throwing; a regression unit test is included (fails before the fix, passes after).

Document Info

One of the following should be checked.

• This PR doesn't relate to document changes
• The document should be updated later
• The document changes have been made in apache/echarts-doc#xxx

Misc

Security Checking

• This PR uses security-sensitive Web APIs.

ZRender Changes

• This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs

N.A.

Merging options

• Please squash the commits into a single one when merging.

Other information

[echarts-bot]

Thanks for your contribution!
The community will review it ASAP. In the meanwhile, please checkout the coding standard and Wiki about How to make a pull request.

Please DO NOT commit the files in dist, i18n, and ssr/client/dist folders in a non-release pull request. These folders are for release use only.

[echarts-bot]

Congratulations! Your PR has been merged. Thanks for your contribution! 👍