Closed
Bug 544071
Opened 16 years ago
Closed 16 years ago
Unresponsive script dialog "Yes" option not clear
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: marcia, Assigned: mfinkle)
Details
Attachments
(3 files, 1 obsolete file)
Seen while running 20100202 build.
STR:
1. Visit a site that generates an unresponsive script dialog. In my case it was addons.mozilla.org
2. Observe the UI in the attached screenshot
| Reporter | ||
Comment 1•16 years ago
|
||
| Reporter | ||
Comment 2•16 years ago
|
||
Aakash showed me that by pressing the key that the yes shows, but in some way the UI seems funny in this respect so leaving this bug open for the UI issue.
Summary: [WinMo] Unresponsive script dialog missing "Yes" option → [WinMo] Unresponsive script dialog "Yes" option not clear
Comment 3•16 years ago
|
||
Maybe it's because I'm not a native English speaker, but even it was more clear for the user to choose between the yes and no option, I don't think the wording in the dialog is very nice. Don't ask me again: "Yes" - what does that mean?
I am confused if I should select, Don't ask me again - "No" <, don't ask me again>, or Don't ask me again - "Yes" <I select not to be asked again> - I could be simplified by removing a negation(?) and change the text to something like: "Ask me again?" where the user has to choose the answer (yes/no). Or even better if possible, let the user choose between "Ask me again" and "Don't ask me again"
Comment 4•16 years ago
|
||
This isn't winmo only as this dialog is common across all platforms. I also agree that the wording is very confusing. Madhava, your thoughts please?
Assignee: nobody → madhava
Summary: [WinMo] Unresponsive script dialog "Yes" option not clear → Unresponsive script dialog "Yes" option not clear
Comment 5•16 years ago
|
||
This is definitely an awkward wording, and comes from our changing from a wordless checkbox to standard [yes/no] toggles. More than awkward, actually -- really confusing.
To make it work with a [yes/no], one better phrasing would be:
Ask every time [yes/no] **note that this involves reversing the yes/no meanings.
| Assignee | ||
Comment 6•16 years ago
|
||
If anyone has ideas on how we could invert the meaning of the boolean passed to the promptservice, let me know.
| Assignee | ||
Comment 7•16 years ago
|
||
I pitched a different idea to Brad. What if we used a button for the question instead of a label and a yes/no toggle?
Instead of:
"Don't ask me again" [yes|no]
Think of:
( [x] Don't ask me again )
The label and a check/uncheck image would be on a button. The user could press the full button to toggle.
Comment 8•16 years ago
|
||
(In reply to comment #7)
<SNIP>
> Think of:
>
> ( [x] Don't ask me again )
>
> The label and a check/uncheck image would be on a button. The user could press
> the full button to toggle.
Do you mean that the text on the button change between:
( [x] Don't ask me again )
and:
( [ ] Don't ask me again )
?
| Assignee | ||
Comment 9•16 years ago
|
||
(In reply to comment #8)
> Do you mean that the text on the button change between:
>
> ( [x] Don't ask me again )
>
> and:
>
> ( [ ] Don't ask me again )
Exactly
Comment 10•16 years ago
|
||
(In reply to comment #9)
> (In reply to comment #8)
>
> > Do you mean that the text on the button change between:
> >
> > ( [x] Don't ask me again )
> >
> > and:
> >
> > ( [ ] Don't ask me again )
>
> Exactly
Definitively better than what we have now. (And similar to what users see on PC's - so as long as it fits with the way we do it in other places in Fennec (Madhava your comments?), then it's probably the best solution.)
| Assignee | ||
Comment 11•16 years ago
|
||
This patch tweaks the confirm dialog to use a button-checkbox instead of a label and [yes/no] toggle.
We need a real checked/unchecked image and some styling.
screenshot:
http://people.mozilla.com/~mfinkle/fennec/screenshots/fennec-prompt-buttoncheck-01.png
http://people.mozilla.com/~mfinkle/fennec/screenshots/fennec-prompt-buttoncheck-02.png
Assignee: madhava → mark.finkle
| Assignee | ||
Comment 12•16 years ago
|
||
This patch:
* adds check and uncheck images
* removes any button styling
* removes the focus rectangle (it is still in the screenshots though)
Examples:
http://people.mozilla.com/~mfinkle/fennec/screenshots/fennec-confirm-buttoncheck.png
http://people.mozilla.com/~mfinkle/fennec/screenshots/fennec-confirm-buttoncheck-unselected.png
http://people.mozilla.com/~mfinkle/fennec/screenshots/fennec-confirm-buttoncheck-portrait-unselected.png
Attachment #435341 -
Attachment is obsolete: true
Attachment #443447 -
Flags: review?(21)
Attachment #443447 -
Flags: review?(21) → review+
| Assignee | ||
Comment 13•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 14•16 years ago
|
||
Comment 15•16 years ago
|
||
Is there a way to create a testpage which will bring up the unresponsive script dialog in a always reproducible way?
| Assignee | ||
Comment 16•16 years ago
|
||
(In reply to comment #15)
> Is there a way to create a testpage which will bring up the unresponsive script
> dialog in a always reproducible way?
I don't know of any, but you can get the same type of dialog to appear by having more than 1 tab open in Fennec and then close the app. You should get the "Close tabs" dialog, with a checkbox widget.
Comment 17•16 years ago
|
||
This triggers the unresponsive script dialog for me on fennec.
It seems to completely hang current trunk builds of Firefox, though (I thought the unresponsive script dialog should appear there, too?).
Comment 18•16 years ago
|
||
verified FIXED on builds:
Mozilla/5.0 (X11; U; Linux armv7l; Nokia N900; en-US; rv:1.9.2.5pre) Gecko/20100506 Namoroka/3.6.5pre Fennec/1.1b2pre
and
Mozilla/5.0 (X11; U; Linux armv71; Nokia N900; en-US; rv:1.9.3a5pre) Gecko/20100506 Namoroka/3.7a5pre Fennec/2.0a1pre
Status: RESOLVED → VERIFIED
Updated•15 years ago
|
Component: Windows Mobile → General
OS: Mac OS X → Windows Mobile 6 Professional
QA Contact: mobile-windows → general
Hardware: x86 → All
You need to log in
before you can comment on or make changes to this bug.
Description
•