WP 6.3 Attribute not valid fetchpriority

  • Since the new update to wordpress 6.3 a new error appears in AMP, I removed all the plugins but I could not fix the error, now all my AMP pages appear not valid.

    {
    "code": "DISALLOWED_ATTR",
    "element_attributes": {
    "width": "400",
    "height": "266",
    "src": "https://example.net/wp-content/uploads/2023/08/image.jpg",
    "class": "attachment-post-thumbnail size-post-thumbnail wp-post-image amp-wp-enforced-sizes amp-wp-5ca4bda",
    "alt": "",
    "fetchpriority": "high",
    "data-hero-candidate": "",
    "layout": "intrinsic",
    "data-amp-original-style": "object-fit:cover;"
    },
    "node_name": "fetchpriority",
    "parent_name": "amp-img",
    "type": "html_attribute_error",
    "node_type": "ATTRIBUTE",
    "sources": [],
    "removed": true,
    "reviewed": false
    }
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Weston Ruter

    (@westonruter)

    This is a known issue in AMP core. The fetchpriority attribute is in the process of being added to the validator. Once this is done, we’ll update the plugin with a new release that includes support.

    I have same issue too.

    I wonder when the new update will come; due to this error, none of my AMP pages are showing up.

    Plugin Author Weston Ruter

    (@westonruter)

    @ushancan Please open a separate topic. This fetchpriority attribute validation issue should have nothing to do with your pages not rendering.

    We’ll be updating the AMP plugin as soon as the fetchpriority attribute is added upstream to the AMP spec.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WP 6.3 Attribute not valid fetchpriority’ is closed to new replies.

Tags