Opened on 09/17/2015 at 07:30:18 AM
Closed on 10/05/2015 at 05:29:24 PM
#3089 closed defect (duplicate)
Misplaced borders of share and donate section on first run page with smaller viewport sizes
| Reported by: | sebastian | Assignee: | |
|---|---|---|---|
| Priority: | P4 | Milestone: | |
| Module: | User-Interface | Keywords: | goodfirstbug |
| Cc: | greiner, saroyanm | Blocked By: | |
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | yes | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by sebastian)
Environment
Chrome 45, other browsers might be effected as well
How to reproduce
- Open firstRun.html
- Resize the window down to the size were the donate and share section wraps
Observed behaviour
As seen in share.png, the borders are misplaced.
Expected behaviour
The vertical borders should be removed when the donate and share section wraps. Optionally, a horizontal border should be used instead.
Attachments (1)
Change History (8)
Changed on 09/17/2015 at 07:30:45 AM by sebastian
comment:2 Changed on 09/17/2015 at 07:32:25 AM by sebastian
- Summary changed from Misplaced borders of share and donate section on first run page with smaller view port sizes to Misplaced borders of share and donate section on first run page with smaller viewport sizes
comment:3 Changed on 09/17/2015 at 07:49:29 AM by greiner
- Description modified (diff)
- Keywords goodfirstbug added
- Priority changed from Unknown to P4
- Ready set
comment:4 follow-up: ↓ 5 Changed on 09/17/2015 at 08:02:20 AM by sebastian
- Description modified (diff)
I didn't say it would be related to #3031. And there is no urgency to fix this for the upcoming release. Though, I think it's rather a P3 than a P4.
comment:5 in reply to: ↑ 4 Changed on 09/17/2015 at 08:14:01 AM by greiner
Replying to sebastian:
I didn't say it would be related to #3031.
That wasn't addressed to you. It's a general note for anyone seeing this ticket.
And there is no urgency to fix this for the upcoming release. Though, I think it's rather a P3 than a P4.
It's a minor cosmetic issue that doesn't affect anything on the page.
comment:6 Changed on 09/17/2015 at 08:18:42 AM by sebastian
From the TracGuide:
P3 = We definitely want this, but it's not a priority.
P4 = We wouldn't mind having this, but it's unlikely to get done by the core team. Patches are welcome.
Since this is definitely a bug, that is visible to some users, I'd say "we definitely want this", though it might not be a priority. That is literally the definition of P3.
Note that this is unrelated to the recent changes from #3031. See also #2018 for further optimizations for smaller screens.