From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What do you think about Firefox 57?
Date: Thu, 7 Sep 2017 21:21:50 -0500 [thread overview]
Message-ID: <9b36ec89-2f53-283f-005a-5db7d28ad2c4@gmail.com> (raw)
In-Reply-To: <874lse3ry0.fsf@gmail.com>
Danny YUE wrote:
> On 2017-09-08 00:48, Adam Carter <adamcarter3@gmail.com> wrote:
>> On Thu, Sep 7, 2017 at 10:26 PM, Danny YUE <sheepduke@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I have been using FoxyProxy in Firefox for a really long time, until
>>> today I found its new version really sucks.
>>>
>>> Then I read the comment from author who declared that the old version
>>> can *only* be used before (roughly) end of 2017 before Firefox 57 and in
>>> new version some features must perish.
>>>
>> I am assuming that most actively developed addons will be updated before 57
>> drops, so the transition wont be too painful. Is the issue you're having
>> with FoxyProxy related to it relying on features that are no longer
>> available under the new framework?
> Yes. The FoxyProxy author declared that some features are no long
> available under the new framework.
> I am really depressed about it because I just use that plugin every time
> I use Firefox.
>
>
>> This update will break my favorite extension, Vimperator. I am already
>> looking at replacements for Firefox due to this. So far I have found
>> qutebrowser which isn't really as featureful.
>>
>> R0b0t1.
> I am using Keysnail, no idea whether or not it will be deprecated.
>
> If the features I want are blocked by the new framework, I'm afraid I
> would lock the version (fortunately it's Gentoo) for a long time, until
> I find replacement for plugins, or even Firefox...
>
> Danny
>
>
It's been mentioned before in other threads recently, have you looked at
Palemoon? I have it installed here from a overlay. I haven't checked
on it recently but if this new plugin thing with Firefox leaves some of
my plugins unusable, I may be looking at some other options myself. I
might add, Seamonkey is stepping on a nerve or two of mine as well.
I've been wondering about this plugin thing myself since I heard about
it a few weeks ago. Sort of glad to see a discussion about it. Hoping
to find out what others think this is going to end up looking like.
Dale
:-) :-)
next prev parent reply other threads:[~2017-09-08 2:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 12:26 [gentoo-user] What do you think about Firefox 57? Danny YUE
2017-09-07 12:38 ` konsolebox
2017-09-08 0:00 ` R0b0t1
2017-09-07 12:49 ` Rasmus Thomsen
2017-09-07 13:00 ` Ralph Seichter
2017-09-07 13:20 ` Danny YUE
2017-09-07 14:47 ` Ralph Seichter
2017-09-07 15:36 ` Danny YUE
2017-09-07 20:04 ` Dale
2017-09-07 20:30 ` Ralph Seichter
2017-09-07 21:24 ` Dale
2017-09-07 22:05 ` Mick
[not found] ` <8a43ebb9-c908-0f75-5977-5297826451ff@monksofcool.net>
2017-09-07 22:24 ` Dale
2017-09-11 1:24 ` Daniel Campbell
2017-09-08 0:48 ` Adam Carter
2017-09-08 1:22 ` Danny YUE
2017-09-08 2:20 ` R0b0t1
2017-09-08 2:21 ` Dale [this message]
2017-09-08 3:08 ` R0b0t1
2017-09-08 5:59 ` Taiidan
2017-09-11 1:19 ` Daniel Campbell
2017-09-11 2:20 ` Danny YUE
2017-09-11 15:46 ` Walter Dnes
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=9b36ec89-2f53-283f-005a-5db7d28ad2c4@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox