Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Inline-block may cause Chrome's built-in search to fail to match the corresponding content

Open Beginner friendly
#101 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
62/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
css
Domain
frontend

Research direction

Start at src/styles/index.css around line 77 and inspect the .diff-code-edit display rule. Reproduce the provided rendered markup in Chrome and use Ctrl+F to search for "onUpdate". Done means the corresponding split inline code is found by the browser's built-in search without disrupting the diff rendering.

Written by the indexing model from the issue text.

Description

pinned

https://github.com/otakustay/react-diff-view/blob/72868c24b781b26671eb51b94e203a5c9ccf14e3/src/styles/index.css#L77

Assuming that the rendered code is like this

<td class="diff-code diff-code-insert" style="user-select: auto;">
    <span class="diff-code-edit">
        <span class="token function">onU</span>
    </span>
    <span class="token function">pdat</span>
    <span class="diff-code-edit">
        <span class="token function">e</span>
    </span>
</td>

When I use ctrl+f to search for "onUpdate" on the webpage, I cannot find the above one because the display of .diff-code-edit is inline-block.

I think display: inline-block should be changed to display: inline.

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

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 otakustay/react-diff-view

All issues in otakustay/react-diff-view

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.