
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
| Severity: |
Blocker
|
| Runtime: |
DHTML
|
| Fix in hand: |
False
|
|
The "inputtext - clickable" workarounds and special tricks cause some bugs:
Steps to reproduce:
(at least in Firefox2, IE6)
- go to "examples/components/style_example.lzx?lzr=dhtml"
- expand the frosty-window, so it's big enough to cover the inputtext on the right hand side
- hover over the inputtext, or alternatively focus the inputtext by tab-key
- the inputtext's text will become visible
IE6:
from time to time, the whole application did not receive any mouse-clicks anymore,
the only way to resurrect the app, was to change focus by tab-key until I've focused the inputtext,
after the inputtext gained focus, the app was again able to receive mouse-events.
|
|
Description
|
The "inputtext - clickable" workarounds and special tricks cause some bugs:
Steps to reproduce:
(at least in Firefox2, IE6)
- go to "examples/components/style_example.lzx?lzr=dhtml"
- expand the frosty-window, so it's big enough to cover the inputtext on the right hand side
- hover over the inputtext, or alternatively focus the inputtext by tab-key
- the inputtext's text will become visible
IE6:
from time to time, the whole application did not receive any mouse-clicks anymore,
the only way to resurrect the app, was to change focus by tab-key until I've focused the inputtext,
after the inputtext gained focus, the app was again able to receive mouse-events. |
Show » |
|
LPP-5430should resolve the issue with apps not receiving mouse clicks in IE.I'm not sure what to do about the other issues :( Input texts have to be placed in the of the clickable elements (which are in their own tree of divs) to become active.