Sorry I was rambling a bit. Allow me to ramble further, and try to better explain what I was talking about:
So I had "recently" added a mouse-over tooltip that gave ship names. I had put this in around the same time that I took out the automatic opening of the large popups. That manual tooltip feature was functional, but flashes in and out of existance quickly because as it begins existing, it sometimes goes under the mouse, which triggers the mouseout event, which makes it vanish, which now puts the mouse over the target, triggering the mouseenter, making it appear...repeat.
The
jquery UI .position() tools are newish. I think they've been around for a year --so I should have looked at them sooner-- but they are old enough that they weren't available when I started the project. I was looking at them because I thought they'd be a good way to position the tooltip names without the above-mentioned issue. I suggest this because the .position() lets you put relative positions based on 'my' and 'of' parameters that they define, so the position can be relative to another object more easily than pure CSS allows. Additionally it natively handles popup intersection, and has a natural 'flip' logical option to make it switch sides. If this worked, it would be a great way to do not just the name tooltips,
but also the main ship info popups (which are currently positioned using absolute math based on the database-stored positions of the ships).
Ultimately though, I messed around with all this for a while (i.e. my previous post) and discovered that I'd basically need to re-position everything to be relative and have everything use .position() for this to work the way I'd like. My efforts with just the tooltips had them seemingly be relative to the top of the page, despite the 'of' target being the ship's span. I even went so far as to try and position the ships's indicators (the .indicator css class) using .position() but they also seemed to be relative to some top of the page, despite making their 'of' target the '#grid'. At that point I just reverted all the changes and left it be, which is why you probably didn't see anything when you did an update earlier today. Ultimately I do think using .position() would be a good idea, but would likely involve a top-down reworking of how we position everything, hence why I think it should be shelved for after (unless you want to tackle this yourself, Wedge!). My discussion had nothing to do with CSS3, per se, nor rounded corners (although some updates to CSS3 standardization wouldn't be a bad thing).
side note: I only started messing with .position() after I had tried converting the name tooltips I wrote over to the brand new jquery ui .tooltip(). They "worked" in that they did popup, but they were the width of the page for some reason. I still haven't figured out why this was the case, but there's clearly an odd interaction between our css and the "custom-theme" used by the jquery ui widgets. The .tooltip() had a property that took a position of the .position() style, and that led to the above diversion.
Failed attempts you'll discover, if you do an svn update, that I actually did commit something rather large today. I hadn't intended to, but after my experiments with .position() I ended up starting on Phase 6. I'll likely make a formal thread about it alone sometime soon, and I can't promise making a lot more progress, but as of right now, I've got working a number of admin tools for editing ships in-game. For debug purposes sake, I have not locked them away behind an admin authentication, so everyone will be able to test them out, but I'll post details on all that later, in another thread. Industrious readers who have followed this for a while can probably guess how to access phase 6 though...