Mirrors/gitea

Fork 0

mirror of https://github.com/go-gitea/gitea.git synced 2026-08-21 19:31:13 +02:00

Files

T

History

61be9fcdfa chore: update eslint and stylelint configs and re-sync modern-normalize (#38982 )

- update the vendored `modern-normalize` to v3.0.1
- require descriptions for lint disables in TS and CSS, same as we
already have in Go.
- disable core rules covered by `regexp/*` and `unicorn/*`, and ones
that cannot fire
- stop applying vitest rules to the playwright files in `tests/e2e`
- enable 7 stylelint rules, mostly `no-unknown` and `no-invalid` checks
- drop 2 unnecessary vendor prefixes (safari v17+, chrome v120+)
- look up ids via `querySelector` with `CSS.escape` instead of
`getElementById`
- remove stale doc about `@ts-expect-error`, it's forbidden
- misc dev doc fixes

Every declaration that `modern-normalize` v3 removes was checked against
chromium, webkit and firefox defaults first. The `hr` color and the
`:-moz-focusring` outline are kept as documented deviations, dropping
those does change rendering.

---------

Signed-off-by: silverwind <me@silverwind.io>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>

2026-08-20 09:57:56 -04:00

index.ts

Clean up AppURL, remove legacy origin-url webcomponent (#37090 )

2026-04-03 17:56:31 +00:00

overflow-menu.ts

chore: update eslint and stylelint configs and re-sync modern-normalize (#38982 )

2026-08-20 09:57:56 -04:00

polyfill.test.ts

…

polyfills.ts

Vendor relative-time-element as local web component (#36853 )

2026-03-13 10:43:17 +00:00

README.md

refactor: migrate remaining Vue components to <script setup> (#38752 )

2026-08-06 05:45:31 +00:00

relative-time.test.ts

Introduce ActionRunAttempt to represent each execution of a run (#37119 )

2026-04-23 23:33:41 +00:00

relative-time.ts

Introduce ActionRunAttempt to represent each execution of a run (#37119 )

2026-04-23 23:33:41 +00:00

README.md

Web Components

This webcomponents directory contains the source code for the web components used in the Gitea Web UI.

https://developer.mozilla.org/en-US/docs/Web/Web_Components

Guidelines

These components are loaded in <head> (before DOM body) in a separate entry point, they need to be lightweight to not affect the page loading time too much.
Do not import svg.js into a web component because that file is currently not tree-shakeable, import svg files individually insteat.
Any custom element used inside a .vue file must be added to webComponents in vite.config.ts so Vue does not try to resolve it as a component. That list also covers custom elements from dependencies.