Closed Bug 537735 Opened 14 years ago Closed 14 years ago

Addition of Report A Problem Mechanism

Categories

(Firefox for Android Graveyard :: General, enhancement)

Fennec 1.1
enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: aakashd, Assigned: marioalv)

Details

Attachments

(3 files, 17 obsolete files)

43.42 KB, application/zip
Details
10.27 KB, application/x-xpinstall
Details
11.63 KB, application/x-xpinstall
Details
I have a running project to implement the broken website reporter onto mobile firefox. We'll use this bug to track the status of the project.

Wiki: https://wiki.mozilla.org/QA/Fennec/Planning/2010/Reporter
Summary: Addition of Broken Website Reporter → Addition of Report A Problem Mechanism
(In reply to comment #0)
> I have a running project to implement the broken website reporter onto mobile
> firefox. We'll use this bug to track the status of the project.
> 
> Wiki: https://wiki.mozilla.org/QA/Fennec/Planning/2010/Reporter

With the change of summary does this mean that there are plans to convert the reporter into a product and website issue reporter?
Right, now the plan is to implement it as an extension and go from there. Madhava, I'd like to get your opinion on the mock-ups.
i can take a look at writing the extension. This could help to refine the mockups.
(In reply to comment #2)
> Right, now the plan is to implement it as an extension and go from there.
> Madhava, I'd like to get your opinion on the mock-ups.

On a side note, I am curious as to the similar approaches planned for implementation in the mobile version of QAC. It seems like there may be a cross of paths and possible redundancies (i.e., issue reporter).
Fabrice, Marco Alvarado and Jorge Villalobos are going to be developing this extension. Thanks for possibly volunteering though :)
There are still some bugs to be fixed:

Aakash feedback:
* go to combo box and don't change a selection. click done and dialog disappears
* Let's try a simpler (to the user) approach to system page support for reporter blocking. I'd suggest something like graying it out.
* when a user clicks outside the dialog, let's have it disappear. it'll make the UI cleaner. the edit bookmarks dialog (open right sidebar, click on bookmarks star, click on edit button) uses this behavior
* we need to sanitize urls that have passwords associated with them, so they're not posted to a public database (they're not sanitized on reporter.mozilla.org)
Fabrice, when we install the add-on, radio buttons show up on the search bar and the yes/no preferences show as checkboxes in the controls panel. When we disable the add-on they go away.

Do you know what might be happening?
Never mind, the issue was due to the code calling chrome://global/skin/ xml stylesheet.
Attachment #426607 - Attachment is obsolete: true
If I begin testing, did you want all bugs reported in this meta bug?
Yep, that'd be great Aaron!
Attachment #426604 - Attachment is obsolete: true
Attachment #426615 - Attachment is obsolete: true
Attachment #426715 - Attachment is obsolete: true
Attachment #428256 - Attachment is obsolete: true
Attachment #426714 - Attachment is obsolete: true
Attachment #428796 - Attachment is obsolete: true
Attachment #428939 - Attachment is obsolete: true
Attachment #428941 - Attachment is obsolete: true
Attachment #428798 - Attachment is obsolete: true
Attachment #428945 - Attachment is obsolete: true
Assignee: nobody → marioalv.mozilla
Status: NEW → ASSIGNED
Attachment #428980 - Attachment is obsolete: true
Attachment #429001 - Attachment is obsolete: true
Attachment #429236 - Attachment is obsolete: true
Mario/Aakash,

Do you have a changelog of the differences between attachments somewhere? (wiki?) as well a listing of what TODO so that I dont bother filing bugs about them?

Thanks
We don't, but I'd suggest testing off of the latest xpi downloaded only. If you have any issues, please feel free emailing me and mario and we'll answer any questions you might have.
We can go ahead and move this to fixed as its now on AMO :

https://addons.mozilla.org/en-US/mobile/addon/87500/
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Bug

Using desktop version of Fennec 1.1a2pre on Windows XP

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIDOMXULEIement.removeChild]" nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame :: chrome://reporterforfennec/content/overlay.js :: anonymous :: line 69" data: no]
Super, thanks for the bug on the new version Wikiwide! Mario is going to take a look at it
Attachment #436045 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: