I have field validation code that currently is simple regex that I can
run both in javascript on the browser, and in python code on the
server. This has been working well. However, recently I've been adding
data types that are a bit more complicated, and multi-input-field data
types that have an
On Jan 15, 2006, at 11:46 AM, Dethe Elza wrote:
Anyway, since the goal of MochiKit is to make javascript more
pythonic and less broken, why not why not just write the
code in
python to begin with and have it translated?
I've been aware of that for a while, but it's not something I'm
So events are driving me nuts. Normalization is difficult because
some browsers get their backs up when you mess with something like
event.button, or event.timeStamp. The Level 2 DOM spec is incomplete
and in some cases wrong-headed (event.button, for instance). Mozilla
still has some
On Jan 15, 2006, at 12:31 PM, Beau Hartshorne wrote:
So events are driving me nuts. Normalization is difficult because
some browsers get their backs up when you mess with something like
event.button, or event.timeStamp. The Level 2 DOM spec is
incomplete and in some cases wrong-headed
I'm building a table, have successfully run through my THEAD() section,
and am building out the TBODY().
This code works perfectly on all the other browsers I've tried (Firefox
Mac, Safari, Firefox Win).
I have Microsoft's pathetic script debugger installed on the machine.
Can anyone tell me
Clark Evans wrote:
I have field validation code that currently is simple regex that I can
run both in javascript on the browser, and in python code on the
server. This has been working well. However, recently I've been adding
data types that are a bit more complicated, and multi-input-field
On Jan 15, 2006, at 1:00 PM, ssteiner wrote:
I'm building a table, have successfully run through my THEAD()
section,
and am building out the TBODY().
This code works perfectly on all the other browsers I've tried
(Firefox
Mac, Safari, Firefox Win).
I have Microsoft's pathetic script
From the perspective of a web-designer, what Beau is suggesting would
be a god-send. It would allow the type of programming made possible
with the Win32 API but extremely difficult to implement cross-browser
using current tools.
The problem turns out to be something that I'm doing to an IMG tag that
I'm creating using the DOM IMG() function.
Will post details when I figure out exactly which piece IE doesn't like
poked.
Thanks,
S
