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] GCS and never-referenced style props
Date: Sun, 8 Sep 2019 16:23:24 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.1909081602280.83820@phoenix> (raw)

Thanks Karl for mentioning dberr.  This helped with a problem in ontimer 
code that was hard to locate.  Thanks to dberr, I got a real line 
number and went right to the error.  Now that I know what I'm trying to 
work on, I'd like to run a resolution past you.

Here's the situation.  Assume the string Hr = 'transition';

The code that raises an error is, and the error is that it's illegal to 
call split on not a valid string.

var a = window.getComputedStyle(e), s = a[Hr + 'Delay'].split(', ')

I'm assuming these two statements are related because the second statement 
is called on a, the return value of the first.  So I read this to say that 
after gcs is called, the program assumes it can have free reign to 
reference transitionDelay and other properties and assume they are 

I checked in Firefox, and an object returned from gcs has about 500 
different style properties with the default value "", including:
transition: ""
transitionDelay: ""
transitionDuration: ""
transitionProperty: ""
transitionTimingFunction: ""

Karl, is there a best place to set this up, such as in createElement or 
getComputedStyle?  And do you think I should set up hundreds, or just set 
up the ones I know are referenced and do more when a program tries to find 
them?  The latter would mean that we should bear in mind that this can be 
a major reason for runtime errors-- maybe it's better to set up the whole 
A-Z slate now.


             reply	other threads:[~2019-09-08 23:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08 23:23 Kevin Carhart [this message]
2019-09-08 23:50 ` Karl Dahlke
2019-09-09  0:48   ` Kevin Carhart
2019-09-08 23:28 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:

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

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1909081602280.83820@phoenix \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \


* 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).