unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ngillmann@runbox.com>
To: 22115@debbugs.gnu.org
Subject: bug#22115:
Date: Tue, 27 Sep 2016 17:37:55 +0000	[thread overview]
Message-ID: <87inthjlak.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87r385jnh7.fsf@we.make.ritual.n0.is>

ng0 <ngillmann@runbox.com> writes:

> Hi,
>
> Firefox 47.0.1, windows 7: no broken css.
>
> Is this enough to close this bug?

Otherwise I'd say we need more input on how this specific firefox
renders the page, the implemented css support, the proof that the person
who reported this bug has experienced this bug with no added
addons/extensions, etc (basically: is is reproducible, and if yes, how?
... that's why I want (in the future) what Gentoo is doing for
Chrom(e/ium) / Firefox based browsers, a global extensions store.. And
to eliminate the need to contact mozilla/google cdn servers about
addons, and some more reasons).
-- 
              ng0

  reply	other threads:[~2016-09-27 17:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08  8:39 bug#22115: WWW: Package Issues website has broken CSS Jan Synáček
2016-09-27 16:50 ` bug#22115: ng0
2016-09-27 17:37   ` ng0 [this message]
2016-09-27 17:53   ` bug#22115: Leo Famulari
2016-11-26  1:12 ` bug#22115: Luis Felipe López Acevedo
2016-12-15  1:36 ` bug#22115: (no subject) Luis Felipe López Acevedo
2016-12-18 10:14   ` Ludovic Courtès
2016-12-18 14:30     ` Luis Felipe López Acevedo
2016-12-18 21:51       ` Ludovic Courtès
2016-12-20 16:49         ` Luis Felipe López Acevedo
2016-12-17 19:14 ` Luis Felipe López Acevedo

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87inthjlak.fsf@we.make.ritual.n0.is \
    --to=ngillmann@runbox.com \
    --cc=22115@debbugs.gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).