Is it possible to force re-avaluating/re-parsing of HTML?

[Paul Gorodyansky]

Hi,

Ran into the following problem while trying to have a code to
attach a Virtual Keyboard to any user's form:

User clicks a button and my JavaScript changes outerHTML
of say <textarea - adding things like ONCLICK='saveCa ret(this)'
etc. and it also tries to save any text that user could've entered
before the button press.

a) Value - (already typed text) is not assigned back
b) outerHTML is still the same - both in alert() text and via

javascript:x=do cument.body.inn erHTML.replace(/</g,'&lt;').repla ce(/\n/g,'<br>'); document.body.i nnerHTML = x;

The code is simple so I wander whether we have a way to force HTML to be
re-avaluated/re-parsed via a button click

(if I do the same via <script....</scriptline placed above the button
then everything is OK - because HTML is being changed _before_ the
page load is over)

=============== =============== =========
function vkb_addAttribut es(obj)
{

var obj_value = ""; if (obj.value != "") obj_value = obj.value;
var kA=" onFocus='vkb_tx tControl=this;' OnSelect='vkb_s aveCaret(this)' ";

var obj_HTML = obj.outerHTML;
var pos = obj_HTML.indexO f('>');
var part1 = obj_HTML.substr ing(0,pos);
var part2 = obj_HTML.substr ing(pos);
obj.outerHTML = part1 + kA + part2;

obj.value = obj_value;
}
=============== =============== ===============

Thanks,
Paul

[GLC]

I apologize for my incoherent blabber.
I meant that the event object does not have to be specified or passed
in.
But, you are correct that the function definition must include a
parameter to receive the event if it IS passed in, which is the case
with non-IE browsers.
Thus, in my example where I am using a function reference to attach an
event handler, I am not including a parameter, because one cannot be
used for function references; and yet, the function definition does
have a parameter, which may or may not be used depending on the
browser.

Event handling and asynchronous function calls are so easy to
understand, I am surprise we are even having this discusion. ;-) j/k
On Oct 6, 4:13 pm, Paul Gorodyansky <paul...@compus erve.comwrote:

GLC wrote:

No, it is not IE only.
e is passed in as a parameter for non-IE browsers.
That line checks if e exists before using the IE only windows.event.T hen it's a contradiction where it's a MUST to have parameter or not:

e is passed in as a parameter for non-IE browsers.and

For dynamically added event handlers; neither the event nor the element
triggering the event NEED to be passed.?

--
Paul

[Paul Gorodyansky]

GLC wrote:

>
I apologize for my incoherent blabber.
I meant that the event object does not have to be specified or passed
in.
But, you are correct that the function definition must include a
parameter to receive the event if it IS passed in, which is the case
with non-IE browsers.
Thus, in my example where I am using a function reference to attach an
event handler, I am not including a parameter, because one cannot be
used for function references; and yet, the function definition does
have a parameter, which may or may not be used depending on the
browser.

You mean, non-IE browsers would not midn the following?

1) No parameter (can not be)

txtControl.oncl ick=myFunction;

2) There is a parameter and my function magically knows that it's
event
function myFunction(evt) {...}

Right?

Aslo, Keith never wrote a demo/explanation for his package so I still
don't get how to obtain an object where the even handler is working
if there is no 'this' parameter.

--
Thanks,
Paul

[Paul Gorodyansky]

Just to clarify - the discussion is now around the fact that
one can add an evenhandler (we are talking cross-browser, not jsut iE)
by

txtControl.onfo cus=myFunction;

but only with _that_ syntax, i.e. NO parameters.

It then contradicts with your (unless I am missing something) phrase
about non-IE browsers _passing_ the parameter:

But, you are correct that the function definition must include a
parameter to receive the event if it IS passed in, which is the case
with non-IE browsers.

?

--
Paul

[Paul Gorodyansky]

Paul Gorodyansky wrote:

>

You mean, non-IE browsers would not mind the following?

1) No parameter (can not be)

txtControl.oncl ick=myFunction;

2) There is a parameter and my function magically knows that it's
event
function myFunction(evt) {...}

ad not say a variable that sets a color of my button? :)

--
Paul

[Ian Collins]

Paul Gorodyansky wrote:

GLC wrote:

>>I apologize for my incoherent blabber.
I meant that the event object does not have to be specified or passed
in.
But, you are correct that the function definition must include a
parameter to receive the event if it IS passed in, which is the case
with non-IE browsers.
Thus, in my example where I am using a function reference to attach an
event handler, I am not including a parameter, because one cannot be
used for function references; and yet, the function definition does
have a parameter, which may or may not be used depending on the
browser.

You mean, non-IE browsers would not midn the following?

1) No parameter (can not be)

txtControl.oncl ick=myFunction;

Parameters are irrelevant here, 'myFunction' is the function reference.

