|
Using Firefox 3, when I attempt to click the scrollbar on a dropdown list (b:select), the list disappears. I'm unable to scroll using the scroll bar. Is there a workaround? Thanks.
Active Forum Topics
- Invoking customActionListner on click of the pager Button
- slider values is blank
- Attribute to template link
- Changing calender min / max date
- solution needed for adding and deleting treeleaf dynamically from the tree
- Change skin dynamically
- Possibility for creating a new treebranch and treeleaf dynamically in backbase
- displaying the listgrid with column names selected dynamically from listbox
- creating more than one copy of the treeleaf in treewidget
- Displaying icons at the end of the treeleaf of the tree widget dynamically
Recent Blog Posts
- Advanced 3D Animations and Transitions
- Telamon Visual Ajax Builder Beta sent to Early Adopters
- Backbase in Visual Studio 2008 Express in 1 Minute
- Data Services 1.1 (for Java) Released
- New: June Ajax Newsletter available
- Client Edition 4.2.1 Released
- JSF Examples: i18n, custom components, push & listGrid
- Performance Optimization for Backbase Applications
- Javascript HTML Construction Benchmark
- Integration of Spring into Backbase JSF applications
Dropdown list and Firefox 3.0
9 July, 2008 - 16:32 — EmielHi terning1,
in the b-select.xml of the skin you are using there is a reference to the inactive event. For the dynamic skin in my copy of Backbase 3 it is on line 172. I think here is where it goes wrong. It looks like because the select box looses focus it closes the pulldown. An easy way to work around this is to delete this event from the b-select.xml but then it will not close when it looses focus. You will have to close it by hand.
Offcourse the real problem is why it looses focus when you click on the pulldown scrollbar and actually that is the issue to solve. I did not yet investigate this but will do as soon as I can find some time for that.
Regards,
Emiel
Dropdown list and Firefox 3.0
9 July, 2008 - 17:32 — terning1Thank you, Emiel, for looking into this.
We've decided to stay with Firefox 2.0 for now, so I would rather not change any base code--especially if the solution will create another problem.
Please let me know when you find a viable workaround.
Thanks,
Arnel