JabRef / JabRef/html-to-node

RichTextArea renderer polish

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
3
Forks
1
Avg merge
8h 2m
Merged PRs (30d)
4

Description

Follow-ups for the rich renderer (split from #2, where the adoption evaluation and implementation are documented):

  • RTF/HTML clipboard export via RichTextArea's built-in format handlers
  • Scroll-to-search-hit navigation via TextPos (JabRef: jump the preview to the first <mark> highlight)
  • Semantic theming variables: ship the .rich-text-area structural rules in html-to-node.css against library-defined looked-up colors, so consumers set palette variables instead of skin-internal selectors (interim until the upstream styleable property lands)
  • Hand cursor / underline-on-hover over links

🤖 Generated with Claude Code

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

Start by reading RichTextArea's built-in format handlers and the TextPos navigation entry point, then inspect the structural rules in html-to-node.css. Use the checklist as the completion criteria: clipboard export, search-hit navigation, semantic theming variables, and link hover styling should all be addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, java
Domain
desktop, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.