On 10/16/07, Alan Gresley <[EMAIL PROTECTED]> wrote:
> The normal hover functioning of the menu works in most browsers. Any test
> with the Khtml or Webkit browser engines would be appreciated. Regarding full
> accessibility at this point in time, I say that this menu is currently one of
> the b
Alan Gresley wrote:
> I have been following this thread with particular interest but staying in the
> background while it bounded in and out of holy war territory. Keyboard
> Accessibility with CSS is possible by using the :focus pseudo selector but at
> this time, only Firefox and Mozilla (mayb
Alan Gresley wrote:
> Christian Heilmann wrote:
>
>> Here is the assumption this article made: a drop down menu should
>> work regardless of input device and stay on the screen when
>> completely expanded without causing scrollbars and thus becoming
>> impossible to reach the last items. Anything
Christian Heilmann wrote:
> Here is the assumption this article made: a drop down menu should work
> regardless of input device and stay on the screen when completely
> expanded without causing scrollbars and thus becoming impossible to
> reach the last items. Anything wrong with that?
> Let's se
I'm sorry to say I'll start with a note and my own questions:
a) Why do you send to the list something that looks like a private matter?
b) Why do you say "us" when you mean "me"?
c) Why do you bother writing and article if you don't accept critics?
d) Why do you force me to re-read your articl
>>> -Original Message-
>>> David wrote:
>>>
>>> Javascript is a security threat to visitors' computers.
>>> CSS is not.
I seem to recall that at one stage certain versions of Netscape/
Mozilla would not render CSS at all if Javascript was disabled. I
have no idea whether that is still t
> I changed my mind. I just read this article and I don't find it useful.
> I think it lacks in-depth knowledge or he simply didn't took the best
> approach for this topic.
As you obviously know the better approach, why not write a better
article? Actually,simply naming the approach would be
>>-Original Message-
>>David wrote:
>>
>>Javascript is a security threat to visitors' computers.
>>CSS is not. Not a "religious issue" but a well documented fact.
Actually JS isn't the problem, its abuse and exploitation is.
Could it be made more secure? Surely, but it isn't in itself th
EXCELLENT review by Tyssen Design. It'll take me a week or so to get through
it, but thanks much.
J
> From: [EMAIL PROTECTED]
>
> And I'm not sure if this URL as been posted recently:
> http://www.tyssendesign.com.au/articles/css/dropdown-low-down/
>
> --
> Regards,
> Thierry | ht
> Please, for your users' sake: use a Javascript drop down menu (but
> make sure it's one that is fully accessible, and that reverts to a
> pure-CSS menu when JS is not available). I use TwinHelix Designs'
> excellent FreeStyle Menus (http://www.twinhelix.com/dhtml/fsmenu/)
> personally, but it's
I changed my mind. I just read this article and I don't find it
useful. I think it lacks in-depth knowledge or he simply didn't took the
best approach for this topic.
I don't think he's wrong (solely in the point that hybrid menus are
better), but anyone with some knowledge could think
Christian Heilmann wrote:
>> I've heard the request for pure CSS drop-down menus quite a lot, and
>> rarely see people getting told what they should about how *bad* they
>> are.
>>
>
> Cause people don't search archives?
> http://archivist.incutio.com/viewlist/css-discuss/78948
>
LOL. I agr
> I've heard the request for pure CSS drop-down menus quite a lot, and
> rarely see people getting told what they should about how *bad* they
> are.
Cause people don't search archives?
http://archivist.incutio.com/viewlist/css-discuss/78948
--
Chris Heilmann
Book: http://www.beginningjavascript
G'day Rafael,
On 15/10/2007, at 2:01 PM, Rafael wrote:
> I think this is yet another religious topic. Accessibility on
> most JS menus (actually all I've seen so far) is inexistent, some
> of them are so poorly done than they even throw an error on this or
> that browser and the whole m
Rafael wrote:
> I think this is yet another religious topic. Accessibility on most
> JS menus (actually all I've seen so far) is inexistent, some of them are
> so poorly done than they even throw an error on this or that browser and
> the whole menu stops working. If you ask Joe Clark about
I think this is yet another religious topic. Accessibility on most
JS menus (actually all I've seen so far) is inexistent, some of them are
so poorly done than they even throw an error on this or that browser and
the whole menu stops working. If you ask Joe Clark about his opinion...
maybe
Kit Grose wrote:
> I've heard the request for pure CSS drop-down menus quite a lot, and
> rarely see people getting told what they should about how *bad* they
> are.
Thanks for bringing it up.
You're right of course, but CSS designers rarely want to know how *bad*
CSS is in that respect. It is
G'day Jay,
I've heard the request for pure CSS drop-down menus quite a lot, and
rarely see people getting told what they should about how *bad* they
are.
CSS is designed as a method for styling visible items and laying them
out relative to one-another. Drop-down menus are behavioural, and
18 matches
Mail list logo
