Bug 279356 – TypeError: Attempted to assign to readonly property - extractFilteredSchemaValuesFromMicroData

• Component: DOM
• Status: RESOLVED MOVED

Using Schema.org LocalBusiness #Example1 code with the microdata (https://schema.org/LocalBusiness#eg-0004)on a page makes Safari 17.5 with iPhone iOS 17 moo in the dev console with the following message: "TypeError: Attempted to assign to readonly property". 

Linked to native extractFilteredSchemaValuesFromMicroData and extractSchemaValuesFromSchemaOrg methods. 

This was reported on a real iPhone from a customer and reproduced with Xcode Simulator.

If needed here is a codesandbox (but copying example from schema.org is enough): https://codesandbox.io/p/sandbox/5tmwpr

Error has been reported multiple time since a couple of months at least here: https://github.com/odoo/odoo/issues/162145

* https://schema.org/LocalBusiness#eg-0004

Error has been narrowed it down. See https://github.com/odoo/odoo/issues/162145#issuecomment-2074417723

The error appears with PostalAddress schema with:

```
<div itemprop="address" itemscope itemtype="https://schema.org/PostalAddress">
    <span itemprop="streetAddress">1901 Lemur Ave</span>
    <span itemprop="addressLocality">Sunnyvale</span>,
    <span itemprop="addressRegion">CA</span> <span itemprop="postalCode">94086</span>
  </div>
```

[Radar WebKit Bug Importer]

<rdar://problem/136069620>

I am running into the same issue, it seems like its a webkit/safari issue since its only there on safari.

There is definitely an error with how schema is handled here.

I hope it will be fixed soon.

We encountered the same issue and resolved it by adding the following HTML tag:


<span itemprop="telephone">123456789</span>

[Ryosuke Niwa]

Created attachment 473006 [details]
Test

[Ryosuke Niwa]

This is a bug in Safari. Consequently, the fix needs to be made in Safari, not WebKit.

[Ryosuke Niwa]

This bug is fixed in macOS Sequoia 15.4 beta.

[Brent Fulgham]

The fix for this needed to be made outside of the WebKit Open Source project. That fix shipped in iOS/iPadOS 18.4, and macOS Seqoia 15.4.