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: Re: [Edbrowse-dev] document.head.querySelector
Date: Thu, 21 Dec 2017 18:23:34 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.03.1712211815330.14229@carhart.net> (raw)
In-Reply-To: <20171111101510.eklhad@comcast.net>



I'm cleaning up my loose ends.  Sorry it took this long.  I'm going to 
send a startwindow with a few things including this from the 11th, where I 
can answer KD's latest followup from a week ago.  This is about element 
type "a":

> Does someone really ask for a.protocol?
> They should ask for a.href.protocol, I would think.
> Then maybe we should make a default href of type URL.
> But if they want a.protocol then there's no harm setting that to empty string I guess.

I don't know the thinking behind it, but if you demin the sole massive 
code file from xqsuperschool and go to 16343, that's my evidence that 
a.href and a.protocol is a thing.


         createWebSocketURL: function(url) {
           var a;
           if (url && !/^wss?:/i.test(url)) {
             a = document.createElement("a");
             a.href = url;
             a.href = a.href;
             a.protocol = a.protocol.replace("http", "ws");
             return a.href;
           } else {
             return url;
           }
         },











>
> Karl Dahlke
>

--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists

  parent reply	other threads:[~2017-12-22  2:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 10:02 Kevin Carhart
2017-12-10 15:08 ` Karl Dahlke
2017-12-11  9:27   ` Kevin Carhart
     [not found]     ` <20171111101510.eklhad@comcast.net>
2017-12-22  2:23       ` Kevin Carhart [this message]
2017-12-22  2:58         ` Karl Dahlke

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.1712211815330.14229@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).