From 0b5f09bc15cf56db7898c6f8ef5986dca0720d1b Mon Sep 17 00:00:00 2001 From: yyh Date: Sat, 9 May 2026 12:45:13 +0800 Subject: [PATCH] docs(web): remove legacy tooltip migration references --- packages/dify-ui/README.md | 2 +- web/docs/overlay-migration.md | 4 ---- web/eslint.constants.mjs | 8 -------- 3 files changed, 1 insertion(+), 13 deletions(-) diff --git a/packages/dify-ui/README.md b/packages/dify-ui/README.md index fd75042d76..c78faede89 100644 --- a/packages/dify-ui/README.md +++ b/packages/dify-ui/README.md @@ -103,7 +103,7 @@ See `[web/docs/overlay-migration.md](../../web/docs/overlay-migration.md)` for t - Use `Tooltip` only for short, non-interactive visual labels. The trigger must already have visible text or an `aria-label`; the tooltip is not the accessible name and must not contain links, buttons, forms, or structured prose. - Use `Popover` for explanatory content, long text, rich layout, or anything users may need to reach on touch or with assistive technology. In `web/`, the `Infotip` wrapper is the preferred pattern for a `?` help glyph backed by `Popover`. -- Do not copy legacy tooltip offsets into migrated call sites. Pick a `placement` and let the primitive own spacing. +- Pick a `placement` and let the primitive own spacing. Avoid per-call-site offsets unless the component API explicitly needs a measured layout exception. - When passing a Base UI trigger `render` prop, render a real `