Crash report: `ReferenceError: Can't find variable: ResizeObserver`

URL

https://app.uniswap.org/#/swap?outputCurrency=0xf4d2888d29d722226fafa5d9b24f9164c092421e&chain=mainnet

swap state

{
  "INPUT": {
    "currencyId": "ETH"
  },
  "OUTPUT": {
    "currencyId": "0xf4d2888d29D722226FafA5d9B24F9164c092421E"
  },
  "independentField": "INPUT",
  "typedValue": "1",
  "recipient": null
}

Error

ReferenceError: Can't find variable: ResizeObserver

Stacktrace

@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:2805220
@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:2804856
@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:2804579
rs@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:3055158
Su@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:3075371
su@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:3067628
su@[native code]
Hi@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:3008354
@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:3074167
_u@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:3074170
iu@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:3066630
iu@[native code]
S@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:3092483
M@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:3093017
@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:2822437
c@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:2822551
n@https://app.uniswap.org/static/js/3.03e22df4.chunk.js:2:2821497

Device data

{
  "ua": "Mozilla/5.0 (iPhone; CPU iPhone OS 15_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6 Mobile/15E148 Safari/604.1",
  "browser": {
    "name": "Mobile Safari",
    "version": "15.6",
    "major": "15"
  },
  "engine": {
    "name": "WebKit",
    "version": "605.1.15"
  },
  "os": {
    "name": "iOS",
    "version": "15.6"
  },
  "device": {
    "vendor": "Apple",
    "model": "iPhone",
    "type": "mobile"
  },
  "cpu": {}
}

Reproduce the crash at the supplied swap URL using Mobile Safari 15.6 on iOS 15.6, then use the reported ResizeObserver stack trace as the starting point for locating the failing frontend path. Done means the swap page no longer crashes in that environment while preserving the reported swap state.