Permalinks only really work for dark themes

Open
#1,419 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust, zsh
Domain
cli

Research direction

Reproduce the issue with echo '\033[30mHello, World!\033[m' in a light theme, then compare the local preview with the permalink at the reported URL. Done means permalink output remains readable on a light background or provides a documented theme/background choice.

Written by the indexing model from the issue text.

Description

area:ui-framework bug needs-info ready-to-implement triaged
Discord username (optional)

fabjan#6411

Describe the bug
I use a light theme and some programs (e.g. [lsd]) which output black text, not just foreground.

When I create a permalink it shows up as black text on a black background: https://app.warp.dev/block/mAXXTBrDlSqD9I8yLbEOUz

[lsd]: https://github.com/Peltoche/lsd
To Reproduce

Steps to reproduce:

  1. Switch to a light theme (optional)
  2. Run echo '\033[30mHello, World!\033[m'
  3. Create a permalink (notice how the preview looks fine)
  4. View the permalink

The problem is not related to the light theme itself, but without it the text will look bad locally as well as in the permalink and make no sense.

Expected behaviour
I would expect the permalink to either:

A. Use the theme it was created from
B. Have a view that lets users pick a theme
C. Let users pick a white or black background

Since themes can have background images, maybe alternative A is too much to expect.
Screenshots

No response

Operating System

MacOS

OS Version

12.4

Shell Version

zsh 5.8.1 (x86_64-apple-darwin21.0)

Additional context

No response

Warp Internal (ignore): linear-label:24888f54-df93-45d5-9bdd-e38f740cac19

No response

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

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.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.