From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kevin@carhart.net>
Received-SPF: None (mailfrom) identity=mailfrom; client-ip=8.23.224.61;
 helo=out.smtp-auth.no-ip.com; envelope-from=kevin@carhart.net;
 receiver=<UNKNOWN> 
Received: from out.smtp-auth.no-ip.com (smtp-auth.no-ip.com [8.23.224.61])
 by hurricane.the-brannons.com (Postfix) with ESMTPS id 20C0D77DCD
 for <edbrowse-dev@lists.the-brannons.com>;
 Wed, 11 Oct 2017 10:52:02 -0700 (PDT)
X-No-IP: carhart.net@noip-smtp
X-Report-Spam-To: abuse@no-ip.com
Received: from carhart.net (unknown [99.52.200.227])
 (Authenticated sender: carhart.net@noip-smtp)
 by smtp-auth.no-ip.com (Postfix) with ESMTPA id 2EF29729
 for <edbrowse-dev@lists.the-brannons.com>;
 Wed, 11 Oct 2017 10:54:15 -0700 (PDT)
Received: from carhart.net (localhost [127.0.0.1])
 by carhart.net (8.13.8/8.13.8) with ESMTP id v985Gu7R031701
 for <edbrowse-dev@lists.the-brannons.com>; Sat, 7 Oct 2017 22:16:56 -0700
Received: from localhost (kevin@localhost)
 by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id v985GtuG031694
 for <edbrowse-dev@lists.the-brannons.com>; Sat, 7 Oct 2017 22:16:56 -0700
Date: Sat, 7 Oct 2017 22:16:55 -0700 (PDT)
From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Message-ID: <alpine.LRH.2.03.1710072205340.7496@carhart.net>
User-Agent: Alpine 2.03 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Subject: [Edbrowse-dev] hyphenated event type names
X-BeenThere: edbrowse-dev@lists.the-brannons.com
X-Mailman-Version: 2.1.24
Precedence: list
List-Id: Edbrowse Development List <edbrowse-dev.lists.the-brannons.com>
List-Unsubscribe: <http://lists.the-brannons.com/mailman/options/edbrowse-dev>, 
 <mailto:edbrowse-dev-request@lists.the-brannons.com?subject=unsubscribe>
List-Archive: <http://lists.the-brannons.com/mailman/private/edbrowse-dev/>
List-Post: <mailto:edbrowse-dev@lists.the-brannons.com>
List-Help: <mailto:edbrowse-dev-request@lists.the-brannons.com?subject=help>
List-Subscribe: <http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev>, 
 <mailto:edbrowse-dev-request@lists.the-brannons.com?subject=subscribe>
X-List-Received-Date: Wed, 11 Oct 2017 17:52:02 -0000



I think I may have hit on a good one.  It began because some page code 
wants to address an event handler on an event called 'invalid-form'.

I think this currently doesn't work because the eval() that we have in our 
our add event handler code uses the 'dot' style for property referencing. 
The evaluation of a string like blah.invalid-form raises an error.

But I think we can get these to work by changing it to bracket style, like 
this:
eval(
'this[\'' + ev + '\'] = function(){ var a = this[\'' + evarray + '\']; 
if(this[\'' + evorig + '\']) this[\'' + evorig + '\'](); for(var i = 0; 
i<a.length; ++i) {var tempEvent = new Event;tempEvent.type = "' + 
ev_before_changes + '";a[i](tempEvent);} };');

It becomes ugly because I added escaped single quotes, but it works!

I wonder if this might come up quite a bit and we never knew.  Also, I am 
excited, because this *might* fit the profile for being the answer to a 
major headache, which is error messages without a line number.  There are 
quite a few of these at the very end of the logging for a particular run.
I have not known what they are or how to address them in order to fix 
them.  These are the ones that remain opaque, even with the wonderful, 
lovely new diagnostic tools.

What if every single time some page's javascript was trying to 
build event types programmatically in a string variable, and use a hyphen 
between pieces, it wasn't working in edbrowse because of the difference between 
dot referencing and bracket referencing, and what if from now on, it can?

Could be big!


K