ov-player

src/ov-player.js

LIFTED FROM demo/player.html

Attributes

Properties

READ-ONLY PROPERTIES

report

Events

Using it

import 'overscan'
import 'overscan/overscan.css'
import 'overscan/src/player.css'
import 'overscan/src/player-icons.css'

<ov-player
  label="TEST CARD"
  controls="icons"
  demo
  style="inline-size:100%"
>
  <video
    playsinline
    muted
    preload="metadata"
    src="../demo/media/testcard.mp4"
  >
    <track
      kind="captions"
      srclang="en"
      label="English"
      src="../demo/media/captions.vtt"
    >
    </video>
  </ov-player>

import { OvPlayer } from 'overscan/react'

<OvPlayer
  label="TEST CARD"
  controls="icons"
  media={data}
  onPlayer={handler}
/>

import { OvPlayer } from 'overscan/vue'

<OvPlayer
  label="TEST CARD"
  controls="icons"
  :media="data"
  @player="handler"
/>

import OvPlayer from 'overscan/svelte/OvPlayer.svelte'

<OvPlayer
  label="TEST CARD"
  controls="icons"
  media={data}
  onplayer={handler}
/>

The CSS is a separate import in every framework. A single element can be imported on its own instead of the whole kit: import 'overscan/src/ov-chart.js'

A reading is set as a PROPERTY, never an attribute. An attribute is a string, so an array cannot survive one and a null arrives as the word "null", which the protocol would read as a value rather than a dropout.

Every ov: event is bound with addEventListener. The colon has no declarative spelling in Svelte 5, where the on: directive is gone and "onov:commit" is not an identifier, nor in JSX. Vue can bind it.

The wrapper applies attributes ITSELF and hands the framework nothing but a ref. All three frameworks set a prop as a property when the name exists on the element, and this kit has 72 getter-only properties across 39 elements. Assigning one throws, and in React it does not degrade: the whole tree fails to render. 13 elements have a getter-only name that is also a real attribute (at, bearing, digits, duration, floor, fov, fresh, hold, lat, lon, period, pitch, range, ring, rings, span, step, sweep, sweeps, traces, value), which are the ones a reader would naturally pass in markup.