Author

Powered By

  • OpenWGA Blogs 2.3.3 Build 129
    Running on:
    OpenWGA Server 6.3.1 Maintenance Release (Build 566)
    www.openwga.com

Searchresult for: KEYWORDS:"portlets"

Sort by:


About OpenWGA 6.2

OpenWGA 6.1 is now almost four months old and it is about time for us to talk about our plans for its successor version. The work for it is in full progress, and while we're again behind schedule regarding our original plan for creating feature releases it won't again take a full year for it to get available. 

In fact it is scheduled to be released in not too far time on 9nd September (Update: We had to postpone the release for a week due to outstanding issues). So let's have a look at what is planned for the second installment of OpenWGA 6 feature releases.

OpenWGA and Firefox 4

Firefox 4 is released and we realized some problems with FF4 and OpenWGA.

One minor problem is that some styles no longer are effective in FF4. These style are set in javascript like this: element.style["MozBorderRadius"]="5px". This seems to be no longer supported in FF4. We replaced it by style["borderRadius"] which is now supported in FF4.

A bigger problem is that in some situations a call to element.appendChild(otherElement) executes javascripts contained in otherElement. Because of this bug (?) in FF4 javascripts are sometime executed twice in OpenWGA ajax portlets and this in the end leads to problems with nearly all (Ext-JS based) applications delivered with OpenWGA: Content Manager, Admin Client and others.

However we found a solution for this problem and OpenWGA 5.0.x and 5.3.x will include a fix for ajax portlet handling letting Content Manager and Admin Client do their job also with FF4.


Entry 1 to 2 of 2