nightly problems even without e10s enabled

[trlkly]

The dialogs won't open, and the settings don't apply unless you select the zoom level in the status bar icon.

Please update this! You've said you would. I will have to stop updating Firefox if this addon doesn't get updated.

[jtackaberry]

I'm not sure where I said I would. I know I said I would try, but I've posted several times here and elsewhere that unfortunately I've been having a hard time to find the time in life to work on NoSquint.

Indeed, I did try with a couple free evenings last month. But Firefox's introduction of backward incompatible changes has outpaced my ability to keep up with it. :(

There are alternative addons that might suit your needs, for example the Zoom Page addon.

[trlkly]

Zoom pages doesn't let you set the page zoom and text zoom at the same
time. I find this is often necessary. I'm not sure why more people don't seem to have noticed.

In the Firefox bug, you did say you thought you could fix it. They were talking of having someone else take over, but, because you replied, it was was assigned to you. You've not come back to Bugzilla to say otherwise, as far as I know.

NoSquint and Tab Mix Plus are the two reasons I use Firefox instead of
Chrome. Neither appears to be possible with their extensions. Chrome has a rudimentary text scaling extension, but it waits until the page has loaded entirely to work, rather than even starting at DOMContentLoaded.

The errors I noticed in Firefox 47 look like they have something to do with external scripts not loading. I note that it says the Jquery $ function isn't a function. So I was really hoping this much was an easy fix. I'm sorry it was not.

I am trying to make do with lesser addons and UserCSS injection. But please go to Bugzilla and report that you will not be able to fix the addon if that is the case.

[jtackaberry]

Which bugzilla bug are you referring to? It would be terribly uncharacteristic of me to turn down help. That is, if it was assigned to someone who was willing to submit a patch, I just don't see myself jumping in and pushing them out of the way.

Today I've formally stepped down as maintainer of NoSquint. I apologize for letting NoSquint bitrot to the degree that it has. I really should have shuttered the project sooner. I thought it would just take a couple evenings to fix things up, but I have recently realized Firefox has evolved to the point now that an architectural overhaul is necessary, and it's something I don't have the time to invest in.

If you can link me to that post from a developer who offered (or was otherwise prepared) to fix the issue you're reporting, I will approach them to see if they're willing to pick up the torch.

[trlkly]

Oh, no. That's not what I mean. I'm not saying someone else volunteered to
take it on. I am saying that the bug was filed with the idea that anyone
else could take it. But then it was assigned to you.

It is in fact the same bug that you've gotten closed.

On Sun, Apr 10, 2016 at 5:35 PM, Jason Tackaberry [email protected]
wrote:

Which bugzilla bug are you referring to? It would be terribly
uncharacteristic of me to turn down help. That is, if it was assigned
to someone who was willing to submit a patch, I just don't see myself
jumping in and pushing them out of the way.

Today I've formally stepped down as maintainer of NoSquint. I apologize
for letting NoSquint bitrot to the degree that it has. I really should have
shuttered the project sooner. I thought it would just take a couple
evenings to fix things up, but I have recently realized Firefox has evolved
to the point now that an architectural overhaul is necessary, and it's
something I don't have the time to invest in.

If you can link me to that post from a developer who offered (or was
otherwise prepared) to fix the issue you're reporting, I will approach them
to see if they're willing to pick up the torch.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#200 (comment)

[jtackaberry]

                                                                                  I see. Yes, addon bugs are filed and unassigned by default. Once the addon author's Bugzilla account is identified then it is assigned. No one else would have done anything about this bug.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         From: trlkly‎Sent: Monday, April 11, 2016 1:22 AMTo: jtackaberry/nosquintReply To: jtackaberry/nosquintCc: Jason TackaberrySubject: Re: [jtackaberry/nosquint] nightly problems even without e10s enabled (#200)Oh, no. That's not what I mean. I'm not saying someone else volunteered to

take it on. I am saying that the bug was filed with the idea that anyone
else could take it. But then it was assigned to you.

It is in fact the same bug that you've gotten closed.

On Sun, Apr 10, 2016 at 5:35 PM, Jason Tackaberry [email protected]
wrote:

Which bugzilla bug are you referring to? It would be terribly
uncharacteristic of me to turn down help. That is, if it was assigned
to someone who was willing to submit a patch, I just don't see myself
jumping in and pushing them out of the way.

Today I've formally stepped down as maintainer of NoSquint. I apologize
for letting NoSquint bitrot to the degree that it has. I really should have
shuttered the project sooner. I thought it would just take a couple
evenings to fix things up, but I have recently realized Firefox has evolved
to the point now that an architectural overhaul is necessary, and it's
something I don't have the time to invest in.

If you can link me to that post from a developer who offered (or was
otherwise prepared) to fix the issue you're reporting, I will approach them
to see if they're willing to pick up the torch.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#200 (comment)

—You are receiving this because you commented.Reply to this email directly or view it on GitHub