You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2005/05/19 02:38:55 UTC
[JIRA] Commented: (FOR-336) Table alignment problem with pelt and IE

The following comment has been added to this issue:

     Author: Addison Berry
    Created: Wed, 18 May 2005 7:37 PM
       Body:
It looks like it has to do with the table being 100% (#content table in basics.css).  I switched it to 99% to see and that eleiminates the problem of dropping it below the menu, but then, of course the table is only 99%.  I'm sure it is IE being stupid and I'm sure there is a fix out there.  I'll see if I can track down the IE hack to correct this.

---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-336?page=comments#action_12408

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-336

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-336
    Summary: Table alignment problem with pelt and IE
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Forrest
 Components: 
             Skins (general issues)
   Versions:
             0.6
             0.7-dev

   Assignee: 
   Reporter: Stefano Mancarella

    Created: Wed, 27 Oct 2004 8:51 AM
    Updated: Wed, 18 May 2005 7:37 PM
Environment: Forrest 0.6
Internet Explorer 6.0

Description:
There's a strange (css?) problem using tables with the pelt skin and viewing the result in IE.
If a page contains a table, the table itself always starts below the menu in IE.
So if the table is among the first elements of the page and the menu is long, the result is a blank space before the table itself.
To reproduce the problem do a forrest seed, add a <table> to index.xml (just below the <body> tag) and see the result in IE.

The problem doesn't show up in browsers of the Mozilla family, so maybe it's due to a bug in IE.

Tested with both 0.6 and trunk.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira