Remove fixed position on search bar on scroll
Categories
(Firefox :: New Tab Page, enhancement, P3)
Tracking
()
People
(Reporter: amy, Assigned: jsudiaman, Mentored)
References
(Blocks 1 open bug)
Details
(Whiteboard: [lang=css])
Attachments
(2 files)
| Reporter | ||
Updated•4 years ago
|
| Reporter | ||
Updated•4 years ago
|
| Reporter | ||
Comment 1•4 years ago
|
||
| Reporter | ||
Comment 2•4 years ago
|
||
Currently, when scrolling on the new tab page the search bar changes from being inline on the page to a fixed position at the top. This bug is to remove that behavior. See gif attachment for a visual spec.
Comment 3•4 years ago
|
||
Hello I am an accepted outreachy applicant I am looking for good first bug can I work on this bug?
Comment 4•4 years ago
|
||
Hello, I want to contribute to this project.
Thanks
| Reporter | ||
Comment 5•4 years ago
|
||
(In reply to Falguni Islam from comment #3)
Hello I am an accepted outreachy applicant I am looking for good first bug can I work on this bug?
Hi there! I assigned you to bug 1709204, were you wanting to work on multiple bugs?
Comment 6•4 years ago
|
||
Hello Amy, I am an outreachy applicant too.
I would love to be assigned to work on this bug.
| Reporter | ||
Comment 7•4 years ago
|
||
(In reply to onuohaoluebube05 from comment #6)
Hello Amy, I am an outreachy applicant too.
I would love to be assigned to work on this bug.
Hello! Seeing as Falguni has a bug they are working on, let's assign this one to you. Don't hesitate to let me know if you have any questions.
Please note that you will have to bundle the CSS before you can see your changes on the new tab page. Run ./mach npm run bundle --prefix=browser/components/newtab. More information here.
Comment 8•4 years ago
|
||
Thanks Amy
Comment 9•4 years ago
|
||
Hello Amy,
I am getting an error running this "./mach npm run bundle --prefix=browser/components/newtab ".
What could be the cause?
Thanks
Comment 10•4 years ago
|
||
Resolved
Comment 11•4 years ago
|
||
Hello Amy
When I build the browser on my system it appear like this
Behavior on my system
The gif you posted is it the current behavior or the desired behavior?
| Reporter | ||
Comment 12•4 years ago
|
||
Hi onuohaoluebube05!
The gif posted is the desired behavior. Locally, I am still seeing the fixed position behavior we are looking to remove.
We can investigate further.
Just to make sure we are on the same page, will you double-check that you are on the latest central?
- Pull and update your local central:
hg up central && hg pull central && hg update - To build Firefox and run new tab:
./mach npm run bundle --prefix=browser/components/newtab && ./mach build && ./mach run
Also, what operating system are you using?
Comment 13•4 years ago
|
||
Hello Amy,
Thanks for your response
I am using windows operating system.
I updated my local central.
From what i can get, i should set focus to the topmost search bar as the the second search bar scrolls out of view?
Thanks
Comment 14•4 years ago
|
||
Hello Amy,
Thanks for your response
I am using windows operating system.
I updated my local central.
From what i can get, i should set focus to the topmost search bar as the the second search bar scrolls out of view?
Thanks
Comment 15•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last months and this bug has priority 'P1'.
:daleharvey, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 16•3 years ago
|
||
Hi Amy,
From the animated gif, I know the desired search bar behaviour when the search input is empty and in focus.
But what if there is some character typed in the urlbar or search bar, should the input content transfer to the other bar and clear the content?
If the search bar is not focused, will the urlbar set to focus after the search bar is not visible?
Also, there are 2 search bar modes in newtab page, the default one is a fake button and the other one is a real search bar. Are they both have the same behaviour?
What are the behaviours of all the above cases?
Comment 17•3 years ago
|
||
At a guess, this only applies to the "fake" search box that hands off to the urlbar. That search box will not have content only the urlbar
Updated•3 years ago
|
Comment 18•3 years ago
|
||
(In reply to Dale Harvey (:daleharvey) from comment #17)
At a guess, this only applies to the "fake" search box that hands off to the urlbar. That search box will not have content only the urlbar
But now the default focus is on the url bar. It needs to change to default focus on search box?
Comment 19•3 years ago
|
||
is this bug assigned to someone?
Comment 20•3 years ago
|
||
It's my first time here. Can I try to solve the bug?
| Reporter | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 21•3 years ago
|
||
Comment 22•3 years ago
|
||
Many thanks for the patch Jonathan
Scott this is far more involved in the Activity Stream code than I could handle reviewing, is there any chance you could find someone suitable?
Thanks
Comment 23•3 years ago
|
||
Amy, do you want to review this? Code looks to be doing the right things, but I am not really familiar with the specifics of search.
| Assignee | ||
Updated•3 years ago
|
Comment 24•3 years ago
|
||
Do we believe there won't be much change in user engagement with the search box that might have been the original intent behind bug 1481677?
Comment 25•3 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:daleharvey, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?
For more information, please visit auto_nag documentation.
| Reporter | ||
Comment 26•3 years ago
|
||
Hi Jim, wanted to check in to see if we need signoff for this change? There was some confusion about whether we still intend to ship this or not.
| Reporter | ||
Comment 27•3 years ago
|
||
Closing all remaining bugs under https://bugzilla.mozilla.org/show_bug.cgi?id=1707989 per request from product.
Description
•