Closed
Bug 840703
Opened 12 years ago
Closed 12 years ago
Adblock settings missbehaving
Categories
(Firefox for Android Graveyard :: Add-on Manager, defect)
Tracking
(fennec+)
VERIFIED
FIXED
Firefox 22
| Tracking | Status | |
|---|---|---|
| fennec | + | --- |
People
(Reporter: micmon, Assigned: wesj)
Details
Attachments
(1 file)
|
3.47 KB,
patch
|
mbrubeck
:
review+
|
Details | Diff | Splinter Review |
Pressing the "filter subscription" list button in Adblock settings does not show the list most of the time, it just darkens the screen.
In very rare cases (one in 20 maybe) the llist is actually displayed. Pressing one item selects the item above it, which will not be the value shown in the list button. However, there is now way to actually save this, pressing "back" reverts the value to "Easylist".
Updated•12 years ago
|
Assignee: nobody → wjohnston
tracking-fennec: ? → +
| Assignee | ||
Comment 2•12 years ago
|
||
I am not entirely sure what's going wrong here. AFAICT, Adblock ships a control that looks like:
<setting type="control" title="&subscriptions.tab.label;">
<menulist id="adblockplus-subscription-list"/>
</setting>
and fills in the list at some point, so I think this may be a race. I also realized we really don't need this binding for menulist anymore though. SelectHelper already intercepts clicks for us, and the rest of the code in there seemed to be for hiding the gtk popup, which we no longer show anyway?
Removing that binding seems to fix the problem for me. I wonder if our binding and click handling was interfering with adblock creating the filter list?
Attachment #716762 -
Flags: review?(mbrubeck)
Comment 3•12 years ago
|
||
Comment on attachment 716762 [details] [diff] [review]
Patch
Looks good to me. I think the click-handling here was only needed for <menulist> elements in browser chrome (which /mobile/android no longer uses). For in-content UI like the add-on manager, SelectHelper's event handling is all we need.
Attachment #716762 -
Flags: review?(mbrubeck) → review+
| Assignee | ||
Comment 4•12 years ago
|
||
Comment 5•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 22
Comment 7•12 years ago
|
||
(In reply to Andreea Pod from comment #6)
> I am not able to verify this issue, due to Bug 847002
You can in builds between February 25th and 28th.
No longer depends on: 847002
Comment 8•12 years ago
|
||
Verified fixed on:
-build: Firefox for Android 22.0a1 (2013-02-27)
-device: Samsung Galaxy Nexus
-OS: Android 4.1.1
Status: RESOLVED → VERIFIED
Updated•5 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
•