[8.1] [MP] Story - Windows 8.1 specific Regressions

RESOLVED FIXED

Status

defect
P1
normal
RESOLVED FIXED
6 years ago
6 months ago

People

(Reporter: asa, Assigned: bbondy)

Tracking

Details

(Whiteboard: [8.1] [preview] feature=story c=Other_charms_and_integration u=metro_firefox_user p=8)

Attachments

(3 attachments)

Reporter

Description

6 years ago
All of the functionality we've built must work well in Windows 8.1.  This story is not calling for new 8.1 features.
Reporter

Updated

6 years ago
Depends on: 894039
Reporter

Updated

6 years ago
Depends on: 893412
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Assignee

Comment 1

6 years ago
Re-opening based on us having many problems (nothing too major in 8.1)
p=8
Assignee: nobody → netzen
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee

Updated

6 years ago
Depends on: 901002, 901025, 901071
Assignee

Comment 2

6 years ago
CC ally
This is a list of bugs just to get 8.1 working up to par to 8.0, not specific to any enhancements in 8.1. CCing for list-adding (I was having trouble accessing that page Jim setup).
Assignee

Updated

6 years ago
No longer depends on: 894039
Hey Brian, are you taking this for Iteration #12 or in the future?
Blocks: metrov1backlog
No longer blocks: metrov1it0
Flags: needinfo?(netzen)
Summary: Story - Windows 8.1 specific Regressions [8.1] → [8.1] Story - Windows 8.1 specific Regressions
Whiteboard: feature=story c=Other_charms_and_integration u=metro_firefox_user p=0 [8.1] → [8.1] feature=story c=Other_charms_and_integration u=metro_firefox_user p=8
Hi Asa, would you like this added to the Metro Preview list?
Status: REOPENED → NEW
Flags: needinfo?(asa)
Assignee

Comment 5

6 years ago
I was blocked on some apzc work so was looking into 8.1 during a couple days of this iteration. But it won't be completed this iteration, so probably the next one I'll signup for this.

This story will only cover "must have 8.1 work" to put it at part with 8.0.
Flags: needinfo?(netzen)
Assignee

Updated

6 years ago
Depends on: 896627
Reporter

Comment 6

6 years ago
(In reply to Brian R. Bondy [:bbondy] from comment #5)
> I was blocked on some apzc work so was looking into 8.1 during a couple days
> of this iteration. But it won't be completed this iteration, so probably the
> next one I'll signup for this.
> 
> This story will only cover "must have 8.1 work" to put it at part with 8.0.

I'm in agreement with bbondy. We must not be broken in 8.1 because that is the release our users will have when we ship. We must also be careful not to slip into doing things for 8.1 that aren't needed. So a bug to track issues that make us un-shipworthy on 8.1 is useful.
Flags: needinfo?(asa)
Summary: [8.1] Story - Windows 8.1 specific Regressions → [8.1] [MP] Story - Windows 8.1 specific Regressions
Whiteboard: [8.1] feature=story c=Other_charms_and_integration u=metro_firefox_user p=8 → [8.1] [Metro Preview] feature=story c=Other_charms_and_integration u=metro_firefox_user p=8
Depends on: 897699
Whiteboard: [8.1] [Metro Preview] feature=story c=Other_charms_and_integration u=metro_firefox_user p=8 → [8.1] [preview] feature=story c=Other_charms_and_integration u=metro_firefox_user p=8
No longer depends on: 897699
Priority: -- → P1
Assignee

Updated

6 years ago
Depends on: 914351
Blocks: metrov1it15
No longer blocks: metrov1backlog
Status: NEW → ASSIGNED
QA Contact: jbecerra
Assignee

Comment 7

6 years ago
This is happening with Chrome too
Assignee

Comment 8

6 years ago
(In reply to Brian R. Bondy [:bbondy] from comment #7)
> This is happening with Chrome too

sorry that comment was meant for bug 914351
Assignee

Updated

6 years ago
Status: ASSIGNED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Please see below (comment 9, comment 10 and comment 11) the results of our testing for this story, from both PASS and FAIL categories:

Nightly with build ID 20131002030201 and build ID 20131003030203

PASS

1) enter an URL
2) add new tabs
 - with CTRL + T
