quote:
It would have been better to be open and truthful in the first instance.
Tao, I am totally willing to adress your points, but for the sake of not mixing matters, I recommend the "witch hunt" thread in the Ozones forum,
which has been opened for that purpose : not having one more interesting thread polluted by emotionally charged exchanges.
Rest assured I understand part of your views and am willing to deal with it : in an APPROPRIATE thread.
AS FOR MY MENU : just to clarify the purpose, a bit obscure in the thread title - I had a meeting this morning where I had to demonstrate webdesign skills,
and wanted something a bit more "relaxed", pro, and a bit less "flashy" than www.beyondwonderland.com as it is.
Hence the QUICK and incomplete actions taken - and my reluctance at drifting too far from something that gets the job done : it did.
The meeting was a success and this thing played it's part.
On to my COSA 3d, a Java programming marathon for the next ten days until I meet the next, bigger customer.
And thank you for both the input AND the "turning this thread into a fun thing" and creating useful widgets.
Speaking about accessibility : all the while it kept working on all major browsers, as per my personal coding standards,
and quite frankly, what's left to fix is pretty symbolic as opposed to "getting it to work". I could use a day like today
(except that I've been up until daybreak working my behind off on Cosa. It will be a long week.
Coffee donors, please send some beans to my paypal account).
Have learnt, these past years, to start off as close as possible to my goals, and debug as the very last step.
Thank you and yeah, sure... I still see some jittering or something at the bottom, and there is a lot to improve - LI for one. Will get back to it.
Right now, I am stuck in COSA, building it up - a Java coding marathon of sorts.
Finally back to this. Aim of the weekend : being THROUGH with the COSA and the "me" thingies.
So, some tweaking later, I think it's better now, the jittering seems to be gone.
The items still fadeOut when the user hover the A tag inside the *cough* DIVs, and the links do not take the full size of their container making them a LOT harder to click as the navigations swings.
While I am getting gently started on four CMS/frontends at once, reviewed today, and one integrated in the whole stock control system of a store (meaning
I have to design and implement the stock control system in question) - but keeping time to prepare the core hardware/software demo of leading products including COSA
for the beginning of April, and around midnight tonight, there is the medical imagery 3d scanning project for which I will get the directions.
Right now, I am ending 30 hours of work in a row. *cough*
Last week, only COSA was facts, all the rest were words. Now they are paper, plans, code, and the nightly classes? Oh yeah. That, too.
In FF its very jumpy and jerky, when you click it loses the highlight which isn't great, and expanding the size of a menu items space seems pointless. The Doc did one a few years ago you might be able to find and take a look at.
Blaise, thank you. I'd be happy if we could preserve this thread free from flames now that all has been said and done, though,
it really is good the few drifts aside.
Hugh, thanks too, even poi for that matter : to Hugh, which OS? FF2/3 on WinXP here is fluid.
...It is now clear, though, that some of these flaws are due to avoiding the li usage in first place.
Are you talking about the Latest in iTunes thing ? btw their image replacement technique shows nothing when CSS are ON but images are OFF.
Oh my, this thing works so bad it hurts. I barely see any animation in FF2, FF3, Op 9.2, Op 9.5 or IE7. In IE7 there is a bunch of JS error fired in http://www.apple.com/global/script/lib/iepngfix.htc, Then the script seem to wait a bit to register the position of the mouse. It only seem to animate ok in Sf3. Quite a few times I was hovering the menu and got a submenu open while I was hovering the headline of another submenu.
Yeah, I would call that implementation vs. the one discussed here apples and oranges I don't find the implementation on the Apple site to be interesting at all - it is much like countless typical expanding list-menus out there.
Of course, extra space being needed for content will obviously make differences in implementation, but any way you look at it, a list - coded as such - is both semantically correct, and with the proper understanding easily achievable from a markup and styling perspective.
Oh? I am on Safari, didn't notice. There are really good things in Safari btw - backbutton warning when resubmitting a form for example.
Would much appreciate a break down of what they are doing wrongly about image replacement there,
but one thing they do correctly is that it is not the whole surface of "elastic" panels which triggers the "resize",
it's only the heading, and only onclick.
(which I fixed by taking the last div off of the shrinking mechanism - it's at maximum size all the time)
Poi's version is right in all regards (and works in IE8 and all browsers), except the transition is a bit "jumpy" when moving from an item to the next : http://poi.ribbon.free.fr/tmp/argo_nav/