Just a few notes about the current version of compat component-showcase:-
1) regression (already). for some reason, today's build is showing problems with menupopup and menubar. I looked in the svn log, but can't seem to find where the problem lies. There are no server exceptions, and it is probably javascript-related by the looks of it. On the other hand, panelPopup now kind of works (FF only).
2) any javascript-related issues (like 1) are being left for now until Mircea and Adnan have figured out how to get the javascript libraries/functions loaded for the various components. This includes charts, autocomplete, gmap, inputRichText (although it looks good today), tree, Adnan has been assigned 4992. Once javascript gets loaded properly and done with encoding of components, more jiras may be created if these components still don't work.
3) ICE-5000 fix has been committed (using getRequestMap() instead of requestParameterMap()...see jira for details).
4) progressMonitor. Ted had stated that we were going to use pushServer for pushing the progressMonitor instead of the current PushServer api. If this is the case, we should open a jira for this and link it to 4458.
5) safari issues. Most of the components work fine using Firefox, but Safari is totally not good at all (too many problems to list). Most of the javascript fixes already done do not solve problems with Safari but do with FF.
6)Drag & Drop:- drop area moves after first drop. If you remove all the items in the shopping cart, you lose the drop area permanently
7)ICE-4493...for review by components team, but the panelPopup now (kind of) works. Problem with menupopup when it worked a couple of days ago
8) panelTooltip giving NPE when trying to find the parent Id of the form. I am looking into this. Will create jira today.
9) position panel only works first time (javascript problem?).
10) I just realized that panelConfirmation isn't in the application, so am currently adding it in. (it was added to the current showcase after I did this one).
11) it is now locking up occasionally (even with FF). Will try to see if there is some consistent behaviour.
13) LASTLY....fileupload will be the last one to be fixed.
Here is a preliminary list of issues identified by Joanne, with some notes on possible causes and fixes added after each '>'. A bunch of these are solved by simply making the rime.css stylesheet available to the app, since initially it wasn't being found.
> Rime styling was incorrect
> Rime styling and incorrect path to the images
> Bean scope was incorrect so the chart was being recreated and reset (as part of it's default constructor) on every interaction.
> More Rime styling, alot of these issues came about because the xmlhttp folder containing the rime resources (sheet and images) was unavailable to the app.
> Possibly an issue with the DragEvent
> An issue with the iframe and how it's handled by the framework
> Missing Rime style
> Missing Rime style
> RenderManager issues for how it was declared in faces-config