I studied the behaviour of the pointer-shape a little on my machine.On Firefox:
The mouse pointer changing to a hand over areas that have a function when clicked is defined by css. Somehow on firefox after refreshing the contents of the table CSS isn't applied again so the cursor changes into what Firefox thinks it should be. A text-cursor when hovering over text and a normal pointer when not hovering over text. However, the css for highlighting a table row when hovering over it, does seem to hold after refreshing the contents.On Opera:
The code used for Opera is the same as Firefox's, but: the pointer stays a hand after refreshing if so defined by css, but the row highlight does not stay when refreshing. This is opposite to the behaviour in Firefox where the pointer doesn't work, but the highlight does.On Safari and Chrome:
Both the shape of the mousepointer and the row-highlighting work, but there's some blinking when refreshing.Click behaviour
How it's possible that you can totally not click on anything I don't understand. I'm at a loss, really. I checked on every browser I can think of and can't reproduce what you are experiencing in any way. Over here it's working perfectly. Where just using onclick or just using onmouseup would fail I understood that and I could recreate the situations where it would go wrong, but this I can't.
However, just in case this is something that is OS related or driver related ( or maybe you are using a wacom or something
), please tell me something more about your OS, mouse, drivers. It's really the only thing I can think of right now and I would also really hate it if this is what makes a difference.Progress bars
There is no way to send the data for the progress bar images via xml right now, since there is no base64encode in amuleweb. If I would just pass the filenames then the images would not update. I could add a random tag to the filenames, but then all the images will retransmit every refresh. I think that's not very bandwidth efficient. Transferring the images on first load takes about 5 to 10 seconds for me, and that's on LAN. Don't know exactly what the bottleneck is, but it just isn't fast enough to refresh often. As far as I can see, there is no way to just retransmit those pictures that are updated, so I chose to just have bars that fill from left to right that are drawn by some css.Console
Ok ok, so the bug was in two places
It should be gone when I release the next update.