Closed
Bug 1482247
Opened 6 years ago
Closed 6 years ago
Incorrectly positioned search icon on sticky search in RTL
Categories
(Firefox :: New Tab Page, defect, P2)
Firefox
New Tab Page
Tracking
()
People
(Reporter: k88hudson, Assigned: ahillier)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
For RTL, the search icon inside the search box is incorrectly positioned on the left instead of the right only when in it's "fixed" form.
Reporter | ||
Updated•6 years ago
|
Iteration: --- → 63.4 - Aug 20
Priority: -- → P2
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → ahillier
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Commit pushed to master at https://github.com/mozilla/activity-stream https://github.com/mozilla/activity-stream/commit/883d23f70006c51660a98a6d261614ac53118654 Fix Bug 1482247: rtl search icon position (#4308)
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment 3•6 years ago
|
||
qa note: This also did not export to nightly, so no previous build to verify the existence of the bug.
Comment 4•6 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/972b3c48c6e9
status-firefox63:
--- → fixed
Target Milestone: --- → Firefox 63
Comment 5•6 years ago
|
||
I have verified this on Windows 10 x64, Arch Linux and Mac 10.13.3 with the latest version of "Firefox Nightly" (63.0a1 - Build ID 20180813220525) installed and I can confirm that the search engine icon is displayed in the right side of the "Search Box", in the RTL builds.
Status: RESOLVED → VERIFIED
Comment 6•6 years ago
|
||
https://hg.mozilla.org/releases/mozilla-beta/rev/9e752b54a20f425449e1f00bf3adefa903f8051a
status-firefox62:
--- → fixed
Comment 7•6 years ago
|
||
I have verified that the Search Engine icon is displayed in the right side of the "Search Box", in the RTL builds on Windows 10 x64, Arch Linux and Mac 10.13.3 with the latest Firefox latest Beta (62.0b18 Build ID 20180816151750).
Updated•5 years ago
|
Component: Activity Streams: Newtab → New Tab Page
You need to log in
before you can comment on or make changes to this bug.
Description
•