Pop out window renders too small in Safari (title bar height eats into content area)

Open
#1,162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend, web-dev

Research direction

Start by locating the Pop Out entry point and the code that calculates the new window size. Reproduce the issue in Safari and Firefox with the same splits and layout, then verify that the pop-out content area is the same size as the main window's splits view in both browsers.

Written by the indexing model from the issue text.

Description

The pop out window renders noticeably smaller in Safari than it does in Firefox. It looks like the difference is that Firefox doesn't include the height of the title bar in the window open size but Safari does.

Image

Repro Steps

  1. Open one.livesplit.org in both Firefox and Safari.
  2. Load the same splits/layout in both.
  3. Click "Pop Out" in both.

Expected behavior

The pop-out window's content should render at roughly the same size in both browsers, matching the size of the main window's splits view.

Actual behavior

In Safari, the pop-out window's content (text, rows, header) is noticeably smaller than in Firefox — see attached screenshot (Firefox on the left, Safari on the right, same splits/layout). I believe this is because in Firefox the content size is the same as the content size from the main window but in Safari it's the full window size that matches, reducing the content size by the height of the title bar.

Environment

  • macOS 26.6.2 (25G83)
  • Safari 26.6.2 (21624.5.1.11.3)
  • Firefox 154.0.1
Dominant language
TypeScript
Stars
301
Forks
55
Avg merge
8m
Merged PRs (30d)
1

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.

More from LiveSplit/LiveSplitOne

All issues in LiveSplit/LiveSplitOne

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.