Asa are we pulling out update checking functionality from this? I think we discussed that it should be a non P1. I think that is best. > An About Firefox Flyout replaces the Settings pane, displaying > the product name, channel, version, and ***an update checking mechanism.*** If so, please move bug 835151 into a dependency for the new story.

I only heard about Bug 835615 being reported in testing this feature and that should be fixed now, so resolving this.

I'd love to have some early testing for this feature to see if anything else is needed to keep this story closed out (which I could tackle on this same iteration).

(In reply to Brian R. Bondy [:bbondy] from comment #3) > I'd love to have some early testing for this feature to see if anything else > is needed to keep this story closed out (which I could tackle on this same > iteration). I am no longer seeing the failures in opening the Options and About Flyouts that I was seeing a week ago in Iteration#1 testing. With Elm nightly (2013-02-09) Built from http://hg.mozilla.org/projects/elm/rev/6b7200b41efb the Flyouts work as expected.

Awesome, thanks Asa!

Tested on 2013-02-13 Nightly built from http://hg.mozilla.org/mozilla-central/rev/aceeea086ccb - Tested that the About Flyout appeared consistently, going back and forth between displaying the Settings and the About panel. - Tested this on a tablet as well, where I checked that the About Flyout appeared regardless of orientation, and that the panel was re-drawn when I reoriented the view. - The elements of the About Flyout are almost as described in the story, taking into account changes added to the bug, but not to the story like the ability to update from this About Flyout panel.

Re-verfied for it4 testing and everything passes without any issues. Used the following build: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013-04-10-06-59-39-mozilla-central/ - As Juan mentioned in Comment 6, the ability to update the browser through the "About" Flyout panel is currently not implemented - Couldn't test thet tablet portion of the Story as I don't own a tablet (only touch laptop) Went through the following extra test cases: - Went through the test cases Juan outlined in Comment 6 - Ensured that the "Read the Nightly privacy policy online" link takes you to the correct website - Ensured that the information on the "About" screen is correct and displayed correctly - Ensured that you can access the "About" Flyout while the "App Bar" is visible - Ensured that you can access the "About" Flyout while the "Navigation App Bar" is visible

verified items in comment 7. This fails on : * The Flyout should full screen height, regardless of orientation, and should be one of two specific widths, narrow (346 pixels) or wide (646 pixels). - widths are not aligned with these standard widths. * The Flyout header should include a back button, the name of the entry point that opened the Flyout, and the app’s icon. - none of the flyout have the app icon.

Yuan, curious about these two failures. Are we supposed to be standardizing on flyout widths, and are we missing an app icon or was that dropped at some point? The story here might be out of date.

(In reply to Jim Mathies [:jimm] from comment #9) > Yuan, curious about these two failures. Are we supposed to be standardizing > on flyout widths, and are we missing an app icon or was that dropped at some > point? The story here might be out of date. I believe we should use the standard width for flyout width. We should adjust the width to 346px if the current one doesn't meet the standard. No app icon on the flyout is a design decision. First, I don't think the app icon is a standard requirement for flyout. Lots of non Microsoft apps don't have it. Second, Without texts, the flat Nightly icon is not very recognizable. So I decided not to include it in the flyout, so that the users can focus on the content better.

(In reply to Yuan Wang(:Yuan) – Firefox UX Team from comment #10) > (In reply to Jim Mathies [:jimm] from comment #9) > > Yuan, curious about these two failures. Are we supposed to be standardizing > > on flyout widths, and are we missing an app icon or was that dropped at some > > point? The story here might be out of date. > > I believe we should use the standard width for flyout width. We should > adjust the width to 346px if the current one doesn't meet the standard. > > No app icon on the flyout is a design decision. First, I don't think the app > icon is a standard requirement for flyout. Lots of non Microsoft apps don't > have it. Second, Without texts, the flat Nightly icon is not very > recognizable. So I decided not to include it in the flyout, so that the > users can focus on the content better. Thanks. Filed polish bug 876816 on the widths.

Went through the following "Story" for iteration #9 testing without any issues. Used the following build: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013-07-03-03-13-23-mozilla-central/ - Went through the original story that has been attached without any issues - Went through the test cases from comment 7 without any issues - Ensured everything described in comment 10 matched the behavior - Ensured that all of the above test cases also worked while in "Filled View" Note: Bug 876816 is still an issue as the "About" flyout width doesn't match the other flyouts

User Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:26.0) Gecko/20100101 Firefox/26.0 Build ID: 20130808030205 Built from http://hg.mozilla.org/mozilla-central/rev/fd4cf30428b0 WFM Tested on windows 8 using latest nightly for iteration-11. Followed steps provided in user story and got expected result.

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 Build ID: 20130826074752 Built from http://hg.mozilla.org/mozilla-central/rev/14b1e8c2957e WFM Tested on windows 8 using latest nightly for iteration-12. Followed steps provided in user story and got expected result.