The new find bar shifting down content

Ehsan Akhgari ehsan.akhgari at
Mon Sep 9 20:31:03 UTC 2013

Thanks a lot Mike for the follow-up and the due diligence here, much



On Mon, Sep 9, 2013 at 5:04 PM, Mike de Boer <mdeboer at> wrote:

> Ehsan, my apologies for not replying earlier. My PTO made this slip
> through a bit…
> I filed to back out
> the findbar on top and move it back to the bottom. I was able to use `hg
> qbackout` for the entire back out, so it was rather straightforward to do.
> The idea is to back it out of *at least* aurora, so it will not reach beta
> and further. A back out of m-c depends on the results of a conversation
> between product, UX and engineering, which did not happen yet. Please track
> the bug I mentioned above for details that are upcoming.
> Mike.
> On Sep 5, 2013, at 1:12 AM, Ehsan Akhgari <ehsan.akhgari at> wrote:
> Ping?
> --
> Ehsan
> <>
> On Wed, Aug 28, 2013 at 10:40 PM, Ehsan Akhgari <ehsan.akhgari at>wrote:
>> So, what are the concrete next steps here?  Are we planning on letting
>> the current implementation get to the beta channel and hope that we get
>> user feedback on beta?  What is going to be the criteria for evaluating
>> whether we're going to let the current implementation find its way to
>> release and what is the fallback option if we decide that this is not
>> something that we want to ship?
>> While the brainstorming conversation is interesting, I started this
>> thread with a very concrete goal of not letting this feature get released
>> without due diligence, and I'd like to know if I have had any success
>> towards that goal yet!  :-)
>> Thanks,
>> --
>> Ehsan
>> <>
>> On Wed, Aug 28, 2013 at 4:30 PM, Brian Smith <brian at>wrote:
>>> On Fri, Aug 23, 2013 at 9:48 AM, Asa Dotzler <asa at> wrote:
>>> > Can we move our focus to the other potential wins like better
>>> highlighting
>>> > and word counting and put together a new plan for moving the Find bar
>>> to the
>>> > top that has as it's first requirement to not shift content?
>>> I don't know how we go about prioritizing user needs, but it would be
>>> very surprising for me if "user's don't know we don't have a 'find in
>>> page' feature and/or don't know how to activate it" isn't at the top
>>> of the list, at least with respect to the "find in page" feature. This
>>> is something that is addressed by Australis. We clearly expect that
>>> users will use the "find in page" feature through the hamburger menu a
>>> lot, as we made it so prominent there. Since the hamburger menu pops
>>> down on the upper-right corner of the page, a user that clicks "find
>>> in page" in the hamburger menu is going to be looking at the
>>> upper-right corner of the page after he clicks it. So, I think with
>>> Australis there is a strong argument to be made that the find in page
>>> box should be in the upper-right corner of the page.
>>> (Interestingly, that is exactly how it works in Chrome.)
>>> Cheers,
>>> Brian
>>> _______________________________________________
>>> firefox-dev mailing list
>>> firefox-dev at
> _______________________________________________
> firefox-dev mailing list
> firefox-dev at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the firefox-dev mailing list