Last modified: 2012-08-04 21:11:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T39358, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37358 - FF has wrong AFT UI?
FF has wrong AFT UI?
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
ArticleFeedbackv5 (Other open bugs)
master
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 39043
  Show dependency treegraph
 
Reported: 2012-06-05 22:23 UTC by Chris McMahon
Modified: 2012-08-04 21:11 UTC (History)
1 user (show)

See Also:
Web browser: Firefox
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
wrong_ui_in_FF? (56.41 KB, image/png)
2012-06-05 22:23 UTC, Chris McMahon
Details
second view (63.04 KB, image/png)
2012-06-05 22:24 UTC, Chris McMahon
Details

Description Chris McMahon 2012-06-05 22:23:32 UTC
Created attachment 10693 [details]
wrong_ui_in_FF?

I see a consistent difference in Chrome vs. Firefox on the AFT input form at http://en.wikipedia.org/wiki/Golden-crowned_Sparrow

See screen shots.  Chrome on the left, FF on the right. 

inconsistent_ui1 shows before clicking, inconsistent_ui2 show after clicking "No" in FF
Comment 1 Chris McMahon 2012-06-05 22:24:24 UTC
Created attachment 10694 [details]
second view

showing further detail of unexpected UI in FF
Comment 2 Fabrice Florin 2012-06-05 22:56:02 UTC
Thanks, Chris!

What you are experiencing here is completely expected as part of the Metrics test 5 we just launched today, as outlined in this Bugzilla ticket:
https://bugzilla.wikimedia.org/show_bug.cgi?id=37287

We are in the process of doing an A/B test between what we call Option 1 (the original feedback form) and Option 6 (the new feedback form we just launched today). The bucketing between these options is 50% - 50%, so it is perfectly normal for you to see these different forms on different browsers.

We are trying to measure volume, quality and user satisfaction for these two forms, to determine which one to deploy more widely.

So unless you see other issues beyond the differences between these two forms, I think we should close down this ticket, or lower its priority.

Much appreciated!


Fabrice
Comment 3 Chris McMahon 2012-06-05 23:07:50 UTC
If this is switching is per-session, then what I saw makes sense.  I thought it was per page view, in which case I was concerned that multiple reloads of the page always yielded the same feedback form. (Thus the "?" in the title.)
Comment 4 Chris McMahon 2012-06-05 23:12:25 UTC
Closing

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links