Open
Bug 1628978
Opened 5 years ago
Updated 5 years ago
AS - Search button border overlaps with holding container border
Categories
(Firefox :: New Tab Page, defect, P3)
Firefox
New Tab Page
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | wontfix |
firefox75 | --- | wontfix |
firefox76 | --- | fix-optional |
firefox77 | --- | fix-optional |
People
(Reporter: cfogel, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
image/png
|
Details |
Affected versions
- 77.0a1 (2020-04-09), 76.0b2, 75.0;
Affected platforms
- macOS 10.15, Windows 8.1/10, Ubuntu 18.04;
Steps to reproduce
- Launch Firefox; *for nightly set browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar to false
- Click and hold on the Arrow Button for Search (activity stream one not awesomebar/searchBar)
Expected result
- borders and shadows properly contained;
Actual result
- on hover the button exceeds the border;
- on click the border button is over the border for search section;
Regression range
- First bad: 2017-09-29;
- Last good: 2017-09-28;
- Pushlog: URL;
- Potential regressor: 1403215 seems a likely candidate, more or less seems like an oversight after changing from implementation with full colours;
Additional notes
- attached screenshot with the issue.
Reporter | ||
Updated•5 years ago
|
Has Regression Range: --- → yes
Has STR: --- → yes
OS: Unspecified → All
Hardware: Unspecified → All
Version: 41 Branch → Trunk
Updated•5 years ago
|
Component: New Tab Page → Search
Comment 1•5 years ago
|
||
Whilst some of the search button is under Search's remit and code, the css here (especially that referenced in bug 1403215) is under the activity stream / new tab code base. Hence I think this is better handled there.
Component: Search → New Tab Page
Updated•5 years ago
|
Updated•5 years ago
|
Priority: -- → P3
Comment 2•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3
(Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3
(normal.)
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•