From: Mike Gerwitz <mtg@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 32820@debbugs.gnu.org
Subject: bug#32820: Some CSS not displaying in latest Icecat
Date: Fri, 28 Sep 2018 21:03:50 -0400 [thread overview]
Message-ID: <87o9ch8689.fsf@gnu.org> (raw)
In-Reply-To: <87bm8mehde.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 24 Sep 2018 23:05:17 +0200")
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On Mon, Sep 24, 2018 at 23:05:17 +0200, Ricardo Wurmus wrote:
> Open the developer console and switch to the Style Editor tab. On
> github.com you’ll see a bunch of CSS files with a note under each saying
> “0 rules”. To the right you see the CSS sources. Now add a space
> character (or make some other edit in the source pane): all of a sudden
> the CSS file can be parsed!
>
> When you do this to each file, Icecat is going to render the page just
> fine.
That's an interesting find!
Fortunately, since Mark's changes, I haven't experienced any further
issues. But it's bizarre indeed.
> I also note that Icecat tells me that the page is not encrypted, despite
> visiting the https site without errors. Something’s not quite right
> here.
Mark fixed this in 32833 (<87a7o5cdv3.fsf@netris.org>).
--
Mike Gerwitz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2018-09-29 1:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 14:08 bug#32820: Some CSS not displaying in latest Icecat Christopher Lemmer Webber
2018-09-24 21:05 ` Ricardo Wurmus
2018-09-29 1:03 ` Mike Gerwitz [this message]
2018-09-25 3:21 ` Mark H Weaver
2018-09-25 4:13 ` Mike Gerwitz
2018-09-26 0:22 ` Mark H Weaver
2018-09-26 0:33 ` Mike Gerwitz
2018-09-26 4:55 ` Mike Gerwitz
2018-09-26 16:19 ` Christopher Lemmer Webber
2018-09-26 16:19 ` Christopher Lemmer Webber
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=87o9ch8689.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=32820@debbugs.gnu.org \
--cc=rekado@elephly.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.