oneOf rendering in path section doesn't work properly

Q&A (please complete the following information)

• OS: Windows 10
• Browser: Microsoft Edge
• Version: 103.0.1264.71
• Method of installation: N/A
• Swagger-UI version: https://editor.swagger.io/
• Swagger/OpenAPI version: OpenAPI 3.0

Content & configuration

Example Swagger/OpenAPI definition:

openapi: 3.0.3
info:
  title: component-test
  description: Components inside PATH section are not rendered properly
  version: 1.0.0
paths:
  /test/example:
    post:
      requestBody:
        content:
          application/json:
            schema:
              "$ref": '#/components/schemas/ListPerson'
      responses:
        '201':
          description: OK

components:
  schemas:
    ListPerson:
      type: object
      properties:
        elements:
          items:
            "$ref": '#/components/schemas/Person'
          type: array

    Person:
      type: object
      properties:
        name:
          description: name
          type: string
          readOnly: true
        age:
          format: int32
          description: age
          type: integer
          readOnly: true
      oneOf:
        - $ref: '#/components/schemas/Dog'
        - $ref: '#/components/schemas/Cat'
    Dog:
      type: object
      properties:
        name:
          description: name
          type: string
          readOnly: true
    Cat:
      type: object
      properties:
        name:
          description: name
          type: string
          readOnly: true
    
    

Swagger-UI configuration options:

• Not available

Describe the bug you're encountering

To reproduce...

Steps to reproduce the behavior:

1. Go to 'Path Schema section'
2. Click on 'ListPerson then click on elements'
3. See error: missing some properties in Person scheme

Expected behavior

Expected right request body to be shown with all the properties
Note: In the schema section at the bottom of the page the Person object is displayed correctly

Screenshots

Additional context or thoughts

Thank you!

Reproduce the issue in editor.swagger.io using the supplied OpenAPI 3.0 definition, then inspect the Path Schema section for ListPerson → elements and compare it with the correctly rendered Person schema below. Done means the request body shows all Person properties, including those involved in the oneOf schemas.