- using Junior-style button
- from tab bar button
3)  close tabs
4) close the browser, in Metro mode
5) add/remove a bookmark
6) download from http://nightly.mozilla.org/
7) Nightly downloaded and installed properly + after setting it as default browser, the Metro icon appears on the start screen and Metro works as expected
8) access flyouts: About, Options, Help, Permissions
9) session restore
10) used desktop Firefox and Metro simultaneously
11) reloading sites
12) search from the app bar
13) Pin, Unpin, and Restore a Top Site
14) Back and forward navigation from the Firefox app bar
15) Domain highlighting
16) access sites from sections: Bookmarks, Recent History, Top Sites
17) find in page- buttons and keyboard shortcuts
18) text selection
19) right click options 
20) Bookmarks & History tiles
21) image rendering, save/options
22) open downloaded file from downloads app bar
23) toggle remember password options 
24) close all tabs (new tab is displayed)
25) update from Metro interface
26) error console
27) HTML5
28) pop-up notifications
29) Nightly consumption in standby mode


Concerns:

1)Metro in Snapped view: see attached screenshot for the shown display; is this expected?


Are there any other areas that need to be tested?
FAIL

1) jerky scrolling on a site - also happening with Win 8 32-bit and 64-bit, and Aurora Metro interface (see attached screenshot for more details)

2)  Nightly install and first run: the Metro icon is displayed on the start screen, even if the browser was not set as default
3) video & audio playback - FAIL - see https://bugzilla.mozilla.org/show_bug.cgi?id=842639
4) Flash content - missing plugin error even if Flash is already installed
FAIL

1)  display rendering issue if 2 monitors are used (17” and 22”): open Metro FF on the 17” monitor, then drag it to the 22” one (see attached screeshot with the problem)
Flags: needinfo?(netzen)
Assignee

Comment 12

6 years ago
nice find, please post a new bug for it for preview triage.
Flags: needinfo?(netzen)
What about the concern from comment 9 and all comment 10?
Flags: needinfo?(netzen)
Assignee

Comment 14

6 years ago
> 1)Metro in Snapped view: see attached screenshot for the shown display; is this expected?

I don't know but feel free to post a bug about it, it may be closed but that's ok.

> 1) jerky scrolling on a site - also happening with Win 8 32-bit and 64-bit, and 
> Aurora Metro interface (see attached screenshot for more details)

This sounds related to apzc, but feel free to post a bug.

> 2)  Nightly install and first run: the Metro icon is displayed on the start screen, 
> even if the browser was not set as default

Please post with specific steps. Sounds like this may just be multi install related though.

> 3) video & audio playback - FAIL - see https://bugzilla.mozilla.org/show_bug.cgi?id=842639

Commented in that bug.

> 4) Flash content - missing plugin error even if Flash is already installed
Plugins including flash are not supported for the initial release.
Assignee

Updated

6 years ago
Flags: needinfo?(netzen)
> > 1)Metro in Snapped view: see attached screenshot for the shown display; is this expected?
> 
> I don't know but feel free to post a bug about it, it may be closed but
> that's ok.

I've logged bug 924038 for this and CC'ed you.

> > 1) jerky scrolling on a site - also happening with Win 8 32-bit and 64-bit, and 
> > Aurora Metro interface (see attached screenshot for more details)
> 
> This sounds related to apzc, but feel free to post a bug.

I've logged bug 924044 for this and CC'ed you.
> 1)  display rendering issue if 2 monitors are used (17” and 22”): open Metro
> FF on the 17” monitor, then drag it to the 22” one (see attached screeshot
> with the problem)

I've logged bug 924051 for this.

(In reply to Brian R. Bondy [:bbondy] from comment #14)

> > 2)  Nightly install and first run: the Metro icon is displayed on the start screen, 
> > even if the browser was not set as default

For this issue I've logged bug 924045.

I've CC'ed you on the logged issues.
OS: Windows 8 Metro → Windows 8.1

Updated

6 months ago
Product: Tracking → Tracking Graveyard
You need to log in before you can comment on or make changes to this bug.