42436 - Changes to wallet demo pages

Status: VERIFIED FIXED

(Toolkit :: Form Manager, defect, P3)

Description

[Daniel Veditz [:dveditz]]

The Form Manager menu contains test items like "Demonstration" and "Prefill 
Form Quickly" that need to be removed before we ship.

Does this need to be a PR2 task, or is PR3 ok? Either way, creating this bug 
for tracking.

Comment 1

[Stephen P. Morse]

Yes, for prefill quickly.  That definitely has to come out of the optimized 
builds.  My intention is to bracket it with if-debug so we can still play around 
with it in debug builds.

The demo on the other hand should remain in the product.  It gives the user a 
quick hands-on facility for playing with wallet and seeing what it can do.  The 
problem with trying this with real websites are:

1. It's not easy to get to a form on a real website.  You need to navigate 
through the site, figure out how to buy something, get it into your cart, and 
then get to checkout.  The demo gets you there immediately

2. You can't do "submit" on a real website without running the risk of buying 
something.  On the demo sites you can press submit all you want and nothing 
should happen.

However, the submit on some of the demo sites actually link to the real websites 
as Vera discovered when she accidently registered with e-bay when she was trying 
out the demo.  This needs to be fixed up so that the submit on the demo pages 
does not link back to the real website.

Comment 2

[Stephen P. Morse]

Nominating for nsbeta2 because this wa considered to be an nsbeta2 issue at John 
Gable's wallet review meeting on June 12.

Comment 3

[Daniel Veditz [:dveditz]]

My main concern with the "demonstration" item is that it points out the fact 
that we have copies of other people's site designs on the mozilla.org site -- 
I'm concerned about copyright problems.

Comment 4

[Stephen P. Morse]

That's a good point.  We can do one of two things:

1. Have a marketing person contact those sites and ask for their permission.  I 
would suspect that they would be happy to give such permission because it is 
free advertising for them.

2. Modify the demo pages so that they do not reflect real websites.

Maybe a combination of both -- some real websites with permissions and some 
purely fictitious sites.

Comment 5

[leger]

Putting on [nsbeta2-] radar. Not critical to beta2.  Putting on nsbeta3 keyword 
radar.

Comment 6

[Stephen P. Morse]

Prefill form quickly has been removed.  That covers first item of this bug 
report.  Still need to work on the demo pages.

Comment 7

[Stephen P. Morse]

I just modified the demo pages so that they do not do anything when you submit 
the form.  Vera reported that she actually signed up with ebay without intending 
to because she was playing with the demo forms.

My part of this is finished.  I guess it's now up to marketing to determine if 
we can get permission from the sites to use their pages in our demo.  If that's 
not possible, assign it back to me and I'll replace the pages with fictitious 
forms.

Comment 8

[Stephen P. Morse]

Resummarizing

Comment 9

[johng]

Looks like we are doing option 2 - modifying the demo pages to *not* use real 
web sites.

Adding keyword netcenter since they will have to host this and make some 
changes.  [e-mail] will manage this.

A client side change will need to be made so that the menu link points to the 
new Netcenter URL for the demo page.  See new bug 45096

But what should those content changes be exactly?

Changing subject to "Changes to wallet demo pages" from "Get permission to use 
wallet demo pages".

Reassigning to verah.  After all, these demo pages are essentially playing a 
help docs role, so her input would be very valuable and she can make a 
recommendation on what we should do.

One usability concern: 
The user has 4 places to look to understand the feature: Interview, 
Demonstration, Preferences, and some place in docs to explain what the feature 
and individual pieces are.

Brainstorm for folks to consider.  Why don't we ask docs to build a "1 stop 
shopping" page, a step by step guide that could serve as the "home/index page" 
for all 4 of these pieces.  It would have links to and leverage all of this 
stuff (interview, demonstration, etc), but give the user just one place to look. 
 We might even be able to reduce the number of different menu items under Tasks 
if we do this right.  I think we could make this simpler to understand for a 
novice user.

Don't know if that is the right answer or not and don't know what we can do for 
beta2, but verah with jglick can drive a recommendation.

Comment 10

[verah (gone)]

Accepting. I'll take a look at this ASAP... I think we can come up with 
something really good for this.

Comment 11

[verah (gone)]

Bug 48860 is a meta bug tracking the UI requests for enhancements for Password 
Manager and Forms Manager. I marked this bug as blocking that bug. Reassigning 
to hangas as part of the Password Manager/Forms Manager *future* UI support.

Comment 12

[verah (gone)]

Nevermind... I just read back over this bug, and now realize that all but one of 
the issues it discusses have been resolved. The remaining issue -- combining the 
Interview and Demo functions -- is being discussed in other places. Marking this 
bug FIXED.

Comment 13

[sairuh (rarely reading bugmail)]

...and verifying.