Opened 10 years ago
Closed 7 years ago
#38405 closed defect (bug) (worksforme)
Twenty Seventeen: Galaxy Note 2 rendering issue on image header
| Reported by: | karmatosed | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Bundled Theme | Version: | |
| Severity: | normal | Keywords: | needs-testing has-screenshots |
| Cc: | Focuses: |
Change History (8)
This ticket was mentioned in Slack in #core by helen. View the logs.
10 years ago
#3
@
10 years ago
- Milestone 4.7 → Future Release
I was able to reproduce this in Browserstack on the stock browser that it comes with... Since it's an older device, I'm going to punt this ticket to a future release, but hopefully, we can get the content rendering okay in an old browser like this one.
This ticket was mentioned in Slack in #core by jeffpaul. View the logs.
10 years ago
#6
@
10 years ago
- Milestone 4.7 → Future Release
Per @karmatosed in today's bug scrub in #core, this was punted during an earlier conversation so updating the milestone accordingly.
#7
@
7 years ago
- Keywords needs-testing has-screenshots close added; dev-feedback removed
I just tested this a bit and was unable to reproduce the issue. How I tried:
- Chrome (MacOS) with developer tools and Galaxy Note II screen dimensions.
- Firefox (MacOS) with developer tools and Galaxy Note II screen dimensions.
- Browserstack with Chrome on Galaxy Note 3
- Browserstack with default browser on Galaxy Note 3
The Galaxy Note 2 was no longer available when I logged into Browserstack.
I feel like I saw saw a similar report come through that fixed this issue under other conditions. It's possible that this was fixed.
I am going to mark as close pending someone with the actual device verifying it has been fixed.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)

Flagging as dev-feedback as I'm not sure we want to support this.