Footer text non-clickable

Bug #145624 reported by Paul Sladen
38
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Matthew Paul Thomas

Bug Description

On pages such as:

  https://bugs.launchpad.net/malone/+filebug

the text that appears at the bottom:

  Terms of Use | Help improve Launchpad | FAQ Copyright 2004-2007 Canonical Ltd. | build 492

is not clickable or selectable, except when hovering over the bottom ~5px of the text; the upper 2/3rds doesn't respond to actions.

Perhaps there is an invisible image or div over the top and obscuring events?

Ideally the links should be fully clickable.

  Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/2007040314 Firefox/2.0.0.3 (Ubuntu-feisty)

description: updated
Changed in malone:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Diogo Matsubara (matsubara) wrote : Re: Footer text partly non-clickable

After today's rollout the footer became totally un-clickable

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Footer is unclickable in Firefox (2.0.0.8) only. It works in IE6 and Opera.

Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [Bug 145624] Re: Footer text non-clickable

On Thu, Oct 25, 2007 at 06:48:16PM -0000, Diogo Matsubara wrote:
> Footer is unclickable in Firefox (2.0.0.8) only. It works in IE6 and
> Opera.

The footer is still unclickable for me with Opera 9.21, at least on most
pages. On https://launchpad.net/ the footer is clickable, but not on
https://bugs.launchpad.net/.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Matthew Nuzum suggested:

https://pastebin.canonical.com/798/

Matthew Thomas, can you take a look and land accordingly on edge?

Thanks

Changed in launchpad:
assignee: nobody → mpt
milestone: 1.1.10 → 1.1.11
Revision history for this message
David Allouche (ddaa) wrote :

This is caused by the "top: 28px" property in the #container rule.

Removing that property damages the layout w.r.t. to the application chooser, so it's not trivial to fix.

Revision history for this message
David Allouche (ddaa) wrote :

It seems that increasing the padding-top in this rule to 48px fixes the layout.

Revision history for this message
David Allouche (ddaa) wrote :

In other words, I suggest the same thing as Matthew Nuzum :)

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Fix in mainline r5110

Changed in launchpad:
milestone: 1.1.11 → 1.1.10
status: Confirmed → Fix Committed
Revision history for this message
verdy_p (verdy-p) wrote :

Absolutely not fixed in IE: the content area is ALL blnk, due to the <div class="clear"></div> that follows it (with a comment "for Opera").
The problem is not this div, but the way the class "clear" is implemented (in "style.css"): it forces a height="0", BUT, it incorrectly sets "overflow:hidden" which does not change the height, but forces the excess height below it to be clipped. So we have space reserved for the "float:left" content area, but the normal inline/block flow truncates everything that is below it.

You MUST remove "overflow:hidden" (this won't change the layout or position of any element, but at least the floatting elements beside the clear will be drawn!). Even the kludge for Opera (with ".clearfix") is not even needed if you remove this undesirable property! If you search where it is set, it is just in the few first lines of "style.css"...

In addition, the CSS file "style.css" is bogous at line 710: a floating element (float:left) CANNOT be "display:inline". This should be "display:block". Normally browsers should ignore "display:" in this case where "float:left" applies, if this is not "display:none" and always treat it as if it was "display:block" (see the CSS1 and CSS2 specs for the algorithm used to get the COMPUTED style value, this is clearly "display:block"). So don't specify things that could be bogous, remove "display:inline" or set it exactly the way it should be interpreted "display:block".

Finally, at the same place, there's "position:relative": is this needed? The only value possible alternate for floating elements is "position absolute" to set the position of the floating element according to the display frame instead of the container block of the floating element. It is NOT relative to the current inline or block position of the main central flow of the container, but to the current position of the left flow of the container.

Revision history for this message
Khoo Kah Ken (gossipze) wrote :

I tried on Firefox 2.0.0.6 and im still unable to use the link

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Not entirely fixed.
Some places it does work while in others it does not.
Places confirmed as not working:
The main applications front pages (bugs.launchpad.net, code.launchpad.net, translations.launchpad.net, and so on)
The launchpad help wiki (https://help.launchpad.net/)

Places where the links do work:
LP front page (launchpad.net)
Any random bug page (launchpad.net/bugs/1)
Translations page (+translations)

Changed in launchpad:
status: Fix Committed → Confirmed
Joey Stanford (joey)
Changed in launchpad:
milestone: 1.1.10 → 1.1.11
Changed in launchpad:
milestone: 1.1.11 → 1.1.12
Revision history for this message
Ansgar Burchardt (aburch) wrote :

Konqueror (3.5.7) is also affected by this bug.

Revision history for this message
verdy_p (verdy-p) wrote :

The bug is fixed for me in Internet Explorer 6 or 7...

Changed in launchpad:
milestone: 1.1.12 → 1.2.1
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I'm not able to reproduce this problem on any Launchpad page in Firefox 2.0, Konqueror 3.5.8, Opera 9.25, or Internet Explorer 6.

Changed in launchpad:
status: Confirmed → Incomplete
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

If you can reproduce it, please give an exact browser version and the exact URL of a problem page.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

This probably is fixed already, but certainly won't be altered for 1.2.1 without steps to reproduce.

Changed in launchpad:
milestone: 1.2.1 → none
Revision history for this message
Martin Albisetti (beuno) wrote :

Problem seems fixed, I can't find anywhere where it's no clickable with Firefox 3

Revision history for this message
Paul Sladen (sladen) wrote :

Works for me, so seemingly this probably got fixed.

Changed in launchpad-foundations:
status: Incomplete → Fix Released
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/145624

tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.