Skip to content

Ask the bug form for the device context that decides visual bugs - #39

Merged
spdotdev merged 1 commit into
mainfrom
feat/bug-form-device-context
Jul 12, 2026
Merged

spdotdev merged 1 commit into
mainfrom
feat/bug-form-device-context

Conversation

@spdotdev

Copy link
Copy Markdown
Owner

Follow-up to #32. No issue to link — this is a process fix.

Why

#32 ("looks different on Pixel and Samsung") turned out not to be a code bug at all: one of the tester's phones has Android's Bold text accessibility setting on and the other doesn't, so the same build renders at different weights. I found that out only after measuring the type on-device, misreading the result, and getting most of the way through replacing the app's variable font with five static files. The control run showed the original font was fine.

The device context that settles this kind of report was never asked for. The form had a free-text "Phone and Android version" box and nothing else — so the two settings that actually decide a visual difference went unreported, and the report was ambiguous about which screenshot came from which phone.

Asking a tester to remember three settings every time is fragile. The form can just ask.

What changes

  • Phone becomes a dropdown — Pixel 7 Pro, Pixel 10, Samsung Galaxy S24, or another phone — with Android version as its own field.
  • "Is Bold text turned on?" — required, with a Not sure option so it can't become a wall. Includes the exact path on Pixel and Samsung, plus the version-proof trick: search Settings for "bold".
  • Font size and display size — optional; "default" is an acceptable answer.
  • "Comparing two phones?" — optional, and the field that would have saved this issue: which screenshot came from which phone, with the settings above for both.

The screenshot, steps, expected-result and build-version fields are untouched.

Validated as GitHub issue-form YAML (parses; all dropdowns and required flags as intended).

The free-text "Phone and Android version" field left the two things that
actually explain a visual difference unasked: whether Android's "Bold text"
is on, and what the font/display size sliders are set to. Both change how
every app renders, so two phones on the same build legitimately look
different — which is all of #32, after it was chased into the type system
first.

Phone becomes a dropdown of the phones in the test group (Pixel 7 Pro,
Pixel 10, Galaxy S24, other), and the form now asks for Bold text, font and
display size, and — when a report compares two phones — which screenshot came
from which, with those settings for both.

Bold text is required, with a "not sure" option so it can't become a wall.
The rest stay optional; a tester who has never touched them can write
"default" and move on.
@spdotdev spdotdev linked an issue Jul 12, 2026 that may be closed by this pull request
@spdotdev
spdotdev merged commit e9c3402 into main Jul 12, 2026
1 check passed
@spdotdev
spdotdev deleted the feat/bug-form-device-context branch July 12, 2026 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Different view on Pixel and Samsung phones

1 participant