2.0b3 Does Not Support Strict / Standards-Compliant mode correctly in BEA Weblogic Portal.

I am trying to implement a grid in BEA Weblogic Portal 8.1.4, which forces the strict document type. This is causing significat problems with Grid 2.0 (beta 3) when it is implemented in a portlet.
(1.0 does not work at all- see this post http://www.activewidgets.com/javascript.forum.5548.6/grid-problems-under-weblogic-portal.html)

Basically all formatting (grid height and width) and column widths are not being displayed correctly inside of the portlet, and default values are being used. Additionaly, when Resizing a column or scrolling down the grid, the redraw rate is extremely slow and sometimes does not redraw unless you place your mouse over the affected areas.

Removing the "strict" doc type (only for experimentation, portal requires strict doctypes) fixes the problems with the sizing, but the problem with the redraw rate remains (our table is large; 23 columns and 50+ rows).

Does anybody have any suggestions on how to fix this problem. We created a prototype with the grid 1.0 and our client loved it, but if it can not be implemented inside of a portlet than it is useless. Am i missing a setting that turns on the grid "standards compliant mode"? Does beta3 not have all of the "strict" functionality?

Any and all insight is greatly appreciated.

Ryan,

as far as I remember in the Jeff's case the problem was due to strict doctype in the portal page and the grid was working fine in the same page in 'quirks' mode.

The new grid (2.0) 'should' work with strict doctype so the problem might be due to some bugs still in the grid. Would be great if you can send me this page for testing ( file -> save as -> web page complete -> zip :-)

Most likely your page structure is made out of nested tables - in this case it might help to add style="table-layout:fixed" to the parent table element.

Alex,

I e-mailed the files to the support e-mail address... hopefully we can figure out what is going on here.

Ryan,

I was able to correct the example which you sent me – maybe grid will work in full portal page as well. Here are the required fixes (I also sent files to your email) –

- due to IE CSS bugs you have to add grid id and use it together with CSS column styles, like

#grid .aw-column-1 {…}

- You have to use style="table-layout:fixed" in all parent tables of the grid (sometimes it is enough applying it just to immediate parent table). In your page you have to apply it to immediate parent and ‘portal-layout’ table. Brut force solution would be using

table {table-layout: fixed}

which would force it to ALL tables, but if it breaks something, you can just use

table.bea-portal-layout-grid {table-layout: fixed}

and add inline style to grid’s immediate parent - this should fix resizing issue.

- in strict mode padding and border sizes are included into the width/height calculations (so called ‘content box’ model) so if you add 1px border you should reduce padding by 1px to 3px (default is 4px) – this would fix misalignment between cells and headers.


That made it working with your example page. Please let me know if this also fixes it in full portal or if something still does not work.

Alex,

Thanks for the quick relpy.. I have implemented the changes that you have sent and it does appear to be working much better.. The only problem that I see now is that the size of the actual grid iteslf is still not responding. I have the property set as: '.aw-grid-control {height: 350px; width: 850px; border: none; font: menu;}' but the grid still does not resize to those dimensons. In my test case, I also removed the table it was inside (Which had a width of 100%) and had the same problem. Any ideas?

Thanks again for you help

Ryan,

you should try

#grid {height: 350px; width: 850px; border: none; font: menu;}

Didn't work :(

wait, i lied- it did work :)