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] data-* attributes / new work on RC
Date: Fri, 24 Nov 2017 17:44:18 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.03.1711241728020.5490@carhart.net> (raw)
In-Reply-To: <20171024202245.eklhad@comcast.net>



Great progress!

Can you make heads or tails out of this behavior when you try to click 
those links, like the top15s or the schedule?  It takes you to a 
netherworld of size 0, and you have to back up with ^.  It's as though you 
went to an empty frame, or like when you add additional ed environments 
for editing.

Here's the code for the click handler which has been added to "a" 
elements.  It's in the file menus.js.  I don't think a click is triggering 
this code, because I added some alerts and they don't show up.

         function parse_menu_item(url, externalURL, soundURL){
         //if(soundURL) playSound(soundURL);
         if(externalURL){
         window.open(externalURL); // open url in external window only
         return false; // no need to proceed
         }else if(url == "donate.html"){
         slidePopupPanel();
         }else{
         window.location.hash = url; // apply hash to address bar
         }
         }

Maybe it's something to do with the hash change.  Is that supposed to 
trigger http action to a new destination?

K


  reply	other threads:[~2017-11-25  1:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 12:29 [Edbrowse-dev] Tidy error reporting Karl Dahlke
2017-11-22  8:43 ` [Edbrowse-dev] data-* attributes Kevin Carhart
2017-11-22  9:33   ` Kevin Carhart
2017-11-22 15:48   ` Karl Dahlke
2017-11-22 21:36     ` Kevin Carhart
2017-11-23  1:23       ` Kevin Carhart
2017-11-24 21:19   ` Karl Dahlke
2017-11-25  0:20     ` [Edbrowse-dev] data-* attributes / new work on RC Kevin Carhart
2017-11-25  0:56       ` Karl Dahlke
2017-11-25  1:15         ` Kevin Carhart
2017-11-25  1:22           ` Karl Dahlke
2017-11-25  1:44             ` Kevin Carhart [this message]
2017-11-25  2:28               ` Karl Dahlke
2017-11-25  3:10                 ` Kevin Carhart
2017-11-25  5:02                   ` Karl Dahlke
2017-11-25  5:35                     ` Kevin Carhart
2017-11-26 13:14               ` Karl Dahlke
2017-11-27  1:03                 ` Kevin Carhart
2017-11-27  1:48                 ` Kevin Carhart
2017-11-27  2:58                   ` Karl Dahlke
2017-11-27  3:37                     ` Kevin Carhart
2017-11-26 22:43               ` Karl Dahlke
2017-11-27  3:19                 ` Kevin Carhart
2017-11-27  4:23                   ` Karl Dahlke
2017-11-27  4:51                     ` 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.1711241728020.5490@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).