2) There is a parameter and my function magically knows that it's
event
function myFunction(evt) {...}

It doesn't magically know, it is passed when then event handler is called.

Modern browsers call event handling callbacks with an event object as
their parameter, IE calls them with window.event as the event object.

--
Ian Collins.

[Paul Gorodyansky]

Ian Collins wrote:

>

1) No parameter (can not be)

txtControl.oncl ick=myFunction;

Parameters are irrelevant here, 'myFunction' is the function reference.

2) There is a parameter and my function magically knows that it's
event
function myFunction(evt) {...}

It doesn't magically know, it is passed when then event handler is called.

Modern browsers call event handling callbacks with an event object as
their parameter, IE calls them with window.event as the event object.

So non-IE browser while looking at that function definition - say
function myF(parA, parB, parC)

ALWAYS assumes that parA is event
and in the 'body' of that function I can use say

if (parA.ctrlKey)
return true;

?

Then it _is_ a magic :) So, always parameter #1? Or it's allowed
to have only one parameter at that's it? And the assumption that
it's event ?

Or you are saying that NO parameters are needed in the function
_definition_ - just

function myF()
{
}

and event is a pre-set, special name that can be used
like this

if (event.ctrlKey)
return true;

?

Presently I have say (event is 2nd parameter)

<textarea .... onkeypress=vkb_ changeKey (this, event)

with parameters being set and used like this:

function vkb_changeKey (txtControl, evt)
{
if (evt.ctrlKey)
return true;
}

*************** *************** ****

So you guys are saying that it's possible to do the same

by

txtObject.onkey press=vkb_chang eKey;

and use some other methods for getting hold of text Object
(with the lcuk of 'this' as a parameter)
and use some other methods of using event ?
---
Thanks,
Paul

[Ian Collins]

Paul Gorodyansky wrote:

Ian Collins wrote:

>>>1) No parameter (can not be)

txtControl.o nclick=myFuncti on;

Parameters are irrelevant here, 'myFunction' is the function reference.

>>>2) There is a parameter and my function magically knows that it's
event
function myFunction(evt) {...}

It doesn't magically know, it is passed when then event handler is called.

Modern browsers call event handling callbacks with an event object as
their parameter, IE calls them with window.event as the event object.

So non-IE browser while looking at that function definition - say
function myF(parA, parB, parC)

ALWAYS assumes that parA is event
and in the 'body' of that function I can use say

if (parA.ctrlKey)
return true;

?

Then it _is_ a magic :) So, always parameter #1? Or it's allowed
to have only one parameter at that's it? And the assumption that
it's event ?

Do you have a book on JavaScript? If not, I'd recommend David
Flanagan's "JavaScript The Definitive Guide" where all these concepts
are explained.

--
Ian Collins.

[Paul Gorodyansky]

Ian Collins wrote:

>

Do you have a book on JavaScript? If not, I'd recommend David
Flanagan's "JavaScript The Definitive Guide" where all these concepts
are explained.

Thanks, I'll do that - before I just used Web materials - thinking,
"if I know how to program in C or C++ then I can program in JavaScript
especailly because it's a _hobby_ (Virtual Keyboard) -
by just looking at Web examples and FAQ".

Kind of worked :)

But it looks like now it's time for learning more deep concepts...
--
Regards,
Paul

[Ian Collins]

Paul Gorodyansky wrote:

Ian Collins wrote:

>>Do you have a book on JavaScript? If not, I'd recommend David
Flanagan's "JavaScript The Definitive Guide" where all these concepts
are explained.

Thanks, I'll do that - before I just used Web materials - thinking,
"if I know how to program in C or C++ then I can program in JavaScript
especailly because it's a _hobby_ (Virtual Keyboard) -
by just looking at Web examples and FAQ".

That (C and C++) is my background as well and it took me a while to
break loose of the shackles imposed by a strongly typed, class
inheritance mindset.

Kind of worked :)

But it looks like now it's time for learning more deep concepts...

In the case of the above book, 590 well written pages of them :)

--
Ian Collins.

[Paul Gorodyansky]

Hi,

GLC wrote:

...
To add an event handler: EventManager.Ad d(tmpImg, "click", saveItem,
false);
Then in the called function:
function saveItem(e){
// get target button
var targ;
if (!e) var e = window.event;
if (e.target) targ = e.target;
else if (e.srcElement) targ = e.srcElement;
if (targ.nodeType == 3) // defeat Safari bug
targ = targ.parentNode ;
...

Thanks, it works - if it's just a function that I want to have in a new
eventhandler added to object, but I can not figure out what to do
if it's not

<textarea onkeypress=myFu nction(this, event)

but several things like (what to do with return ?):
a)
<textarea onkeypress={myF unction(this, event);x=f2(thi s);return false;}

or

b)
<textarea onkeypress={ return myFunction(this , event); }
--
Regards,
Paul