Feature testing DOM0 event interface

P

Peter Michaux

LOL. But seriously, this was as "pretty" as a strip of tabs can be.
IIRC, my aim at the time was to make it look like a Windows property
sheet.

"look like...Windows"

Please spend your time doing anything else but finding that property
sheet. ;-)

Peter
 
D

David Mark

"look like...Windows"

But it will look like any OS it runs on as that is how buttons are
typically rendered. How fancy do you need tabs to be? There's
nothing that prevents adding additional CSS flourishes to the buttons;
they just won't be rendered in some browsers.
 
D

David Mark

Is this in regard to the Safari 1.x preventDefault bug on click/
dblclick?  I have thought about that one and I don't think it requires
a workaround.
I think the workaround is tiny
[snip]
Below is the idea for click events. I suppose a user cannot cancel the
bubble for this to work. I just thought this up. Does it have any
merit?
You lost me on the "user cannot cancel the bubble" point.

The function called "check" needs to run as a DOM0 event handler and
return false to actually make the prevent default happen in the broken
Safari browsers.

Oh. Disregard my previous comments then.
I think there could be workarounds so that cancel bubble would still
be allowed.

Now I get the connection to propagation. I thought you were trying to
feature test the preventDefault problem.

[snip]
In a broken Safari browser, at least one DOM0 handler for the event
needs to return false to prevent the default behavior. The normal
solution is to use legacy handlers for click and dblclick in so the
actual handler that wants to prevent default will return false.
However why not just let the event bubble up the dom a bit and then
have the document.documentElement.onclick handler be the one to return
false. I think the above code might be good.

It just might.
I don't follow. The above isn't a test. It is the workaround.

I didn't understand what I was reading. I get it now and it might be
a valid workaround. No way to know for sure without trying it.
 
T

Thomas 'PointedEars' Lahn

Peter said:
javascript:alert(typeof document.documentElement.onclick !=
'undefined')

Unfortunately, Firefox returns false for the above.

As it should. Your point being?


PointedEars
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,483
Members
44,902
Latest member
Elena68X5

Latest Threads

Top