Your message dated Fri, 11 Jan 2008 09:31:50 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#408768: gitweb: incorrect search form layout when 
$site_header is in use
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: gitweb
Version: 1:1.4.4.4-1
Severity: normal

When $site_header is in use and some vertical space is added to the top
of the web page, the search layout with CSS
div.search {
        position: absolute;
        top: 56px;
        right: 12px
}
is incorrect and ends up to cover the git logo.

Correcting this by using "position: inherit;" is complicated and may
involve some code reorganization between
   git_header_html();   and    git_print_page_nav(...); 

Please forward this upstream for correction.

Thanks,
        Matthijs Melchior.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gitweb depends on:
ii  git-core                     1:1.4.4.4-1 content addressable filesystem
ii  perl                         5.8.8-7     Larry Wall's Practical Extraction 

Versions of packages gitweb recommends:
ii  git-doc                      1:1.4.4.4-1 content addressable filesystem (do

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1:1.5.3.7-1

On Thu, Jan 10, 2008 at 11:53:19PM +0100, Matthijs Melchior wrote:
> So, yes I can confirm this is fixed in version 1.5.3.7.

Thank you.  Regards, Gerrit.


--- End Message ---

Reply via email to