Compare
Component
Compare · 11 components with a popup

Context Menu, five ways

Open one. Five follow. Each tile runs Context Menu in its own framework and reports the change in its own syntax.

Context Menu docs: demo, examples and API
Frameworks
5
Parts
19
Open now
0 of 5
Events
0

Live

Sync on · one tile drives all five

React

LoadingonOpenChange

Loading React…

Vue

Loading@open-change

Loading Vue…

Svelte

LoadingonOpenChange

Loading Svelte…

Angular

Loading(openChange)

Loading Angular…

Solid

LoadingonOpenChange

Loading Solid…

EventsNo changes yet

No changes yet. Use any tile.

The same example, in each framework

The showcase example for Context Menu, as written in each framework. Lines that only React has are marked.

React · ContextMenu.tsx23 lines only in React
import { ContextMenu } from '@▢▢▢▢/react/context-menu'

const areaStyle = {
  padding: '32px 48px',
  border: '1px dashed var(--demo-border)',
  borderRadius: 12,
  color: 'var(--demo-muted)',
  fontSize: 14,
  userSelect: 'none',
  WebkitUserSelect: 'none',
} as const

export default function ContextMenuExample() {
  return (
    <ContextMenu.Root>
      <ContextMenu.Trigger style={areaStyle}>
        Right click here
      </ContextMenu.Trigger>
      <ContextMenu.Portal>
        <ContextMenu.Positioner>
          <ContextMenu.Popup className="menu">
            <ContextMenu.Item className="menu-item">
              Back
            </ContextMenu.Item>
            <ContextMenu.Item className="menu-item">
              Forward
            </ContextMenu.Item>
            <ContextMenu.Item className="menu-item">
              Reload
            </ContextMenu.Item>
            <ContextMenu.Item className="menu-item">
              Save as...
            </ContextMenu.Item>
          </ContextMenu.Popup>
        </ContextMenu.Positioner>
      </ContextMenu.Portal>
    </ContextMenu.Root>
  )
}
ContextMenu.vue
<script setup lang="ts">
import { ContextMenu } from '@▢▢▢▢/vue/context-menu'

const areaStyle = {
  padding: '32px 48px',
  border: '1px dashed var(--demo-border)',
  borderRadius: '12px',
  color: 'var(--demo-muted)',
  fontSize: '14px',
  userSelect: 'none',
  WebkitUserSelect: 'none',
} as const
</script>

<template>
  <ContextMenu.Root>
    <ContextMenu.Trigger :style="areaStyle"
      >Right click here</ContextMenu.Trigger
    >
    <ContextMenu.Portal>
      <ContextMenu.Positioner>
        <ContextMenu.Popup class="menu">
          <ContextMenu.Item class="menu-item">Back</ContextMenu.Item>
          <ContextMenu.Item class="menu-item">Forward</ContextMenu.Item>
          <ContextMenu.Item class="menu-item">Reload</ContextMenu.Item>
          <ContextMenu.Item class="menu-item">Save as...</ContextMenu.Item>
        </ContextMenu.Popup>
      </ContextMenu.Positioner>
    </ContextMenu.Portal>
  </ContextMenu.Root>
</template>

Measured, per framework

Context Menu in each framework, side by side. Lower is better for size, time and memory. No outside baseline: the frameworks are compared with each other only.

MetricReactVueSvelteAngularSolid
SizeKiB gzip, with core and dom
Openms, median
Closems, median
MemoryMiB after one open and close
Testspassing
Measured
Nov 4 on Apple M3 Max, Chromium 156, 35 runs per framework over 5 page loads. The range under each time is the spread of the per-load medians.
Tests
Context Menu's tests in each framework's suites, jsdom and Chromium together, from the latest run. React runs the React tests on the port; the other four also run the shared behaviour tests.
Sources
reports/size-baseline.json (size), reports/perf.json (shared code, time, memory) and reports/tests-by-component.json (tests).

Same props, five spellings

The ContextMenu.Root props as each framework writes them. A name that differs from React is marked.

React
Props and callbacks have upstream's names and signatures: onCheckedChange(checked, details), onOpenChange(open, details), onValueChange(value, details).
Vue
Props keep upstream's names and can be written in kebab case in a template (:default-checked, :side-offset). Upstream's callbacks are Vue events with the same arguments: checkedChange(checked, details), openChange(open, details), valueChange(value, details).
Svelte
Callbacks are props with upstream's names and arguments: onCheckedChange(checked, details), onOpenChange(open, details), onValueChange(value, details), with details.cancel(), reason and event. Native event props use Svelte's names (onclick, onkeydown).
Angular
Inputs are signal inputs with upstream's names (checked, disabled, nativeButton); boolean inputs also work as bare attributes. Each callback with details is an output named without on: checkedChange, openChange, valueChange.
Solid
Callbacks keep upstream's names and arguments: onCheckedChange(checked, details), with details.cancel() and details.event. Native handlers are camelCase (onClick, onKeyDown), as Solid 2 requires.
Prop · 11ReactVueSvelteAngularSolid
defaultOpenpropdefaultOpendefault-opendefaultOpen[defaultOpen]defaultOpen
openpropopenopenopen[open]open
onOpenChangeeventonOpenChange@open-changeonOpenChange(openChange)onOpenChange
highlightItemOnHoverprophighlightItemOnHoverhighlight-item-on-hoverhighlightItemOnHover[highlightItemOnHover]highlightItemOnHover
actionsRefpropactionsRefactions-refactionsRef[actionsRef]actionsRef
loopFocusproploopFocusloop-focusloopFocus[loopFocus]loopFocus
onItemHighlightedeventonItemHighlightedon-item-highlightedonItemHighlighted(itemHighlighted)onItemHighlighted
onOpenChangeCompleteeventonOpenChangeComplete@open-change-completeonOpenChangeComplete(openChangeComplete)onOpenChangeComplete
disabledpropdisableddisableddisabled[disabled]disabled
orientationproporientationorientationorientation[orientation]orientation
childrenpropchildren#defaultchildrenng-contentchildren