Closed
Bug 770873
Opened 12 years ago
Closed 10 years ago
Different behavior when loading about:config using a new profile or an old one
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox14 affected, firefox15 affected, firefox16 affected)
RESOLVED
WORKSFORME
People
(Reporter: paul.feher, Unassigned)
References
Details
Nightly Fennec 16.0a1 (2012-07-04) Aurora Fennec 15.0a2 (2012-07-03) Firefox 14 Beta 10 Device: HTC Desire Z OS: Android 2.3.3 Steps to reproduce: 1. Open Fennec with a new profile. 2. Load about:config. 3. Visit any webpage. 4. Load about:config again. Expected: There should be no entries in about:config list only the search field and the "add new setting" button should be present Actual: After step 2 the about:config list is loaded containing the search field, "add new setting" button and other 6 entries. After step 4 the about:config list is loaded containing only the search field and the "add new setting" button.
Reporter | ||
Updated•12 years ago
|
Comment 1•12 years ago
|
||
I'm unable to reproduce this. There's nothing in the code that would indicate a change without a search.
Reporter | ||
Comment 2•12 years ago
|
||
I can reproduce this also on: Samsung Galaxy Nexus - Android (4.0.2) Please see the video. http://youtu.be/O0cVAUpXXUU
(In reply to Aaron Train [:aaronmt] from comment #1) > I'm unable to reproduce this. There's nothing in the code that would > indicate a change without a search. wouldn't this do it? http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/config.xhtml#192
Comment 4•12 years ago
|
||
Yeah, we're observing changes and adding new items for new prefs. We could update the observer code to ignore these new items if there's no search string.
Comment 5•10 years ago
|
||
Also Superceded by the new about:config ... ok to close?
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•