edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] fetch local / progress on carrier lookup
Date: Mon, 25 Sep 2017 22:50:50 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1709252231440.16707@carhart.net> (raw)
In-Reply-To: <20170826000159.eklhad@comcast.net>



> I fixed the fetch local javascript bug.

Awesome.  Thank you.

I have exciting progress to report on freecarrierlookup.com

We are very close.  Here's the issue.  Is there some way we can allow 
elements to act as clickables when they are not a traditional HTML button, 
but basically anything like an image or a span, yet they have event code attached?

freecarrierlookup's submit button is a type="image"

The exciting thing about freecarrierlookup is that all of the other steps 
work.  You can actually go to jdb and trigger the function that the submit 
is supposed to trigger: showCarrier.
This goes to xhr.  xhr loads the subject matter 
(the entry about the phone number you asked for).  A callback places this 
in a div with id txtHint.  innerHTML side effect works beautifully.  When 
you exit out of jdb, the information has made it back to edbrowse!

Here's the image with the onclick.
<input type="image" src="images/search2.png" 
onmouseover="this.src='images/search2hi.png'" 
onmouseout="this.src='images/search2.png'" 
onclick="showCarrier(document.getElementById('small').value, 
document.getElementById('large').value);return false"/>


Tyler also asked about something on the site fanfiction.net which I think 
in part is a related issue of event handlers on arbitrary elements that we 
haven't earmarked as being interactive.

I think there is a lot of transforming of elements on the fly using JS and 
CSS.  It could say <cat> and be made to woof like a dog through the magic 
of simply overriding everything and assuming all responsibility 
for managing the suppression of the cat behaviors and coding all 
of the canine ones.

  reply	other threads:[~2017-09-26  5:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25  5:45 [Edbrowse-dev] Radio Caroline wants doc.implementation Kevin Carhart
2017-09-25 12:46 ` Karl Dahlke
2017-09-26  2:53   ` Kevin Carhart
2017-09-26  4:01     ` Karl Dahlke
2017-09-26  5:50       ` Kevin Carhart [this message]
2017-09-26 11:57         ` [Edbrowse-dev] fetch local / progress on carrier lookup Karl Dahlke
2017-09-26 23:29           ` [Edbrowse-dev] freecarrierlookup Kevin Carhart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.03.1709252231440.16707@carhart.net \
    --to=kevin@carhart.net \
    --cc=edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).