All components · Category: Content and utilities

World clock

Analog and digital clocks for time zones, from the visitor's own clock.

Analog and digital clocks for the time zones you choose, plus the visitor's own, read from the device's clock and written in the visitor's language, with a day or night mark. Nothing is sent anywhere, and reduced motion drops the second hand.

Try it

<world-clock>

ViewPreviewCodeCSS

world-clock: Analog and digital clocks for time zones, from the visitor's own clock. A picture of the real component, drawn from its own code. The controls change the picture and the code beside it; nothing here is sent or stored.

Generated from the component's manifest and the values above.

index.html

<world-clock locale="en"></world-clock>

Add the site's Taggor script once; the component appears when it loads.

taggor-component.js

const element = document.createElement("world-clock");
element.setAttribute("locale", "en");
document.body.append(element);

Add the site's Taggor script once; the component appears when it loads.

WorldClock.tsx

export function WorldClock() {
  return <world-clock locale="en" />;
}

Add the site's Taggor script once; the component appears when it loads.
React 18 sends every prop of a custom element as a text attribute.

WorldClock.tsx

export function WorldClock() {
  return <world-clock locale="en" />;
}

Add the site's Taggor script once; the component appears when it loads.
React 19 sets a property when the element already has it, an attribute otherwise.

src/WorldClock.vue

<template>
  <world-clock locale="en" />
</template>

vite.config.ts

import vue from "@vitejs/plugin-vue";
import { defineConfig } from "vite";

export default defineConfig({
  plugins: [
    vue({
      template: {
        compilerOptions: {
          isCustomElement: (tag) => tag === "world-clock",
        },
      },
    }),
  ],
});

Add the site's Taggor script once; the component appears when it loads.
vite.config.ts tells Vue that this tag is not a Vue component.

src/app/world-clock.component.ts

import { Component, CUSTOM_ELEMENTS_SCHEMA } from "@angular/core";

@Component({
  selector: "app-world-clock",
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <world-clock locale="en"></world-clock>
  `,
})
export class WorldClockComponent {}

Add the site's Taggor script once; the component appears when it loads.
The component declares CUSTOM_ELEMENTS_SCHEMA.

src/TaggorComponent.svelte

<world-clock locale="en"></world-clock>

Add the site's Taggor script once; the component appears when it loads.

How an agent gets a component like this onto a site:

taggor checktaggor publish

The CSS variables the component exposes, set the way a customer's page would.

styles.css

world-clock {
  --wc-radius: 16px;
}

Props

Props of the component, read from its manifest
Prop	Type	Default	What it does
zones	list	none	IANA time zones to show, such as Asia/Tokyo (invalid ones are skipped).
hideLocal	boolean	false	Hides the visitor's own clock.
locale	pt-BR \| en	en	–

Prop names and descriptions are the component's own, in English, as its author wrote them.

Events

This component fires no event.

Build one with your agent

Paste this into your agent. It asks you before it signs in, pays or goes further than checking and publishing.

Build me a Taggor component like "World clock" (world-clock): Analog and digital clocks for time zones, from the visitor's own clock. Fetch https://taggor.dev/agent-setup/prompt.md and follow its instructions to set me up for Taggor. Ask me before you sign in, create an account, accept terms, pay for anything or type a secret. Check it with `taggor check` and publish it with `taggor publish`, and stop there. Do not promote it to production, attach it to a site, roll back anything or use --yes, --force or --force-drop-invalid unless I ask for exactly that in this conversation.

Related components

Unit converter<unit-converter>
Launch countdown<launch-countdown>