508387 - zoom settings not stored

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[BUGabundo]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090803 Ubuntu/9.10 (karmic) Minefield/3.6a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090803 Ubuntu/9.10 (karmic) Minefield/3.6a1pre

I've been using this addon for a while:
http://urandom.ca/nosquint/
it allows me to set certain zoom settings per page, and control at the same time both page and text zoom, unlike Firefox default.

earlier on 3.6, support for this addon broke. it was later fixed with addon version 2.0b6.
but with yesterday firefox build, support got broken again.

Reproducible: Always

Steps to Reproduce:
1.set a zoom setting for a page
2.reload the page or change to another
3.
Actual Results:  
zoom defaults to 100% but addon states its the old value

Expected Results:  
for firefox to keep user set zoom

[UPGRADE] firefox-3.6 3.6~a1~hg20090717r30390+nobinonly-0ubuntu1~umd1 -> 3.6~a1~hg20090718r30417+nobinonly-0ubuntu1~umd1
[UPGRADE] firefox-3.6-branding 3.6~a1~hg20090717r30390+nobinonly-0ubuntu1~umd1 -> 3.6~a1~hg20090718r30417+nobinonly-0ubuntu1~umd1

should be in one of this two revisions

Comment 1

[Dave Garrett]

Please report problems with non-Mozilla add-ons to their developers.

Comment 2

[BUGabundo]

(In reply to comment #1)
> Please report problems with non-Mozilla add-ons to their developers.

I did email him about this (he doesnt seem to have an account on this BTS so I couldnt CC him).

But I'm not sure this is a bug in the addon, but a regression on FF.
Unless something changed, and now the addon needs to catch up.

Comment 3

[Dave Garrett]

(In reply to comment #2)
> Unless something changed, and now the addon needs to catch up.

That's usually the case. Add-ons break under Minefield all the time.

(In reply to comment #2)
> But I'm not sure this is a bug in the addon, but a regression on FF.

Always possible. If it is, that's generally something the extension developer should investigate and then file a bug for it, not the other way around. If someone does find an issue that's a specific Mozilla bug, feel free to file a bug for it, though. Seeing as you noted that support broke and was fixed previously, there's a good chance it's a similar thing this time.

Comment 4

[BUGabundo]

FYI I'm having trouble reproducing this with todays build.
So it seems it was a regression that self healed.
I'll update this if anything changes.

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090804 Ubuntu/8.04 (hardy) Minefield/3.6a1pre ID:20090804155037

  Installed: 3.6~a1~hg20090804r31113+nobinonly-0ubuntu1~umd1~hardy