We had reports from the wild (via Facebook a11y contact) that Firefox 'no longer works' with Windows HCM. I've tested it on Windows 7 a bunch, (turning HCM on and off, restarting, etc) and had various outcomes: FF seemed to hang. FF seemed to work properly. FF seemed to mangle the tab names, and the window: shrink, restore, and close buttons disappeared (?). Gijs have you had any similar reports? Blair I noticed you filed a bunch of specific HCM bugs recently, did you also hear about any intermittend HCM breakage?

This is the latest public version in High Contrast Mode #1

(In reply to george zamfir from comment #1) > Created attachment 8460271 [details] > High contrast Mode in Firefox Browser.jpg > > This is the latest public version in High Contrast Mode #1 OK thanks George, so is the main concern here that content is not updating/reacting to Windows HCM?

(In reply to David Bolter [:davidb] from comment #0) > We had reports from the wild (via Facebook a11y contact) that Firefox 'no > longer works' with Windows HCM. I've tested it on Windows 7 a bunch, > (turning HCM on and off, restarting, etc) and had various outcomes: > FF seemed to hang. > FF seemed to work properly. > FF seemed to mangle the tab names, and the window: shrink, restore, and > close buttons disappeared (?). > > Gijs have you had any similar reports? > Blair I noticed you filed a bunch of specific HCM bugs recently, did you > also hear about any intermittend HCM breakage? I've not heard anything like this, no... what version were they using?

(In reply to :Gijs Kruitbosch (Gone July 26 - August 3) from comment #3) > (In reply to David Bolter [:davidb] from comment #0) > > We had reports from the wild (via Facebook a11y contact) that Firefox 'no > > longer works' with Windows HCM. I've tested it on Windows 7 a bunch, > > (turning HCM on and off, restarting, etc) and had various outcomes: > > FF seemed to hang. > > FF seemed to work properly. > > FF seemed to mangle the tab names, and the window: shrink, restore, and > > close buttons disappeared (?). > > > > Gijs have you had any similar reports? > > Blair I noticed you filed a bunch of specific HCM bugs recently, did you > > also hear about any intermittend HCM breakage? > > I've not heard anything like this, no... what version were they using? That was my testing today with FF 30 (sorry I meant to mention that).

[Tracking Requested - why for this release]: [Tracking Requested - why for this release]: [Tracking Requested - why for this release]: [Tracking Requested - why for this release]: There are two regression: #1: Broken subview regressed by Bug 878546 #2: Contents area regressed by Bug 946595 #1 Regression window(m-c) Good: http://hg.mozilla.org/mozilla-central/rev/4cd99f870618 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140123124827 Broken subview: http://hg.mozilla.org/mozilla-central/rev/066c526104ef Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140123125931 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4cd99f870618&tochange=066c526104ef #1 Regression window(fx) Good: http://hg.mozilla.org/integration/fx-team/rev/2da09980b901 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140123040907 Broken subview: http://hg.mozilla.org/integration/fx-team/rev/04b6213da4e1 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140123051013 Pushlog: http://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=2da09980b901&tochange=04b6213da4e1 Regressed by: 04b6213da4e1 Mike de Boer ? [Australis] Bug 878546: refresh the styling of sub-views. r=Gijs #2 Regression window(m-c) Good: https://hg.mozilla.org/mozilla-central/rev/88ae1bfaaf3d Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140328161633 Broken contents and subview: https://hg.mozilla.org/mozilla-central/rev/4f3443da36a1 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140328164933 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=88ae1bfaaf3d&tochange=4f3443da36a1 #2 Regression window(fx) Good: https://hg.mozilla.org/integration/fx-team/rev/38c8dbb6ad87 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140328024048 Bad: https://hg.mozilla.org/integration/fx-team/rev/d8a36b893b2b Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140328031646 Pushlog: http://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=38c8dbb6ad87&tochange=d8a36b893b2b Regressed by:: d8a36b893b2b Gijs Kruitbosch ? Bug 946595 - High contrast themes on Windows 8 shouldn't be considered the default theme in CSS, r=jimm Regarding #1 subview theme problem, I will file a separate bug.

It seems like various unrelated issues were mixed up in this bug. They should be filed and treated as individual bugs instead.

(In reply to Dão Gottwald [:dao] from comment #7) > It seems like various unrelated issues were mixed up in this bug. They > should be filed and treated as individual bugs instead. I already filed a separate Bug 1042263 about #1 regression. This bug is for #2 problem (#2: Contents area regressed by Bug 946595).

(In reply to David Bolter [:davidb] from comment #0) > Blair I noticed you filed a bunch of specific HCM bugs recently, did you > also hear about any intermittend HCM breakage? No, but those bugs were largely from my own observations of where we're lacking in HCM - and I hadn't experienced any intermittent hanging/mangling while exploring HCM.

(In reply to Alice0775 White from comment #8) > This bug is for #2 problem (#2: Contents area regressed by Bug 946595). Hm, that fits with comment 1. But comment 0 describes hanging/mangling. So I think comment 1 should be split out to a separate bug.

Okay I filed a saparete bug for #2 problem (#2: Contents area regressed by Bug 946595).

I filed a saparete Bug 1042625 for #2 problem.

I think there are no remaining issues here.