guardian / guardian/cql

Adding a chip when something is selected doesn’t replace this something

Open
#115 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
4
Forks
1
PR merge metrics
No merged PRs in 30d

Description

This is only to try to mimic usual text editing behaviour (when typing/pasting over selected text replaces it). It has minim al real-world impact.

1. select some text
2. press `+` to add a chip

Actual: chip is added BEFORE selected bit in Firefox. In Chrome it’s worse:
Expected (?): chip replaces selected bit

Firefox:

![Image](https://github.com/user-attachments/assets/32732be8-86b2-45c1-b8c1-0494c57de7f0)

Chrome:

![Image](https://github.com/user-attachments/assets/9ee4d81e-5430-4cc8-9a1d-25d788a64a5e)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by selecting text and pressing `+` in Firefox and Chrome, then compare the insertion behavior with the expected replacement behavior. Identify the chip insertion entry point and verify that the selected text is replaced consistently in both browsers.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.