edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] $ object in javascript
Date: Sun, 25 Dec 2016 13:06:39 +0000	[thread overview]
Message-ID: <20161225130639.GB16190@odin> (raw)
In-Reply-To: <20161030201745.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 605 bytes --]

On Wed, Nov 30, 2016 at 08:17:45PM -0500, Karl Dahlke wrote:
> > come in by a direct route instead does it work? Does $ exist?
> 
> No and yes.
> Sure $ is there supporting jquery,
> But the website doesn't work because jquery isn't fully implemented / operational.
> This should probably be the highest priority for 3.6.3.
> More than half the sites I run into use jquery.

Agreed, this'd be good to get for 3.6.3.  Anyone know how much more we need to
implement, and is there anything I can do to help with this
(I'm hoping to be able to put some more time into edbrowse development again).

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-12-25 13:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 16:03 Karl Dahlke
2016-11-29 16:24 ` Chris Brannon
2016-11-30  0:47 ` Kevin Carhart
2016-11-30  7:30   ` Karl Dahlke
2016-11-30  7:43     ` Tyler Spivey
2016-11-30  7:54       ` Karl Dahlke
2016-12-01  0:04         ` Kevin Carhart
2016-12-01  1:17           ` Karl Dahlke
2016-12-25 13:06             ` Adam Thompson [this message]
2016-12-26 14:52               ` Karl Dahlke
2016-12-27  3:04                 ` Kevin Carhart
2016-12-27  3:49                   ` Karl Dahlke
2016-12-27  4:17                     ` Kevin Carhart
2016-12-27  4:38                       ` Karl Dahlke
2016-12-27 18:37                         ` Adam Thompson
2016-12-27  4:59                       ` Chris Brannon
2016-12-27  6:53                         ` Kevin Carhart
2016-12-27 15:21                           ` Chris Brannon
2016-12-27 20:13                             ` Kevin Carhart
2016-12-27 13:26                         ` Karl Dahlke
2016-12-27 15:47                           ` Chris Brannon
2016-12-27 18:48                             ` Adam Thompson
2016-12-27 20:23                               ` Chris Brannon
2016-12-28 11:42                                 ` [Edbrowse-dev] Edbrowse in NetBSD Adam Thompson
2016-12-28 11:50                                   ` Chris Brannon
2016-12-28 12:15                                     ` Adam Thompson
2016-12-27 19:11                   ` [Edbrowse-dev] $ object in javascript Adam Thompson
2016-12-27 19:47                     ` Kevin Carhart
2016-12-27 20:11                       ` Karl Dahlke
2016-12-27 20:45                         ` [Edbrowse-dev] nextSibling and previousSibling Kevin Carhart
2016-12-27 21:14                           ` Chris Brannon
2016-12-28 11:38                       ` [Edbrowse-dev] $ object in javascript Adam Thompson

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=20161225130639.GB16190@odin \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).