[Trinidad] Firefox 3.6 has removed the getBoxObjectFor() function - tr:panelPopup non functional

This function seems to have been deprecated until 3.5.x, and has been removed with Firefox 3.6. I just updated and noticed that problem. This makes for example the tr:panelPopup method non functional. There might be other examples where this function has been used. I think someone who

AW: [Trinidad] Firefox 3.6 has removed the getBoxObjectFor() function - tr:panelPopup non functional

Nevermind, it was a double, and has been fixed in 1.2.13 -Ursprüngliche Nachricht- Von: Eisenträger, Tobias [mailto:tobias.eisentrae...@arag.de] Gesendet: Mittwoch, 27. Januar 2010 10:04 An: MyFaces Discussion Betreff: [Trinidad] Firefox 3.6 has removed the getBoxObjectFor() function

Re: [Trinidad] Firefox 3.6 has removed the getBoxObjectFor() function - tr:panelPopup non functional

yep :-) reported and fixed last Friday. Timing was excellent for the new 1.2.13 release ;-) On Wed, Jan 27, 2010 at 10:18 AM, Eisenträger, Tobias tobias.eisentrae...@arag.de wrote: Nevermind, it was a double, and has been fixed in 1.2.13 -Ursprüngliche Nachricht- Von: Eisenträger,

Re: Re: Customizing scroller by using t:dataTable with t:dataScroller

Ok, and how are you sorting your t:dataTable? Are you using sortColumn and t:commandSortHeader or another hack? Regards, Jakob 2010/1/27 Klaus SCHUSTER schus...@racon-linz.at Hi jakob, thanks for the reply. I need the index of the collection, of the first shown element on the page. If I

Antwort: Re: Re: Customizing scroller by using t:dataTable with t:dataScroller

yes right, I am using sortColumn attribute together with t:commandSortHeader. maybe a chance to use the setter of the sortColumn attribute... but in this case I can't use the UIData.getFirst(), I have to calculate the right index of the collection for myself. Jakob Korherr

Re: Re: Re: Customizing scroller by using t:dataTable with t:dataScroller

Take a look at the tomahawk example http://example.irian.at/example-simple-2010012702/pagedSortTable.jsf you can use the binding attribute of the t:dataTable to get a reference to the component in your managed bean like this: binding=#{myBean.uidata}. Then you can use UIData.getFirst() to get the

[Trinidad] error message: selectorString must be non null and non empty

Hi folks I'm migrating a Trinidad application from 1.0.* to 1.2.13 and I've got selectorString must be non null and non empty error. I know it is related with the skin customization, but I could not find any selector field in my css. Hints ? Thanks in advance, Walter Mourão