palantir/blueprint

Consider refactoring overlays to use <dialog> element

Open

#5,120 opened on Feb 9, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (2,167 forks)batch import
P2Package: coreStatus: needs proposalType: enhancementhelp wanted

Repository metrics

Stars
 (20,263 stars)
PR merge metrics
 (Avg merge 43d 10h) (27 merged PRs in 30d)

Description

Feature request

The <dialog> element provides a lot of functionality and affordances out of the box. It is supported in all major browsers except IE11, which we are dropping support for in Blueprint v5.0. We should investigate whether migrating our <Overlay> implementation to use this built-in element can reduce our code complexity and maintenance cost.

Related

Contributor guide

Research direction
Investigate the current Overlay component implementation in Blueprint and explore how to replace it with the native <dialog> element, considering accessibility, existing features, and browser support.
Tech stack
typescriptreact
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60