From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] rawstory and CSS.. a false start
Date: Sat, 28 Jan 2017 21:57:23 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1701282145440.30255@carhart.net> (raw)
I can get Raw Story to work by taking away the CSSStyleDeclaration
prototype from the very bottom of startwindow.js. I'm not sure if this is
the real cause, or just something that makes the site end early on a bug.
If CSSStyleDeclaration.prototype exists and getPropertyValue is
implemented, you get the seg fault some time after some CSS work, which
does not mean there couldn't be something unreported happening in between:
(my alert statements are shown)
trying to set the style paddingRight to zero
the style was set to zero
trying to set the style borderRightWidth to zero
the style was set to zero
trying to set the style paddingLeft to zero
the style was set to zero
trying to set the style borderLeftWidth to zero
the style was set to zero
trying to set the style display to zero
the style was set to zero
trying to set the style width to zero
the style was set to zero
Segmentation fault (core dumped)
If I erase the CSSStyleDeclaration prototype entirely, plain text articles
on the website are available again, but the diagnostic output has this:
< side effects
l{c|0x7f09c662c440,div 0x0, 0x0, `~@}
l{c|0x7f09c662c4c0,div 0x0, 0x0, `~@}
l{a|0x7f09c6d727c0,body 0x7f09c662c4c0,div 0x0, `~@}
l{a|0x7f09c662c4c0,div 0x7f09c662c440,div 0x0, `~@}
l{r|0x7f09c6d727c0,body 0x7f09c662c4c0,div 0x0, `~@}
TypeError: c.getPropertyValue is not a function
It wants to call getPropertyValue and can't
So maybe all I'm seeing is something comparable to the fact that Raw Story
works if you disable js, too.
reply other threads:[~2017-01-29 5:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1701282145440.30255@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).